Just changed a DNS record? Check in seconds whether 20+ DNS resolvers around the world are serving the new value or the old cached one.
See what 20+ DNS resolvers around the world are returning, right now
20 free checks per day · no signup · results in ~4 seconds
Querying public DNS resolvers across Europe, Asia, Americas, Oceania...
Results for
Most common answer
No resolvers returned an answer. The record may not exist, or DNS may not have propagated yet.
Get alerted the moment a DNS record changes
TLDTrack monitors DNS on every domain you own and pings you if anything moves, expected or not.
When you change a DNS record, the new value rolls out as old cached copies expire on each resolver. This tool asks 20+ resolvers around the world what they're seeing right now so you can spot stragglers.
20+ public resolvers
Cloudflare, Google, Quad9, OpenDNS, Verisign, Yandex, DNSPod, AdGuard and more. Spread across the Americas, Europe, Asia, Oceania and Africa.
Every record type
A, AAAA, CNAME, MX, NS, TXT, SOA and CAA. Switch the type at the top of the form and re-run, the resolvers requery in parallel.
Consensus highlighting
We pick the most common answer across all responding resolvers, then flag any resolver returning something different so you can see exactly where the old record is still cached.
Fast, in parallel
All 20+ queries fire at once and complete within seconds. No waiting through resolvers one at a time like some other tools.
After a DNS edit
You changed an A record or moved nameservers and want to confirm the new value is live globally before users notice.
Migrations
Moving a site between hosts or registrars. Stragglers can keep sending traffic to the old IP for hours, or days, after the change.
Debugging
"It works for me but not for them" is often a stale DNS cache somewhere. This tool shows you which resolver is the problem.
A one-off check is a snapshot. TLDTrack watches every record on every domain you own and alerts you the moment a value moves, whether you made the change or not.
7 days free · cancel anytime
It depends on the TTL of the record before you changed it. If TTL was 300 seconds, most resolvers update within ~5 minutes. If TTL was 86400 (24h), some caches can take a full day to expire. Nameserver changes at the registrar level can take 24-48 hours.
Cloudflare (1.1.1.1), Google (8.8.8.8), Quad9 (9.9.9.9), OpenDNS, Verisign, Level3, DNS.WATCH (Germany), Yandex (Russia), Freenom (Netherlands), AdGuard, SafeDNS, CleanBrowsing, 114DNS and DNSPod (China), Telstra (Australia), NIDA (Korea), UOL (Brazil), TENET (South Africa) and more, around 20 in total.
That resolver still has the old record cached and hasn't hit its TTL expiry yet. Either wait for the cache to expire, or, if it's your own machine, flush your local DNS cache. You can't force public resolvers to flush.
Same idea, just across many resolvers at once and rendered visually. Under the hood we shell out to dig with +short.
No. Anonymous one-off checks are not stored against an account. We may keep aggregate counts for service quality and abuse protection.
All features overview
Every check TLDTrack runs and what it costs.
For small business
Plain-English website monitoring for non-technical owners.
For agencies
Manage every client domain in one dashboard.
TLDTrack vs UptimeRobot
Honest feature-by-feature comparison.
Free email deliverability
Free SPF / DKIM / DMARC checker, no signup.
iOS & Android apps
Push alerts the moment something breaks.
This action cannot be undone.