Changed a DNS record? See which resolvers around the world already return the new value, which still have the old one, and how long until their cache expires.
| Status | Location | Answer | TTL left |
|---|
Each probe asks its own local resolver, the same way real visitors in that city would. "TTL left" is how long that resolver keeps its cached copy before asking again.
Worldwide checks use the free Globalping probe network by jsDelivr, plus Google and Cloudflare DNS-over-HTTPS.
www or SaaS setup, MX for a new email provider, and NS after moving your DNS to a new provider.The "24–48 hours" rule of thumb is only true for nameserver changes. Most changes are much faster, and the TTL decides.
| What you changed | Typical time | What controls it |
|---|---|---|
| A, AAAA, CNAME, MX or TXT record | 5 min – 1 hour | The old record's TTL (up to 24h if it was set high) |
| New record on a name that didn't exist | Instant – 1 hour | Negative caching (SOA minimum TTL) |
| Nameservers (switching DNS provider) | 24 – 48 hours | TLD registry NS TTL (2 days for .com and .net) |
| Brand-new domain registration | Minutes – a few hours | Registry publishing + negative caching |
| Lowering a TTL | The old TTL | Resolvers keep the old TTL until it expires |
Set the record's TTL to 300 (5 minutes) and wait at least one full old TTL, e.g. 24 hours if it was 86400.
Then make the change. The worst-case wait is now 5 minutes. Raise the TTL back to 3600 or more once you're done.
Millions of users sit behind Google and Cloudflare DNS. Clear their cached copy with Google's Flush Cache tool and Cloudflare's Purge Cache page.
If this checker shows the new value but your browser doesn't, the old record is cached on your device or router.
| Windows | ipconfig /flushdns |
| macOS | sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder |
| Linux (systemd) | resolvectl flush-caches |
| Chrome / Edge | chrome://net-internals/#dns → Clear host cache |
| Router | Restart it — most home routers cache DNS too |
For a normal record change (A, AAAA, CNAME, MX, TXT) it takes as long as the record's old TTL — usually 5 minutes to 1 hour, at most 24 hours with a high TTL. Nameserver changes take longer, typically 24–48 hours, because the TLD registry's NS records are cached for up to two days. A brand-new domain usually resolves within minutes to a few hours.
Your phone on mobile data uses your carrier's DNS resolver, while your Wi-Fi uses your home ISP's resolver (or your router's cache). One of them has already refreshed and the other still has the old record cached. It will fix itself when the old TTL expires. To speed it up on your side, flush your computer's DNS cache and restart the router, or temporarily switch your device to 1.1.1.1 or 8.8.8.8.
If no location returns the new value long after the old TTL, the change probably isn't live at the source. The most common cause is editing DNS at the wrong place: if your domain's nameservers point to Cloudflare, your hosting company or another DNS provider, changes made in your registrar's DNS panel are ignored. Check the NS record type with this tool to see which provider is actually in charge, and make the change there.
Not exactly. Your new record is live at your authoritative nameservers the moment you save it. What takes time is caching: every resolver that looked up the old record keeps it until its TTL runs out, then asks again and gets the new one. 'Propagation' is just thousands of caches expiring at different times — which is why this tool shows the TTL each resolver has left.
Large sites use CDNs and geo-DNS, which deliberately return a nearby server's IP to each region. For those domains, different answers are normal and don't mean propagation is incomplete. Use the Expected value field with your own value to check a specific change.
Those resolvers looked up the name before the record existed and cached the 'does not exist' answer. This is called negative caching. It expires on its own after the time set by your zone's SOA minimum TTL (often 5 minutes to 1 hour). It's common right after creating a new subdomain or registering a domain.
You can't make other ISPs clear their caches, but you can plan ahead: lower the record's TTL to 300 seconds at least one full old-TTL before the change, then make the change. You can also purge Google Public DNS and Cloudflare 1.1.1.1 using their official cache-flush pages, and flush your own device's cache.
Each check asks about 20 probes from the Globalping network spread across North America, Europe, Asia, South America, Oceania and Africa. Each probe queries its own local resolver, typically the ISP or hosting provider's DNS — the same answer a real visitor in that city would get. Google Public DNS and Cloudflare are also queried directly for an instant baseline.
Free tools for network engineers — no signup, no rate-limit walls.