DNS propagation multi-region
6 public JSON-DoH resolvers worldwide in parallel — surface geo-split DNS and cache lag.
How this tool works
After a DNS change — new A record, new MX, new TXT — the new info propagates worldwide step by step. This multi-region check queries 6 independent public resolvers simultaneously: Cloudflare (1.1.1.1), Google (8.8.8.8), AdGuard, NextDNS, AliDNS (China) and DNS.SB. Within seconds you see whether all 6 resolvers see the new records, or whether some caches still hold the old values. "Consistent" turns green once all resolvers agree.
Typical use cases
- Check propagation status immediately after a DNS update
- For customer-side "site unreachable" reports, locate which resolver has stale data
- Make geo-split DNS visible — some vendors return different answers per region
- Before TTL reduction, verify the current TTL is honoured everywhere
Frequently asked questions
How long does full propagation take?
At most as long as the TTL of the old record — TTL=300 (5min) means within 5 minutes, TTL=86400 (24h) up to a day. Lower the TTL 24h before a planned change.
Why do resolvers persistently see different IPs?
Geo-split DNS is common with large CDNs — Cloudflare returns the nearest POP, for example. "Inconsistent" here is not a bug.
Which resolvers cover which regions?
Cloudflare and Google are global via anycast. AdGuard has an EU focus, NextDNS US/EU, AliDNS China, DNS.SB Singapore. More diversity = better signal.
Why not 30 or more resolvers?
More resolvers = more latency and more retries. 6 is enough for a sound assessment; beyond that many answers become redundant.
What is the difference vs the standard DNS lookup?
Standard DNS lookup uses 3 resolvers (Google, Cloudflare, AdGuard) for fast diagnosis. DNS propagation uses 8 for global coverage. Functionally identical but propagation is the right tool right after DNS changes.
Related tools
Continuous monitoring vs. one-shot?
XICTRAQ monitors uptime, SSL, security headers, GDPR and performance 24/7. Free plan, no credit card.