Developer Tools
DNS Propagation Checker
See whether a DNS change has reached the world's public resolvers: compare A, AAAA, CNAME, MX, NS, TXT, CAA and SOA answers from Google, Cloudflare, Quad9 and others, plus Google's view from 15 countries.
How to use
- 1Type the domain or hostname you changed (for example www.example.com) and choose the record type.
- 2Optionally type the new value (an IP address, mail server or part of a TXT record) to see exactly which resolvers have it.
- 3Press Check. Each row is a public DNS resolver or a country view; a tick means it matches the new value (or, without one, the most common answer).
How it's calculated
Your browser asks each resolver over DNS-over-HTTPS (RFC 8484), with a 15-second limit per request. The country rows ask Google Public DNS with an EDNS Client Subnet (RFC 7871) from a consumer network in that country, checked against the regional internet registry's records on 22 November 2026. The SOA serial column shows which version of the zone each resolver has cached.
Frequently asked questions
Why do some resolvers still show the old value?
Resolvers keep an answer for the record's TTL (time to live) before asking again. If the old record had a TTL of 3600, a resolver that fetched it just before your change keeps it for up to an hour. Nothing can force other people's resolvers to forget early, though Google and Cloudflare offer public cache-flush pages for their own.
How long does DNS propagation take?
Usually no longer than the old record's TTL, which is often 5 minutes to 1 hour. Changing the name servers at your registrar is slower: the parent zone (.com, .uk…) lists them with its own TTL, commonly up to 48 hours. Tip: lower the TTL a day before a planned move.
Why do the country rows show different IP addresses?
Big sites and CDNs answer with servers near the visitor (geo DNS). The country rows show those location-based answers, so different addresses there don't mean the change is incomplete; compare with the expected value or look at the resolver rows.
What does 'Name doesn't exist (NXDOMAIN)' mean?
The resolver was told the name doesn't exist at all. For a new subdomain, it can also be a cached 'doesn't exist' answer from before you created it, kept for the zone's negative TTL (the last number in the SOA record).
Is anything sent to your servers?
No. Your browser queries the public resolvers directly; we don't see the domain or the results.
Sources
Example: moving a website to a new server
You point example.com from 198.51.100.7 to 203.0.113.10. The old A record had a TTL of 3600. Ten minutes later, entering 203.0.113.10 as the expected value shows Cloudflare and Quad9 already have it (they hadn't cached the old answer), while Google still returns 198.51.100.7 with a TTL counting down from 2950 seconds. That row will update within about 50 minutes, and you can keep the old server running until it does.
Reading the SOA serial
Every change to a zone usually increases its SOA serial number (often written as the date plus a counter, like 2026112201). If one resolver shows 2026112201 and another 2026112103, the second still has yesterday's copy of the zone cached. If the serials differ but every resolver answered recently, your name servers may be out of sync, which is worth checking with your DNS host.
Why this only uses public resolvers
A browser can't send classic DNS queries over UDP, so it can't ask your domain's own name servers or an ISP's resolver directly. DNS-over-HTTPS resolvers that allow web pages to query them are what a browser can reach: Google, Cloudflare, Quad9, Control D, CleanBrowsing, IIJ (Japan) and AliDNS (China). They're widely used and each caches independently, so together they're a good sign of how far a change has spread, but your ISP's own resolver may still lag behind.
Related tools
- DNS Lookup (A, MX, TXT, CNAME, NS…)
Look up DNS records for any domain — A, AAAA, CNAME, MX, TXT (SPF/DKIM/DMARC), NS, SOA, CAA, SRV and reverse PTR — compared across Google and Cloudflare to spot propagation issues.
- DMARC, SPF & DKIM Checker
Check a domain's email authentication: SPF with its 10-lookup limit and every include, DMARC under the current RFC 9989 rules, and DKIM key strength, plus Gmail's sender requirements. Runs in your browser.
- JSONPath Tester
Query JSON with JSONPath expressions like $.store.book[*].author or $..price and see every match with its exact path.
- Regex Tester
Test JavaScript regular expressions live — see every match highlighted, capture groups, named groups and match positions.
- API Tester (Online REST Client)
Send HTTP requests from your browser — any method, query params, headers, JSON or form body, bearer/basic/API-key auth — and inspect status, timing, headers and pretty-printed JSON. Export as cURL, JavaScript or Python.
- Color Contrast Checker (WCAG)
Check text and background colors against WCAG 2.2 AA and AAA contrast requirements — with a live preview and a suggested fix when a pair fails.