DNS Propagation Checker
Query the same record across Cloudflare, Google, Quad9 and other DNS-over-HTTPS resolvers and see who still serves the old answer.
Your query is sent only to the resolver shown; this site keeps no logs. Copy link to this result
What this checks
Sends your query to every enabled public resolver in parallel and compares answers, TTLs and latency.
Agreement below 100 % right after a change is cache, not an error.
There is no push mechanism in DNS: each recursive resolver keeps the old answer until its cached copy reaches the TTL you published (RFC 1035 section 3.2.1, RFC 2181 section 8), then asks your authoritative nameservers again. So "propagation" is really many independent caches expiring at different moments, and the only way to speed it up is to lower the TTL before you make the change. A resolver that gives a different answer long after the TTL has passed points to a problem at the source, not to slow propagation.
If it fails
- Old answer at one resolver: wait for the previous TTL to expire; lower TTLs before the next migration.
- Different answers for days: your authoritative nameservers disagree — check serials and zone transfers.
FAQ
How long does propagation take?
Up to the old TTL (often 1–24 h). The 48-hour figure is a leftover from registrar root updates.
Why does my ISP still show the old value?
ISP resolvers are not in this list and may ignore TTLs; flush or wait.
Can I add a resolver?
The list lives in data/resolvers.json; only resolvers that allow browser (CORS) requests work.
Is this the same as a global check from many locations?
No — these are anycast public resolvers; it shows resolver caches, not geography.