DNS Propagation Checker
See where a DNS change has arrived, and when the rest will follow.
Asked from our server in Newark, US · 44 resolvers in 20 countries + your browser
Each check of the same domain and type adds a point. Kept in this browser only, never sent anywhere.
Validating resolvers set the AD flag when they have checked the record’s signatures.
Run a check to read this record’s TTL from its nameserver.
Kept in this browser only, never sent anywhere. Tap one to fill the form.
Every resolver
44 asked by our server in Newark, US · 2 asked by your browser
No resolver matches these filters.
What the DNS propagation checker does
When you change a DNS record, the update doesn’t reach everyone at once. Resolvers that looked up the record earlier keep their cached copy until its TTL runs out. This checker first asks your domain’s own nameserver, which always holds the current record, then asks 44 resolvers from our server in Newark, US: 29 regional resolvers in 20 countries and 15 global anycast services.
Your browser also asks Cloudflare and Google directly over DNS-over-HTTPS, reaching their sites nearest you; those rows say “From your browser”. Use it after pointing a domain at a new host, switching email provider or adding a TXT record.
How to use the DNS propagation checker
- Type a domain and choose one of 12 record types. For PTR, you can type the IP address.
- If you know the value you set, enter it and choose Exact or Contains.
- Under Check from, keep Worldwide, choose Your browser, or ask A resolver by its IP address.
- Press Check, and check again when the countdowns run out.
Understanding the results
Each answer is compared with your nameserver’s, or with your expected value. Updated means it matches. Different means it doesn’t, usually because the old record is still cached there. No answer means no reply in time, or an error such as SERVFAIL.
The countdown beside a different answer is that resolver’s reported TTL, ticking down live; when it ends, the copy expires. Regional resolvers sit in the approximate city shown. Anycast services answer from their site nearest our server, so they’re drawn there, and the browser rows at your approximate location.
The DNSSEC column shows which resolvers say they validated the answer’s signatures. The propagation chart tracks the share of updated resolvers across your checks, kept in this browser only, and the TTL planner uses the record’s TTL to time your next change. A PDF report carries a reference anyone can verify on our site; browser rows aren’t in it, because our server didn’t measure them. Email updates for registered users are coming soon. For every record type at once, use the DNS lookup.
DNS propagation questions
How long does DNS propagation take?
Usually as long as the old record’s TTL: from a few minutes to a day. Lowering the TTL a day before a change makes the switch faster.
Why do resolvers show different addresses for big sites?
Large sites and CDNs give each resolver nearby addresses. When the name is an alias (CNAME), we compare the alias itself, the part you control.
What if my nameserver doesn’t answer?
Then the answer most resolvers give becomes the reference, and the page says so. Check that your nameservers are online and hold the zone.
My own computer still shows the old site. Why?
Your device, browser and router keep DNS answers too, and your provider’s resolver may not be on our list. Reconnecting to your network often clears a stale copy.