DNS Propagation Checker
Ask five public DNS resolvers the same question at the same time, to see whether they agree on a record after a change.
What it checks
- Queries Cloudflare, Google, Quad9, AdGuard and OpenDNS in parallel over DNS-over-HTTPS
- Supports A, AAAA, CNAME, MX, NS, TXT and CAA; A is the default
- Sorts each resolver's answers and marks the result consistent only if every answering resolver returned the same set
- Shows the error text for any resolver that did not answer
How to read the result
- Consistent means all answering resolvers returned identical values at the time of the check. Disagreement usually means a change is still spreading or a resolver holds an older cached answer.
- The result is marked not consistent when fewer than two resolvers answer, even if the one answer that came back is correct.
- Cached copies expire after their TTL. Re-run the check after the old TTL has passed before you judge the change.
What it does not tell you
This is a single snapshot from five resolvers, not a global survey, and it does not show TTL values. It does not query authoritative servers directly. This is not a penetration test.
Data sources
Each request goes live to the public DNS-over-HTTPS endpoints of the five resolvers named above; the propagation results are not cached.
No login · 30 calls / hour / IP · Data stored in the EU
FAQ
Why do the resolvers disagree?
Each resolver caches answers for its own period. After a DNS change, some resolvers can keep returning the old record until their cached copy expires.
Which record types are not supported?
SOA, SRV and other types are not supported here. Use the DNS Lookup tool for a broader set of record types.
Guide: Subdomain takeover: how a forgotten DNS record is claimed