DNS propagation checker
A DNS propagation checker shows whether a DNS change has reached public resolvers. This free tool compares a hostname's A and AAAA records across four fixed resolvers: the WebJi® server, Cloudflare, Google and Quad9. Matching rows mean those caches hold the new address; a mismatch usually means an old TTL has not expired yet.
For anyone who has just changed hosting, name servers or an A record and wants to know whether visitors now reach the new server.
needed
- Price
- Free
- Signup
- None
- Built by
- WebJi®
- Support
- 24/7 email
Last editorial update: 14 November 2026.
How do you check DNS propagation with this tool?
Enter one hostname and run the check: the tool fetches its A and AAAA records from four resolvers, this server, Cloudflare, Google and Quad9, and says whether all four returned the same addresses. The resolvers are fixed; text you type is only ever treated as the hostname to look up, never as a resolver address.
- Enter one hostname, such as example.com or www.example.com. An IP address is rejected.
- Read the A (IPv4) and AAAA (IPv6) lines for local, Cloudflare, Google and Quad9.
- If any lookup failed, treat that row as incomplete. The tool never reports agreement when a lookup has failed.
- If the sets differ, wait out the TTL and check again before changing more records.
Which resolvers does the DNS propagation checker compare?
The checker compares the resolver on the WebJi® server with three public resolvers queried over DNS-over-HTTPS: Cloudflare, Google Public DNS and Quad9. Agreement is reported only when every lookup succeeded and all four returned identical A and AAAA sets.
| Row | Resolver | How it is queried |
|---|---|---|
| local | The WebJi® server's own resolver | Standard system lookup |
| cloudflare | Cloudflare 1.1.1.1 | DNS-over-HTTPS, JSON (cloudflare-dns.com) |
| Google Public DNS 8.8.8.8 | DNS-over-HTTPS, JSON (dns.google) | |
| quad9 | Quad9 9.9.9.9 | DNS-over-HTTPS, wire format (dns.quad9.net) |
The three public services are anycast networks, so each answer comes from the node nearest the WebJi® server, not from every country. Four matching rows are strong evidence that large public caches have the new value; they are not proof that every ISP and home router has updated.
Which DNS records does the propagation check cover?
Only A and AAAA records are compared; CNAME, MX, NS and TXT are not queried here and belong in the DNS lookup tool. That keeps the result focused on the question most migrations ask: which server does this name point to now?
| Record | What this checker does |
|---|---|
| A | Compared across local, Cloudflare, Google and Quad9 |
| AAAA | Compared the same way; an empty list is a valid answer when every resolver is empty |
| CNAME | Not queried; follow aliases with the DNS lookup |
| MX | Not queried; use the MX record lookup for mail routing |
| NS | Not queried; name servers show who serves DNS, not where the site lives |
| TXT | Not queried; SPF and verification strings stay on the DNS lookup |
Why does DNS propagation take minutes for some changes and up to two days for others?
Propagation time equals the TTL of whichever record changed: an A-record edit clears when your own TTL expires, while a name-server change waits on the TTL the registry publishes for the delegation. That registry TTL differs sharply by extension.
| Extension | Registry NS TTL | Worst-case wait after a name-server change |
|---|---|---|
| .com | 172,800 seconds | About 48 hours |
| .in | 900 seconds | About 15 minutes at the registry, plus your own record TTLs |
This is why some ISP resolvers keep showing the old IP for 24–48 hours after a .com name-server move, while a .in domain can switch far sooner. A mismatch here is a cache, not a second website, and flushing your own computer does not flush your ISP. The explainer on how long DNS propagation takes covers the waiting period in detail.
How do you lower DNS TTL before moving a live website?
Cut the TTL on the records you will change a day or two before the move, wait at least the old TTL, then switch and confirm with this checker. Changing only the A record, not the name servers, avoids the registry delay altogether.
- Note the current TTL on the A and AAAA records you plan to change.
- Set a short TTL, such as 300 seconds, and wait at least as long as the old value.
- Change the address or the name servers, not both at once, and run this check.
- Raise the TTL again only after all four resolvers agree and the site loads from the new host.
The guide to pointing a domain to hosting compares the A-record and name-server routes, and WebJi®'s website migration service can plan the cutover for you.
Frequently asked questions
All four resolvers agree, but my office still sees the old site. Why?
Your office router or ISP resolver still holds a cached copy until its TTL ends. Flush the local cache, try mobile data, or set the computer to use 1.1.1.1 or 8.8.8.8 temporarily; the stale copy disappears on its own once the timer runs out.
Can I add my own resolver to the check?
No. The four resolvers are fixed so the tool cannot be used to send queries to arbitrary servers. To test a particular resolver, run dig @resolver-ip example.com A or nslookup example.com resolver-ip from your own machine.
Why does only the local row differ?
The WebJi® server's resolver may have cached the old answer slightly longer than the public resolvers, or it may sit behind a different network path. If the three public rows agree with the new address, the change is live at the source.
Does Cloudflare's orange-cloud proxy affect this result?
Yes. A proxied record returns Cloudflare's edge addresses, not your origin server's IP, so every resolver shows Cloudflare IPs. That is expected; check the origin address in the Cloudflare dashboard instead.
Should I change name servers or the A record when moving host?
Change the A record when you want speed and control, because it follows your own TTL. Change name servers when the new host will manage all DNS, and allow for the registry's delegation TTL, which is 48 hours for .com.
Resolver behaviour and registry TTLs checked 14 November 2026 · Reviewed by the WebJi® team, Jaipur.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.