Skip to main content
DNS Tools

DNS Propagation Checker

Check if a DNS change - new host, nameservers or email records - is already visible on the internet's major public resolvers.

Refresh Result
Checks whether major global DNS resolvers agree on this domain's A record yet.
Not sure what to enter? Try an example: google.com
Free & instant No signup How to use FAQ
Still Propagating / Inconsistent

google.com (A)

2 of 3 resolvers returned an answer.

Google (8.8.8.8)
Resolved
  • 142.251.126.100
  • 142.251.126.139
  • 142.251.126.101
  • 142.251.126.102
  • 142.251.126.113
  • 142.251.126.138
Cloudflare (1.1.1.1)
Resolved
  • 192.178.211.100
  • 192.178.211.101
  • 192.178.211.138
  • 192.178.211.113
  • 192.178.211.102
  • 192.178.211.139
Quad9 (9.9.9.9)
Unreachable

HTTP 505

Last checked: 0 seconds ago Live
Download JSON Download PDF

Enter a domain to ask several large public DNS resolvers what they currently return, so you can see whether your latest change has spread.

What is DNS propagation?

When you change a DNS record, resolvers around the world keep serving the old value until its cached copy expires (its TTL). DNS propagation is that transition period. This checker asks several major public resolvers for the record and shows whether they already return the new value.

How to check DNS propagation

  1. Enter the domain you updated in the box above.
  2. Click Check Propagation.
  3. Compare the answers from each resolver - matching values mean the change has spread.
  4. If some still show the old value, wait for the old TTL to pass and check again.

Related checks

  • To see how long the old value may be cached, use the TTL Checker.
  • To view the full set of records, use the DNS Lookup.

Different answers across resolvers are normal for a few hours after a change and settle as cached copies expire. Lower the TTL a day before your next planned move, and let JustChecker confirm when the new record is live everywhere.

Frequently Asked Questions

Most changes appear within minutes to a few hours; nameserver changes can take up to 24-48 hours. The old record's TTL decides how long resolvers may keep the previous value.

No, that is what propagation in progress looks like. Each resolver refreshes when its cached copy expires. Check again later; once all show the same value, the change is complete.

A day before a planned move, lower the TTL of the records you will change (for example to 300 seconds). Resolvers then refresh quickly, and you can raise the TTL again afterwards.
Share this tool:
Need a website for your business? Only $599