DNS Propagation Checker
Type a domain, pick the record you changed, and see what 15 resolvers return right now: Cloudflare, Google, Quad9, AdGuard, DNS.SB, AliDNS and NextDNS, plus Google answering for users in the US, Brazil, Germany, the UK, India, Japan, Australia and South Africa. Each row shows the answer and its TTL left: how long that resolver may keep serving it before it asks your nameservers again. DNS never pushes a change out. Every resolver keeps its cached copy until that TTL runs out, so a change has finished spreading once no row shows the old value, which takes at most the old record's TTL (often 5 minutes to an hour). A nameserver change is slower: the .com registry publishes NS records with a 2-day TTL.
Free, no sign-in, 20 lookups a minute. Answers are cached for 30 seconds. Also: DNS lookup, MX lookup, Nameserver lookup, TXT record lookup, SPF record checker, DMARC checker, DKIM checker, CNAME lookup, reverse DNS lookup, MTA-STS checker, BIMI checker, email deliverability checker.
Do resolvers agree on well-known names
Checked through this tool, from the Worker, on November 7, 2026. Click a name to run it live.
| Name | Type | Agree | Answers seen | Most common |
|---|---|---|---|---|
| github.com | A | 5 of 15 | 11 | 172.182.252.133 |
| www.apple.com | A | 9 of 15 | 5 | 23.45.136.241 |
| netflix.com | A | 15 of 15 | 1 | 207.45.72.1, 207.45.73.1 |
| gmail.com | MX | 15 of 15 | 1 | 5 gmail-smtp-in.l.google.com, 10 alt1.gmail-smtp-in.l.google.com +3 |
| wikipedia.org | NS | 15 of 15 | 1 | ns0.wikimedia.org, ns1.wikimedia.org +1 |
| cloudflare.com | AAAA | 15 of 15 | 1 | 2606:4700::6810:84e5, 2606:4700::6810:85e5 |
Agree counts the resolvers that returned the most common answer, out of those that answered. github.com came back as 11 different addresses because GitHub hands each region its own; www.apple.com sits on Akamai. Neither is a stale record. netflix.com, gmail.com's mail servers, wikipedia.org's nameservers and cloudflare.com's IPv6 addresses were identical on all 15.
DNS Propagation Checker questions
How long does DNS propagation take?
As long as the old record's TTL, counted from when each resolver last fetched it. A record with a TTL of 300 is everywhere within 5 minutes of the change; one with 86400 can take a day. Lowering the TTL only helps if you do it at least one old TTL before the change, so resolvers have picked up the short one. Nameserver changes are the slow case: the .com and .net registries hand out a domain's NS records with a TTL of 172800 seconds (2 days), which is where the 24 to 48 hours people quote comes from. It is the worst case, not the norm.
Why do resolvers show different IP addresses for the same domain?
Usually because the domain wants them to. CDNs and large sites answer each resolver with the address of a data center near it, and the country rows here differ because Google passes a different client subnet each time. On 7 November 2026 github.com's A record came back as 11 different addresses from these 15 resolvers, while netflix.com's was identical on all of them. That is not a stale record. A stale record looks different: a few rows still return one specific old value, with a TTL counting down, while the rest show the new one. If no row shows the address you replaced, the change is done.
Can I clear a resolver's cache to speed propagation up?
For two of them, yes. Google Public DNS has a Flush Cache form (developers.google.com/speed/public-dns/cache) and Cloudflare has one at one.one.one.one/purge-cache; each clears one name and record type from that resolver only. Your ISP's resolver and everyone else's cannot be cleared from outside, they refresh when the TTL runs out. On your own computer, flush the OS cache (ipconfig /flushdns on Windows, sudo killall -HUP mDNSResponder on macOS) and restart the browser, which keeps a cache of its own.
What are the country rows, and are they real servers in those countries?
They are Google Public DNS asked 8 times with an EDNS Client Subnet (RFC 7871): the first 24 bits of a user's address, which Google forwards so a CDN can pick a server near that user. Each row sends a subnet of a big consumer ISP there (Comcast in the US, Deutsche Telekom in Germany, Jio in India, Telstra in Australia and so on), so it shows the answer a CDN gives users in that country. It is still one resolver with one cache, not a server in each country, and nameservers that ignore the subnet give every row the same answer.
More free domain tools
The DNS lookup shows every record a domain publishes. The MX lookup shows which servers take a domain's email and who runs them. The Nameserver lookup shows a domain's nameservers and which company hosts its DNS. The TXT record lookup reads a domain's SPF and DMARC records. The SPF record checker validates a domain's SPF record and counts its DNS lookups against the limit of 10. The DMARC checker reads a domain's DMARC policy, reports and alignment, and flags what weakens it. The DKIM checker finds a domain's DKIM keys among 22 common selectors and checks each key's size. The CNAME lookup follows a hostname's CNAME chain to its final address and spots dangling records. The reverse DNS lookup finds the hostname (PTR record) behind an IP address and checks that it resolves back. The MTA-STS checker fetches a domain's MTA-STS policy and checks that it covers every mail server. The BIMI checker checks a domain's BIMI record, SVG Tiny PS logo, mark certificate and whether DMARC lets the logo show. The email deliverability checker runs every DNS check that decides whether a domain's mail is trusted, with the failures first. For the website itself, the redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers, the HTTP header checker shows the response headers a URL sends and grades its six security headers and the website down checker checks from outside your network whether a site answers, and how fast. For who registered a name and when, use the WHOIS lookup, Domain age checker or Domain expiration checker. See which extensions a name is still free in with the domain availability checker, or price one in the domain value calculator.