DNS Propagation Checker
Check whether a DNS change has propagated by querying multiple public DNS-over-HTTPS resolvers (Cloudflare, Google, Quad9, AdGuard) at once and comparing their answers — see the resolved value, TTL and consensus for A, AAAA, MX, CNAME, TXT or NS records.
Input
The domain (or subdomain) to look up, e.g. example.com, www.example.com or _dmarc.example.com.
Output
| Metric | Value |
|---|---|
| No data yet | |
| Resolver | Provider | Status | Resolved value | TTL |
|---|---|---|---|---|
| No data yet | ||||
Guides
When you update a DNS record — point a domain at a new server, change a mail host, add a TXT verification string — the change does not reach the whole internet at once. Different resolvers around the world cache the old answer until its TTL expires, so for minutes or hours some visitors see the new value and others see the old one. The DNS Propagation Checker shows you exactly where that rollout stands right now.
Enter a domain and pick a record type, and the tool queries several large public DNS resolvers at the same time — Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9) and AdGuard — then compares their answers. A summary tells you whether the record is fully propagated, still rolling out, or not resolving at all, and a per-resolver table shows each provider's resolved value and TTL side by side.
How to use it
- Type the domain you want to check —
example.com, a subdomain likewww.example.com, or an underscore name like_dmarc.example.com. - Choose the record type: A (IPv4), AAAA (IPv6), MX (mail), CNAME, TXT or NS.
- Click Check propagation. Each resolver is queried over DNS-over-HTTPS and its answer is listed with a status of Propagated, Differs, No records or an error.
The Resolvers agreeing line and Verdict in the summary tell you how close the change is to being global. When every resolver returns the same value, propagation is complete.
FAQ
What does "Differs" mean?
That resolver returned a valid record, but a different value than the majority. This is normal mid-change (some caches still hold the old record) — or, for large sites, a sign the domain uses geo-based or anycast answers that legitimately vary by location.
Why does a resolver show an error or "No records"?
NXDOMAIN means the domain does not exist; SERVFAIL/REFUSED mean that resolver could not answer; "No records" means the domain exists but has no record of the type you asked for (for example, no MX record on a domain that does not handle mail).
What is TTL and why does it matter?
TTL (time to live) is how long, in seconds, a resolver is allowed to cache the record. A record with a 3600s TTL can be served from cache for up to an hour after you change it. Lowering the TTL before a planned change makes future updates propagate faster.
How many resolvers are checked?
Four independent public resolvers on different anycast networks. They are a representative global sample, not an exhaustive census — a record can still be cached elsewhere even when all four agree.
Privacy
The domain you enter is sent to the public DNS resolvers listed above so they can look it up — that is inherent to any DNS query. The lookup runs on our server rather than in your browser (public resolvers do not allow direct cross-origin browser calls), and we do not store the domains you check or their results.