DNS Propagation Checker

What is DNS Propagation Checker?

DNS propagation checking queries the same DNS record from a spread of major public resolvers — Google, Cloudflare, Quad9, OpenDNS, and more, across different regions — to see whether a recent DNS change has actually spread across the internet or is still cached as old data in some locations.

Because DNS relies on distributed caching, a change you make at your registrar or DNS provider doesn't appear everywhere instantly. This tool shows you exactly which resolvers already see the new value and which are still serving the old one.

How to use the DNS Propagation Checker tool

1 Enter the domain you recently changed a record for, e.g. example.com.
2 Select the record type that changed — A, AAAA, MX, NS, TXT or CNAME.
3 Run the check and compare results across resolvers — matching values everywhere means propagation is complete.
4 If some resolvers still show the old value, note their TTL and be patient; they'll refresh once their cached copy expires.

When you need this tool

Confirming a DNS change (new hosting IP, updated nameservers, new MX records) has propagated before telling a client or team it's done.
Diagnosing why a site or email works for some users but not others right after a migration.
Verifying a domain transfer or nameserver change has taken effect globally, not just locally.
Checking whether a stale resolver cache — rather than a misconfigured record — explains an intermittent issue.
Timing the rollout of a planned cutover by watching propagation reach 100% across major public resolvers.

How it works

The tool sends the same DNS query, for the record type you choose, to a panel of major public resolvers located in different regions, and displays each one's current answer side by side. Differences between resolvers reflect normal DNS caching behavior — some picked up the new record already, others are still serving a cached copy until its TTL expires.

Frequently asked questions

How long does DNS propagation actually take?

It depends entirely on the TTL that was set on the old record before you changed it — not on any fixed internet-wide delay. A record with a 300-second TTL can be fully replaced everywhere within about 5 minutes of expiring; one with a 24-hour TTL can take up to a full day for every resolver's cache to naturally refresh.

Why do some resolvers show my new record and others show the old one?

Each resolver independently caches DNS answers until their individually-received TTL expires. A resolver that queried your domain recently (right before you made the change) will keep serving its cached answer until that specific TTL runs out, while a resolver that hadn't cached anything yet will pick up the new value immediately.

Can I speed up DNS propagation?

Not retroactively for caches that already hold the old record — but you can avoid the problem next time by lowering the TTL on a record well before you plan to change it, letting old cached copies expire quickly, then making the change once the short TTL is in effect everywhere.

Is 100% propagation guaranteed eventually?

Yes — once every resolver's cached copy of the old record naturally expires based on its TTL, every resolver will query again and get the new value. There's no permanent "stuck" state; it's purely a function of time and TTL.