DNS propagation checker
Enter your domain and record type to check propagation across 10 global DNS resolvers simultaneously.
About this tool
See if your DNS change has propagated across Cloudflare, Google, Quad9, OpenDNS, and 6 more global resolvers in real time. Browser-based, no signup.
Enter your domain and record type to check propagation across 10 global DNS resolvers simultaneously.
- 1
Enter your domain name and select the record type you changed (A, MX, TXT, etc.).
- 2
Click Check Propagation — the tool queries 10 global resolvers simultaneously.
- 3
Green rows indicate resolvers that have the updated record; red rows show stale or missing data.
- 4
Check the consistency rate at the top to see how widely the change has spread.
Confirm that a new A record has spread to all major resolvers after a server migration.
Check whether your MX update has propagated before switching email providers.
Diagnose why some users see a new site but others still hit the old IP.
After migrating a server
example.com Type: A8/10 resolvers show new IP — 80% consistentAfter adding SPF record
example.com Type: TXT10/10 resolvers show v=spf1 record — 100% consistentJust after a change
newdomain.com Type: A2/10 resolvers updated — still propagatingThese answers explain common dns propagation tasks, expected input formats, and edge cases so both visitors and search engines can understand what this tool does.
How many resolvers are checked?
10 resolvers across different geographic regions: Cloudflare, Google, Quad9, OpenDNS, AdGuard, NextDNS, DNS.SB (Asia), Mullvad (Europe), BlahDNS (Japan), and CanadianShield (Canada).
What does the consistency rate mean?
The consistency rate shows the percentage of responding resolvers that returned the same record set. 100% means all resolvers agree. Lower values indicate the change is still in progress or some resolvers are serving stale cached data.
How long does DNS propagation take?
Propagation speed depends on the TTL of the old record. A low TTL (e.g., 300 seconds) spreads changes in minutes. A high TTL (e.g., 86400 = 24 hours) means resolvers may cache the old record for up to a day.