DNS Propagation Checker
Use this DNS propagation checker to see whether a DNS change has reached public resolvers. It asks Cloudflare, Google and Quad9 for the same record and highlights any difference between their answers.
Three public resolvers are a sample, not every location. Resolvers of ISPs and other networks can still hold an older answer.
Try an example
How this DNS propagation checker works
The tool sends one query for the name and record type to Cloudflare, Google and Quad9 at the same time. It then groups the answers by value, so you see at a glance which resolvers return the old value and which return the new one.
How DNS propagation works
DNS does not push a change to the world. Each resolver keeps an answer in its cache until the TTL of that answer runs out, then asks again. After you change a record, a resolver shows the new value only after its cached copy has expired.
This is why the wait depends on the TTL that the old record had. Lower the TTL some time before a planned change to shorten the wait.
How to check DNS propagation
Enter the name and the record type that you changed, then press Check. Each row of the result is one value. The table shows which resolvers return it and with what TTL. A value that one resolver does not return is marked as different.
When all resolvers that answered return the same set of values, the result says they agree. TTL numbers can differ and that does not count as a difference.
What a DNS propagation checker with three resolvers can tell you
Cloudflare, Google and Quad9 are large public resolvers. They are not three countries: each one runs many servers worldwide, and you reach one of them. If they all show the new value, most people who use these resolvers see it too.
It does not prove that every user sees the change. Home routers, ISPs and company networks run their own caches, and some keep an old answer longer than its TTL.
Frequently asked questions
How long does DNS propagation take?
It depends on the TTL of the old record. A resolver can keep the old answer until that TTL runs out. A change to the name servers of a domain can take longer, because the parent zone caches the delegation with its own TTL. Lowering the TTL before a change shortens the wait.
Why do the resolvers show different answers?
They cached the record at different times, so some of them still hold the old value. Check again after the TTL has passed. If the difference stays, check the records at the authoritative name servers.
Does a matching result prove that everyone sees the change?
No. It shows that three large public resolvers agree. Other resolvers, such as your ISP, can still return an older answer.
Can I check DNS propagation from different countries?
Not with this tool. It compares three public resolvers, not countries. The result is labeled by resolver for that reason.
Which record type should I check?
Check the type you changed: A or AAAA for a web server address, CNAME for an alias, MX for mail, TXT for SPF or DKIM, NS for a move to other name servers.
Monitor this DNS record every minute
Uptrack checks the record on a schedule and alerts you when it changes or stops resolving.
Plans from $3/mo, with a 30-day money-back guarantee.