About This Tool
DNS propagation is the delay between publishing a DNS change and that change becoming visible everywhere on the internet. When you update an A record, add an MX record, or change your nameservers, resolvers around the world keep serving the old value from cache until their TTL expires. This tool checks whether a change has gone live by asking five major public DNS resolvers (Google, Cloudflare, Quad9, OpenDNS, and AdGuard) what they currently return for your domain, then comparing their answers. When every resolver agrees, your record has propagated consistently. When they differ, the change is still working its way through resolver caches. Note that these are five different DNS providers, not geographic points of presence in different cities, so this measures cross-resolver consistency rather than per-region geography, which is a reliable proxy for real-world propagation.
How to Use
Enter a domain name, choose the record type you changed (A, AAAA, MX, TXT, NS, or CNAME), and click Check Propagation. The tool queries all five resolvers at once over DNS-over-HTTPS and shows a row per resolver with the exact values it returned, plus a status dot. The summary banner at the top tells you whether the responding resolvers are consistent (green) or still disagree (amber). If they differ, the amber dots in the table show you exactly which resolvers are still serving a stale answer. Click the resolved values to copy them.
Tips & Best Practices
Propagation speed is governed by the TTL on the record before you changed it, not the new value. If your old record had a 24-hour TTL, some caches can serve the stale value for up to 24 hours. Lower the TTL a day or two before a planned change so the switchover is faster. A brief inconsistency right after a change is completely normal. If resolvers still disagree after several hours, double-check that you edited the correct zone and record type, and that you do not have conflicting records. Nameserver (NS) changes at the registrar level can take the longest, sometimes up to 48 hours, because they depend on the parent zone and registry.
