digdns.site
Free · no sign-up · DNS propagation

Has your DNS
change spread everywhere?

Check a domain’s DNS propagation across 15 public resolvers worldwide (Google, Cloudflare, Quad9, OpenDNS…): A, AAAA, CNAME, MX, NS, TXT.

Examples: google.com wikipedia.org github.com

15public resolvers
11blocklists
47DKIM selectors
100score points
Public DNS resolvers
Cloudflare · San Francisco1.1.1.1public resolver
Quad9 · Zurich9.9.9.9public resolver
Drag to spin the globe
15public resolvers on 4 continentsGoogle · Cloudflare · Quad9 · OpenDNS…

Understanding DNS propagation

Why a DNS change does not show up everywhere at once.

1You edit the zone

The new value is published at once by your domain’s name servers.

2Caches expire

Each resolver (ISP, Google, Cloudflare…) keeps the old answer until its TTL runs out.

3The new value spreads

When every resolver gives the same answer, propagation is complete. Run the test again to follow progress.

FAQ

How long does DNS propagation take?

Usually a few minutes to a few hours: each resolver keeps the old answer until its TTL expires. Changing name servers (NS) at the registrar can take up to 48 hours.

Why do some resolvers show a different answer?

They still have the old value cached, or the domain deliberately returns different addresses by region (CDN, load balancing). Several answers therefore do not always mean a problem.

How can I speed up propagation?

Lower the TTL several hours before the change, then raise it afterwards. On your computer, flush the DNS cache: “ipconfig /flushdns” on Windows, “sudo dscacheutil -flushcache” on macOS.