DNS Propagation Checker

After you change a DNS record, resolvers keep serving the old answer until its TTL expires. This tool asks 8 major public resolvers at the same time and groups their answers, so you can see whether everyone sees the new value yet.

Tool status: Functional with limitations Works, but there are technical limits explained on the page.

What this tool can and cannot do

We query large public resolvers operated from several countries. Most of them use anycast (many locations sharing one address), and our server reaches the instance nearest to our hosting location. Results therefore show how major resolver networks see your record – not a guaranteed city-by-city view. Location-specific answers (GeoDNS) may differ for visitors elsewhere.

Data sources: 8 public DNS-over-HTTPS resolvers

Understanding the results

All resolvers matching means the change has propagated to these networks. Mixed answers are normal during the first minutes or hours after a change, depending on the previous TTL.

Troubleshooting

  • If one resolver keeps showing an old answer long after the TTL, some providers offer a cache-purge page (for example Google and Cloudflare).

Frequently asked questions

How long does DNS propagation take?

Usually as long as the old record's TTL – often 5 minutes to 1 hour, at most 24–48 hours for long TTLs or name-server changes.