Why do different checkers show different results?

Because they query different resolvers, and each resolver refreshes on its own TTL schedule. During propagation it's normal for some locations to show the new record while others still serve the cached old one until their TTL expires.

How long does DNS propagation take?

Usually it tracks your record's TTL, from a few minutes to a few hours. Allow up to 48 hours as a worst case, because some ISP resolvers ignore TTLs and cache longer than they should. Lowering the TTL before a change speeds convergence.

Is dig better than a web-based checker?

They answer different questions. dig gives you the exact value and TTL from a resolver you choose, which is precise. Web checkers give you a global map across many locations at once. Use dig to verify correctness and a web tool to gauge worldwide spread.

Best DNS Propagation Checkers Compared

VigilDog Team · September 8, 2026 · 6 min read

You changed an A record or moved MX to a new provider, and now you're refreshing a checker every five minutes waiting for the world to catch up. This is where the best DNS propagation checkers earn their keep, but only if you understand what they can and can't tell you. Here's how propagation really works, what to look for in a tool, and the handful worth using.

What "propagation" really is

DNS doesn't "spread" like a rumor. When you publish a record, it's authoritative immediately at your nameservers. What takes time is the expiry of cached copies at resolvers around the world. Every record carries a TTL (time to live); a resolver that fetched your old record will keep serving it until that TTL runs out, then ask again and pick up the new value.

That's the whole mechanism. A propagation checker simply queries many resolvers in different locations and shows you which ones still hold the old answer and which have refreshed. If you set a 3600-second TTL, expect up to an hour of mixed results, plus a tail of poorly behaved resolvers that ignore TTLs. The practical tip: lower the TTL a day before a planned change so the world converges faster.

How a domain name resolves to a server

What to look for in a checker

Not all checkers are equal, and the fancy-looking ones aren't always the most trustworthy. Judge them on substance.

Geographic spread: more query locations means a truer picture of global state.
Record-type coverage: A, AAAA, CNAME, MX, TXT, NS, CAA, SOA, not just A.
Whether it queries authoritative servers or public resolvers (both are useful, for different questions).
No aggressive caching of its own results, which can show you stale data and send you chasing ghosts.
A raw view of the actual returned value, so you can confirm the record is correct, not just "changed".

The tools worth using

whatsmydns.net is the long-standing favorite for a fast global map of a single record across dozens of locations, clean and free. dnschecker.org covers similar ground with broad record-type support and a slightly denser location list. Both are excellent for the "has it propagated yet?" question.

For authoritative truth rather than cache state, Google's dns.google and Cloudflare's 1.1.1.1 resolver pages let you query specific record types directly and confirm what a major public resolver sees right now. And VigilDog's DNS checker is built for the follow-up question most tools skip: not just what a record is this second, but whether it has quietly changed since you last looked. If you're unsure which record type you're even inspecting, DNS records explained is a quick primer.

Check it yourself with dig

No dashboard beats querying directly, and it takes seconds. Use dig to ask a specific resolver for a specific record:

dig +short example.com A, the current A record from your default resolver.
dig @8.8.8.8 example.com A, ask Google's resolver specifically.
dig @1.1.1.1 example.com MX, check MX at Cloudflare.
dig example.com A +noall +answer, see the TTL counting down, which tells you how long the cache will hold.
On Windows: nslookup -type=MX example.com 8.8.8.8 does the same job.

From spot-check to standing watch

Propagation checkers answer a one-time question during a migration. They can't tell you when a record changes next month because a registrar transfer clobbered your MX, or a team member edited an A record and broke a subdomain. That's a monitoring problem, not a lookup problem.

VigilDog watches your DNS continuously and alerts you the moment a record drifts from what you expect, so the next unexpected change reaches you before your users do. Pair the free DNS checker for migrations with continuous monitoring for everything after.