24H DRIFT ▲ 2,395 vs yesterday 11,930 material changes across 8,531 domains
Provider, certificate, registration and reachability moves that matter, distilled from every scan across the tracked catalog in the last 24 hours. This is the day, in one number.
Watched-domain breakdown · 24h 88 DNS provider moves
46 reachability flips
9 hosting moves
215 domains changed DNS provider
Across the tracked catalog · most recent complete day (Sep 15)
Who runs resolution. A DNS move re-homes all of a domain’s traffic, and it is usually the first public sign of a re-platform.
Named-provider flow · watched + first-scan domains
Gaining · 24h cloudflare.com +2 registrar-servers.com +1 Losing · 24h domaincontrol.com -1 domainesia.com -1 inmotionhosting.com -1
0 domains switched email provider
Across the tracked catalog · most recent complete day (Sep 15)
Where the mail goes. An MX move changes which company receives every message sent to the domain, and migrations show up here first.
No net movement between named providers in the watched flow map, which is a narrower read than the count above it.
Watched domains None of them are on a watch list yet. Name a domain and every time it moves its mail you hear about it in minutes.
Watch a domain →
0 watched domains switched issuing CA
Watched + first-scan domains · last 24h · the catalog-wide reading is re-measuring
Who vouches for the TLS handshake. CA switches track CDN moves and platform changes, and a surprise switch on a domain you own is worth a look.
No net movement between named providers on watched domains in the last 24 hours.
623 curated domains not reachable
No response at all on the last probe: timed out, refused, or dead DNS. Movement against yesterday is the incident signal.
0.08% of 804,216 probed curated domains
612 timed out· 11 DNS failed
17,577 sites serving errors
Up, but broken: origins serving 5xx, roots that 404, TLS handshakes that fail.
2.2% of 804,216 probed curated domains
9,249 404 at root· 8,328 5xx origin error
79,076 throttled or blocked our scanner
Healthy sites running visible bot defense: they rate-limited or blocked the probe. A posture signal, not an outage.
9.8% of 804,216 probed curated domains run bot defense we can see
75,287 403 bot-block· 3,789 429 rate-limited