DNS Propagation Checker: Check DNS changes worldwide
Use the DNS Propagation Checker to check your domain's DNS propagation. The tool queries an A, AAAA, CNAME, MX, TXT or NS record across 20 public DNS resolvers at the same time, shows each resolver's response and tells you whether all responding resolvers return the same value yet.
Built by Jakub Martyniak
Free, with no sign-up required: enter a domain, choose a record type and run the check.
Found your domain? Register it and manage DNS in one panel.
Example result
What the result looks like in the DNS Propagation Checker
You enter a domain and a record type, and the tool queries 20 public resolvers simultaneously and shows each resolver's response. The example shows a fictional state shortly after an IP change; your result depends on your domain.
Example · Example with fictional domain example.com, type A
Not fully propagated yet- New IP
- 16of 20 resolvers
- These resolvers already return 203.0.113.10; the change has reached them.
- Old IP
- 3of 20 resolvers
- These resolvers still have 198.51.100.7 cached and will return the new IP only after the TTL expires.
- No response
- 1of 20 resolvers
- Resolvers that don't respond don't count against propagation; they're excluded from the evaluation.
Input
- Domain
- example.com
- Record type
- A
Output: response by resolver (selection)
- Google Public DNS · US (Global Anycast)
- 203.0.113.10
- Cloudflare DNS · US (Global Anycast)
- 203.0.113.10
- Quad9 · CH (Global Anycast)
- 203.0.113.10
- Deutsche Telekom · DE
- 198.51.100.7
- NTT (OCN) Japan · APAC (JP)
- 198.51.100.7
- Hurricane Electric · US
- No response
How it works
Check DNS propagation: How it works
Enter a domain, choose a record type and run the check to see its status worldwide in just a few steps.
Step 1
Enter domain
Enter the domain or subdomain whose DNS record you changed, such as shop.example.com. A leading https:// and any path are removed automatically.
Step 2
Choose record type
Choose the record type you changed: A (default), AAAA, CNAME, MX, TXT or NS. After changing nameservers, choose NS.
Step 3
Check propagation
Click “Check propagation”. The tool queries 20 public DNS resolvers at the same time.
Step 4
Read result
At the top, you'll see “Fully propagated” or “Not fully propagated yet” and how many resolvers return the same response. Below that, you'll see each resolver's value or status.
Step 5
Check again or share
If some resolvers still return the old value, check again after the TTL expires. The browser URL contains the domain and record type, so you can share the check.
Analysis
Understanding the results: What do the statuses mean?
The tool shows the returned value or status for each resolver. Only resolvers that actually responded count toward the overall result.
Fully propagated
All responding resolvers return the same value. A consistent “Domain not found” also counts as a matching response.
Not fully propagated yet
The responding resolvers return different values, usually a mix of old and new. The tool shows how many resolvers return the same response and how many distinct values there are.
No entry
The resolver knows the domain but has no record of the selected type. This counts as a response—for example, if you check AAAA and the domain only has an IPv4 address.
Domain not found (NXDOMAIN)
The resolver reports that the domain does not exist. If all resolvers report this, the domain often contains a typo.
No response
The resolver did not respond within 2.5 seconds. It is excluded from the comparison and does not count against propagation.
Resolver error or unknown error
The resolver returned SERVFAIL or REFUSED, or another error occurred. These resolvers are also excluded from the comparison.
Why this tool
What the DNS Checker checks for you
Key features of the checker.
20 resolvers at once
20 public DNS resolvers are queried in parallel. If a resolver does not respond within 2.5 seconds, it appears as “No response”.
A, AAAA, CNAME, MX, TXT, NS
Six record types: IPv4 and IPv6 addresses, aliases, mail servers, text records such as SPF or DMARC, and nameservers.
Resolvers in the US, Europe and Asia
Including Google, Cloudflare, Quad9, OpenDNS, Deutsche Telekom, Freifunk München, NTT Japan, AliDNS and 114DNS.
Clear overall result
“Fully propagated” appears only when all responding resolvers return the same value. Otherwise, the tool shows how many resolvers agree.
Shareable result link
After the check, the URL contains the domain and record type. Anyone opening the link runs the same check again—useful for support or colleagues.
No account required
Just enter a domain and check it—no sign-up required.
Troubleshooting
DNS change taking too long? Here's what you can do
How quickly a DNS change reaches everyone depends mainly on the old record's TTL. These three steps can help if propagation seems stuck.
Check the change with your DNS provider
Check your DNS provider's panel to see whether the change has been saved and is active. If all resolvers still return the old value, this is often why.
Lower the TTL before your next change
Lower the TTL one or two days before a planned change, for example to 300 seconds. Caches will then expire sooner after the change. If the change is already live, you can only wait.
Clear your local DNS cache
If the tool shows the new value but your computer still shows the old one, clear your system's DNS cache:
Windows (Command Prompt)
ipconfig /flushdnsmacOS (Terminal)
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderLinux with systemd-resolved
sudo resolvectl flush-cachesExplore more
More tools
Website Down Checker
Check whether a website is online, slow, or offline: HTTP status, response time, and the cause of errors such as DNS issues, timeouts, TLS errors, or 5xx responses.
Built by Eric Mager
DNS Lookup
Look up a domain’s A, AAAA, MX, TXT, NS, CNAME, SOA and CAA records, plus Reverse DNS for any IP.
Built by Luca Stanek
WHOIS Lookup
Check a domain's registrar, registration date, expiration date, and nameservers.
Built by Jakub Martyniak
Email DNS Health Checker
Check a domain's SPF, DKIM, DMARC and MX at a glance, with clear guidance.
Built by Jakub Martyniak
SSL Checker
Check an SSL/TLS certificate’s status, issuer, validity period, and expiration date at a glance.
Built by Sebastian Rademacher
Redirect Checker
Check a URL’s redirect chain hop by hop: status codes (301/302/307/308), HTTP headers, server IP, and response time for each redirect.
Built by Luca Stanek
FAQ
Frequently asked questions about the DNS Propagation Checker
Brief answers about DNS propagation, caching, and record types.
For each of the 20 resolvers, the tool shows its current response and whether all responding resolvers agree. Example using the fictional domain example.com shortly after an IP change: 16 resolvers already return the new IP 203.0.113.10 for the A record, 3 still return the old IP 198.51.100.7 from their cache, and 1 does not respond. The result is then “Not fully propagated yet”.
That depends on the TTL (Time to Live) of the previous DNS record—usually between a few minutes and 48 hours. Many resolvers pick up a change much sooner once their cache for that record expires.
Two possible reasons: Either a resolver still has the old response in its cache (it will disappear automatically when the TTL expires), or the domain uses GeoDNS/Anycast (e.g., via Cloudflare). In that case, resolvers in different regions intentionally receive different but valid addresses (EDNS Client Subnet). Both are normal DNS behavior, not errors.
It's usually due to your device's or browser's local DNS cache. Clear it on Windows with ipconfig /flushdns, on macOS with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, or on Linux with systemd-resolved using sudo resolvectl flush-caches. The public resolvers in the tool do not use your local cache.
20 public resolver addresses: two addresses each for Google Public DNS, Cloudflare, Quad9, OpenDNS (Cisco), Level3/CenturyLink and Verisign, plus AdGuard, CleanBrowsing, Deutsche Telekom, Freifunk München, Hurricane Electric, NTT (OCN) Japan, AliDNS and 114DNS. Our server sends queries directly to each resolver's IP address. The listed region refers to the operator, not the location of the query.
Yes. Select the TXT record type and enter the relevant name, such as _dmarc.example.com for DMARC or selector._domainkey.example.com for DKIM. SPF is a TXT record on the domain itself. The tool accepts names with underscores.
Most common causes: The change has not actually been saved at the registrar/DNS provider, the previous TTL has not expired yet, or there is a typo in the domain (in which case all resolvers report “Domain not found”). If in doubt, first check your DNS provider's panel to see whether the change is active there.
Yes, the checker is free and requires no account. To prevent abuse, you can run up to 10 checks per minute per IP address. The button is disabled for a few seconds after each check. Identical checks may be cached for up to 45 seconds.
Any more questions?
Contact SupportDomain, VPS & DNS hosting from one provider
Register or transfer a domain, manage DNS, and run it directly on a ZAP-Hosting server—all in one panel.
No setup. No risk. Online in seconds.
Looking for more tools? View all network tools