DNS Propagation Checker — 85 Global Resolvers
The dnsverifier.com DNS Propagation Checker queries the same DNS record from 85 public resolvers across 60+ countries on every inhabited continent, then visualizes which regions have received the new value on a live world map. It uses happy-eyeballs UDP → TCP → DoH transport so results work from networks that block UDP/53. Anycast resolvers (Cloudflare, Google, Quad9) are placed at their registered HQ.
Frequently asked questions
- What is DNS propagation?
- When you change a DNS record, recursive resolvers around the world keep serving the old cached value until that record's TTL expires. 'DNS propagation' is the period during which different resolvers return different answers — usually 5 minutes to 48 hours, depending on the previous record's TTL.
- How long does DNS propagation take?
- Most authoritative-level changes propagate within the previous record's TTL. Common defaults: 300 seconds (5 min) at CDN providers, 3600 seconds (1 hour) at most registrars, and up to 172,800 seconds (48 hours) for nameserver delegation changes (NS records at the registry).
- How do I check DNS propagation worldwide?
- Enter your domain and pick the record type. The tool queries 85 resolvers in parallel, colors each location green (matches consensus), amber (different value), or red (no record). The world map shows the geographic spread at a glance.
- What is the difference between dnsverifier.com and whatsmydns.net?
- Both visualize global DNS resolution. dnsverifier.com queries 85 resolvers across 60+ countries (vs ~25 on whatsmydns.net), supports DNSSEC and the full record set including CAA / DS / DNSKEY, falls back to TCP and DNS-over-HTTPS when UDP/53 is blocked, and streams results live as each resolver responds.
- Why does one resolver show a different result?
- Most commonly: that resolver cached the old value and its TTL has not expired. Less commonly: the resolver is GeoDNS-aware and your authoritative server is returning a region-specific answer. Anycast resolvers can also serve different POPs depending on the client's network path.