DNS Propagation Checker
Compare what several major public resolvers return for the same record to see whether a DNS change has propagated.
Check DNS propagation
Query several public resolvers at once and compare their answers for the same domain and record type.
Results will appear here.
Beta: this samples a few major public resolvers, not a full set of global points of presence.
How propagation checking works
When you update a DNS record, the change does not appear everywhere at once. Resolvers around the world keep cached copies until the record's TTL runs out, so for a while some will answer with the new value and some with the old one. This checker queries several independent public resolvers — Cloudflare, Google and Quad9 — for the same record at the same moment and lines up their answers. When they all match, your change has reached those providers; when they disagree, it is still on the way.
How to read the result
A Consistent verdict means every reachable resolver returned the same set of values — a good sign your edit has settled. Differences detected means at least one resolver still has a stale answer; wait for the TTL to expire and check again. Because this is a sample of major resolvers, a consistent result here is encouraging but not a guarantee that every network on earth has caught up. For day-to-day changes it is a reliable, fast signal.
Frequently asked questions
What is DNS propagation?
When you change a DNS record, the new value has to spread to resolvers around the world as their cached copies expire. Until then, different resolvers may still serve the old answer. That spreading process is called propagation.
How does this checker work?
It asks several independent public resolvers — Cloudflare, Google and Quad9 — for the same record at the same moment and compares their answers. If they all agree, your change has reached those providers. If they differ, it is still propagating.
Is this a full global propagation check?
No, and we are upfront about that. A true worldwide check queries dozens of points of presence in many countries. This browser-based tool samples a few major public resolvers, which is a fast, honest indicator rather than a complete map.
How long does propagation take?
It is governed by the record's TTL plus caching along the way. Many changes settle within minutes to a few hours; some can take up to 24–48 hours. Lowering the TTL before a planned change speeds things up.
Migrated a site and something feels off?
Once records have propagated, confirm the new host actually performs. Run the full check-up to measure speed, latency and DNS together, and find the layer that needs attention.