About the DNS Propagation
This DNS propagation checker queries several major public resolvers — Cloudflare, Google, Quad9, OpenDNS, AdGuard and Level3 — for the same record and compares their answers. When you change a DNS record, resolvers around the world pick up the new value at different times depending on cached TTLs, so seeing whether they agree tells you how far a change has propagated.
Pick the record type (A, AAAA, MX, TXT, NS or CNAME), enter your domain, and the tool shows each resolver's answer side by side with a clear verdict: fully propagated when they all match, or still propagating when they differ. Use it after updating an A record, switching nameservers, or publishing a new TXT/SPF record.
How to use it
- Enter the domain whose record you changed.
- Choose the record type you are tracking (A, MX, TXT, NS, …).
- Submit to query several public resolvers at once.
- Compare the answers — all matching means the change has propagated.
Examples
- After repointing an A record, check that every resolver returns the new IP.
- Confirm a new SPF TXT record is visible everywhere before going live.
- Verify a nameserver (NS) change has propagated across resolvers.
Frequently asked questions
How long does DNS propagation take?
It depends on the record's TTL and downstream caches — anything from a few minutes to 24-48 hours. Lowering the TTL before a planned change makes propagation faster.
Why do resolvers show different answers?
Each resolver caches records until their TTL expires. Right after a change, some still serve the old cached value while others have fetched the new one, so answers differ until all caches refresh.
Which resolvers are queried?
Public resolvers including Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), OpenDNS, AdGuard and Level3.
Does this query authoritative nameservers?
No — it queries public recursive resolvers, which is what real users hit. That is exactly what you want to know when checking propagation.