DNS propagation checker
Check whether a DNS change has reached 15 public resolvers, compare each answer with the value you expect, or look up every record for a domain.
Ready when you are
Ready when you are
Enter the details above to run a free check.
Monitor your site
Run continuous uptime checks instead of a one-time website status test. See its first check free, then try a paid plan for 7 days (card required) or subscribe now.
Start 7-day trialHow this check works
Enter a public address
Use a public website or domain. You do not need an account to run a check.
Read the evidence
The result shows what this check measured. Use the details to decide what to investigate next.
Keep watching
One check is a snapshot. Monitoring repeats uptime and SSL checks and alerts you when something changes.
ttl and caching
Why propagation isn't instant.
troubleshooting
What to do if one resolver is wrong.
- Check the authoritative row first. If the authoritative nameserver still returns the old value, the change was not saved, or it was made at a DNS provider that does not serve this domain. Compare the NS records with the provider you edited.
- Look at the TTL in the lagging row. It is the time left before that resolver asks again. Re-check after it runs out.
- Rule out answers that differ on purpose. CDNs and large sites return different addresses by location. Enter the value you set as the expected value to test your change rather than their routing.
- Purge where you can. Google Public DNS and Cloudflare have public cache purge pages for their resolvers. ISP resolvers cannot be purged from outside; they refresh when the TTL ends.
resolvers
The 15 resolvers this checker asks.
Every query goes over encrypted DNS (DNS over HTTPS) from our server. Anycast networks answer from their site nearest to that server, so each row shows the resolver and its operator, not a city. The authoritative nameserver is queried directly as the reference.
- Google Public DNS · Google, US (anycast)
- Cloudflare 1.1.1.1 · Cloudflare, US (anycast)
- Quad9 · Quad9 Foundation, Switzerland (anycast)
- OpenDNS · Cisco, US (anycast)
- AdGuard DNS · AdGuard, Cyprus (anycast)
- NextDNS · NextDNS, US (anycast)
- Control D · Control D, Canada (anycast)
- DNS4EU · DNS4EU consortium, EU
- CZ.NIC ODVR · CZ.NIC registry, Czech Republic
- SWITCH · SWITCH research network, Switzerland
- CIRA Canadian Shield · CIRA registry, Canada
- Xfinity · Comcast (ISP), US
- Hurricane Electric · Hurricane Electric (network), US
- IIJ Public DNS · IIJ (ISP), Japan
- AliDNS · Alibaba Cloud, China
faq
DNS propagation questions, answered.
What is DNS propagation?
DNS propagation is the time it takes for a DNS change to reach everyone. Your DNS provider updates the record at once, but recursive resolvers run by ISPs, companies and public services keep the old answer cached until its TTL (time to live) runs out. Until then, some visitors reach the old value and some the new one.
How long does DNS propagation really take?
For most record changes, as long as the TTL the old record had: 300 seconds means about 5 minutes, 3600 means about an hour. A few resolvers keep answers longer than the TTL, so allow up to a day before calling a change broken. Nameserver changes at the registrar take longer, often up to 48 hours, because the parent zone NS records usually have long TTLs.
How do I know if my DNS has propagated?
Enter the domain above, choose the record type and paste the new value into Expected value. The checker asks every public resolver in the list and marks each one that already returns it, with a percentage. When every resolver that answered shows a match, the change has reached them. Without an expected value, answers are compared with the domain’s authoritative nameserver.
Why isn't my DNS propagating?
The most common causes are: the change was made at a DNS provider that is not authoritative for the domain (check the NS records), the old record had a long TTL that has not expired yet, a typo in the new value, or a missing trailing record such as www. If the authoritative nameserver already returns the new value but resolvers do not, it is caching and will clear on its own.
How can I speed up DNS propagation?
Lower the TTL of the record a day or more before the change (for example to 300 seconds), wait for the old TTL to pass, then make the change. After the change you cannot force other resolvers to drop their cache, although Google Public DNS and Cloudflare offer public cache purge pages for their own resolvers. Raise the TTL again once the new value is everywhere.
next checks
Related checks.
Website status checker
Once DNS points to the new server, confirm the site answers from outside your network.
SSL certificate checker
After a move, check that the new server presents a valid certificate for the hostname.
Domain expiry checker
Records stop resolving when the registration lapses. Check the expiry date and registrar.
DNS monitoring
Scheduled DNS snapshots with alerts when a monitored record changes.
Get alerted when records change
Solo ($15/month) and higher record A, AAAA, MX, CNAME, TXT and NS records of monitored sites every six hours and alert you when a snapshot differs.