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.
What changed on the internet today
rolling last 24 hours · 809,753 tracked domains
24H DRIFT▼ 15 vs yesterday
4,170material changes across 2,277 domains
24h to ~3h ago
Watched-domain breakdown · 24h
85DNS provider moves
38reachability flips
7hosting moves
2SPF policies weakened
DNS DRIFT
406domains changed DNS provider
Across the tracked catalog · most recent complete day (Sep 1)
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
- seqlogic.net+1
- dyndns.gg+1
Losing · 24h
- seqlogic.com-1
- cloudflare.com-1
The board cloudflare 80.6% · aws route 53 14.6% · google cloud dns 2.8%
Moving sectors · watched domcop 28 · majestic 13 · telecom 1
Watched domains 85 of them are on a watch list. Watch a domain
EMAIL DRIFT
0domains switched email provider
Across the tracked catalog · most recent complete day (Sep 1)
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
CERT DRIFT
0watched 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.
NOT REACHABLE▲ 18 vs yesterday
582curated 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.07% of 804,216 probed curated domains
574 timed out·8 DNS failed
SITE ERRORS
18,222sites serving errors
Up, but broken: origins serving 5xx, roots that 404, TLS handshakes that fail.
2.3% of 804,216 probed curated domains
9,376 404 at root·8,846 5xx origin error
THROTTLED
80,776throttled or blocked our scanner
Healthy sites running visible bot defense: they rate-limited or blocked the probe. A posture signal, not an outage.
10% of 804,216 probed curated domains run bot defense we can see
75,003 403 bot-block·5,773 429 rate-limited
Subscribe: RSS · JSON
Every observation signed. Verify receipts →