Home › Toolkit › Network › DNS Propagation Viewer

🌍 DNS Propagation Viewer

You changed the record an hour ago and half the world still sees the old address — or does it? This viewer asks four major independent resolvers the same question at once and lines their answers up side by side.

About this tool

DNS changes do not propagate the way the word suggests — nothing is pushed anywhere. Instead, every resolver on earth holds its own cached copy of your record, stamped with an expiry time (the TTL) that your old record chose. Until a resolver's copy expires, it keeps answering with the old value, correctly, by design. That is why a change lands in minutes for some visitors and lingers for a day for others, and why 'propagation' is really a waiting room full of independent clocks.

This viewer does exactly that: this site's gateway sends a real DNS query — the same packet format your laptop sends — to four independent public resolver services (Google, Cloudflare, Quad9 and OpenDNS) and prints each answer verbatim. Agreement across all four means the change has effectively landed everywhere that matters; disagreement names the stragglers and, by the TTL they still serve, roughly how long they will keep the old answer. It is a sample of four, not a census of every resolver on earth — but these four serve a large share of the planet, and when they agree, the argument is over.

How to use it

  1. Type the domain whose record you changed (or are checking).
  2. Choose the record type you changed.
  3. Press Check propagation and compare the four answers — matching values mean the change has spread.

Good to know

  • Before a planned change, lower the TTL a day ahead (to 300, say) — the next change then clears caches in minutes instead of hours.
  • If one resolver disagrees long past the TTL, it is usually showing you a cached answer from before your change; note which one, and wait for its clock.
  • Check the exact name you changed: www and the bare domain are separate records with separate clocks.

Frequently asked questions

How long should propagation take?

As long as the old record's TTL, at most — commonly an hour, worst case a day for records that were cached at 86400. There is no switch to hurry a stranger's cache.

Why do the four resolvers sometimes show different TTLs?

Each counts down from the moment it cached the record, so their remaining times differ even when the answers agree — that difference is the system working as designed.

Does this check every DNS server in the world?

No tool can. These four are among the largest public resolvers; when they agree, the overwhelming majority of visitors see the same answer.

More Network tools

Making videos too? Try our YouTube Video Analyzer, or browse the full Toolkit and the free YouTube tools.