DNS Propagation Checker |
A DNS propagation checker shows which answer people get for your domain in different countries, so you can see whether a DNS change is live everywhere. Each answer is compared with what your own DNS servers publish now.
What Is DNS Propagation?
Nothing travels: your new record is live on your DNS servers at once, but resolvers around the world keep the old answer until its TTL runs out.
When someone opens your site, their resolver (usually their ISP's, or Google's, Cloudflare's…) asks your DNS servers once, then reuses the answer for as long as its TTL says, for example one hour. Change the record and a resolver that asked 10 minutes ago keeps the old answer for 50 more minutes. "Propagation" is all those caches expiring, each on its own clock. That's why a change can be live in one country and not yet in another.
| Status here | Meaning |
|---|---|
| Up to date | Same answer as your DNS servers publish now |
| Different | An old cached answer (it expires within the TTL shown), or a provider that answers differently by location, such as a CDN |
| No record | That resolver has no record of this type, or the name doesn't exist there yet (often a cached "doesn't exist" for a brand-new name) |
| No answer | The probe or its resolver didn't answer in time |
How to Make DNS Changes Go Live Faster
Lower the TTL a day before the change, make the change, then raise the TTL again.
- A day ahead (or at least one old TTL ahead), set the record's TTL to 300 seconds.
- Make the change. Resolvers now keep old answers for at most 5 minutes.
- Check here until every probe is up to date, then set the TTL back (3,600 seconds or more) to reduce DNS traffic.
- Moving to a new DNS host (changing name servers)? That change is cached by the TLD's servers too, often for up to two days: keep both hosts serving the same records meanwhile.
How This Propagation Check Works
| Probes | One probe in each of about 20 countries on 6 continents, from a third-party network of volunteer-run probes; a country without a free probe is left out |
| Resolver | Each probe asks its own local resolver (usually its ISP's), so you see what people there see |
| Reference | Your domain's authoritative servers, asked directly from our server without cache. When they answer with an alias (CNAME), probes are compared on the alias, because the final addresses often differ by country |
| TTL left | The remaining cache time each resolver reports for its answer |
| Runs in | Your browser, which talks to the probe network directly: it sees your IP and the domain. It allows 250 probe tests per hour per connection (one check uses about 20) |
| What we keep | Nothing: we only answer the authoritative lookup, and don't save it. Our server and Cloudflare keep standard access logs. |
Last verified 12 November 2026.
Frequently Asked Questions
How long does DNS propagation take?
Why do some countries still show my old IP?
Can I speed up DNS propagation?
ipconfig /flushdns on
Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on a Mac.
Is this a real worldwide check?
Put this guide into practice