Who actually answers

curated catalog · last probe · the state of every tracked domain that is not reachable cleanly
not reachable
628
no response at all: timed out, refused, DNS failure, network error
sites serving errors
17,714
the site answered, but with a 5xx, a 404, or a TLS failure
throttled or blocked our scanner
80,408
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 DRIFT8,824 material changesacross 6,103 domains · 24h to ~40m ago · +1,459 vs yesterdayROTATION53 domains moved DNS from magpiedns.com to koaladns.com, 44 moved backa rotation loop, not a migration · 24hCERT DRIFT1 domains switched issuing CA24hNOW628 curated domains not reachablelast probe, steadySITE ERRORS17,714 sites serving errorslast probe · 5xx / 404 / TLSBOT DEFENSEbot defense observed on 80,408 sites429 rate-limit / 403 bot-block, a posture signal