Who actually answers

curated catalog · last probe · the state of every tracked domain that is not reachable cleanly
not reachable
1,602
no response at all: timed out, refused, DNS failure, network error
sites serving errors
20,527
the site answered, but with a 5xx, a 404, or a TLS failure
throttled or blocked our scanner
88,644
healthy sites that 429/403 our shared egress - never counted as an error

We could not read the list just now, so nothing below is a result. Reload in a moment.

We could not read the domain list just now. This is a read failure, not an empty view - the counts above and this list come from different reads, and only one of them answered.
CONTINUOUS INTERNET TELEMETRY24H DRIFT3,911 material changesacross 223 domains · 24h to ~3h ago · -374 vs yesterdayROTATION57 domains moved DNS from magpiedns.com to koaladns.com, 50 moved backa rotation loop, not a migration · 24hREGISTRAR DRIFT1 changed registrar24hNOW1,602 curated domains not reachable+55 vs yesterdaySITE ERRORS20,527 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 88,644 sites429 rate-limit / 403 bot-block, a posture signal