Support
We usually reply within 1–2 business days
✅
Ticket submitted!
Your ticket ID:
A confirmation has been sent to your email address.
DNS Propagation Checker — Test DNS Across 12 Global Resolvers | TestURL.live
DNS

DNS Propagation Checker — See Your DNS Update Worldwide, In Real Time

Query 12 global anycast DNS resolvers in parallel and see exactly which ones have picked up your record change — perfect for verifying a DNS cutover landed everywhere it should.

Just finished a server migration?

Before you change DNS, test the new server with a preview URL — confirm the site works, then propagate.

Test Your Migration →

What This DNS Checker Does

When you update a DNS record (e.g. pointing yourdomain.com from old hosting IP to new), the change has to propagate through the worldwide network of caching resolvers before all your visitors see it. This tool queries 12 public anycast resolvers in parallel and returns each one's answer — so you can see exactly where your update has landed and where it's still serving the old value.

Each resolver is queried directly via dig with a short 3-second timeout. Results are independent — one slow or unresponsive resolver doesn't hold up the others. You'll typically see all twelve answers in under 5 seconds.

Resolvers Queried

Google DNS

8.8.8.8 and 8.8.4.4 — the most-used public resolvers worldwide.

Cloudflare

1.1.1.1 and 1.0.0.1 — privacy-focused, very fast.

Quad9

9.9.9.9 — Switzerland-based, security-filtered.

OpenDNS

208.67.222.222 — Cisco-owned, widely used in enterprise.

Level3

4.2.2.1 — backbone resolver, US carrier-grade.

Yandex

77.88.8.8 — primary resolver for much of Eastern Europe.

Plus Comodo, AdGuard, DNS.WATCH, and NextDNS for full coverage.

DNS Propagation FAQ

What is DNS propagation?

The time it takes for an update to your DNS records to spread across the network of DNS resolvers used worldwide. Different resolvers honour your record's TTL differently, so a change can be visible to some users immediately and to others up to 24 hours later.

How long does DNS propagation take?

For most records, between a few minutes and 24 hours, depending on the TTL of the previous record. Lowering the TTL to 300 seconds a day or two before a planned change shortens the propagation window significantly.

Why do different resolvers return different answers?

Each resolver caches your record according to its TTL. A resolver that fetched the old record 23 hours ago with a 24-hour TTL still has 1 hour of stale cache to burn through. That's normal — and exactly what this tool is designed to surface.

What's the difference between A, AAAA, CNAME, MX, NS, and TXT?

A maps a domain to an IPv4 address. AAAA maps it to an IPv6 address. CNAME aliases one domain to another. MX defines mail servers. NS defines the authoritative nameservers. TXT holds arbitrary text — most often SPF, DKIM, DMARC, or domain-verification records.

Related Tools

SSL CheckerVerify the new cert after DNS lands Redirect Chain CheckerTrace every redirect hop HTTP Headers ViewerSee raw response headers Security Headers CheckerAudit HSTS, CSP, X-Frame