DNS Tools

DNS Propagation Checker

Check whether a domain's DNS changes have propagated across major global resolvers yet.

Enter a domain below to check whether its DNS changes have propagated across major global DNS resolvers (Google, Cloudflare, Quad9) yet.

Checks whether major global DNS resolvers agree on this domain's A record yet.

More DNS Tools

View all 12

SOA Record Lookup CAA Record Lookup CNAME Lookup SRV Record Lookup TXT Record Lookup DNSSEC Checker MX Record Lookup TTL Checker

JustChecker tracks your DNS records continuously and alerts you the moment something changes.

What Is the DNS Propagation Checker?

After you change a DNS record, resolvers around the world keep serving the old value until their cached copy expires. This tool asks three major public resolvers - Google (8.8.8.8), Cloudflare (1.1.1.1) and Quad9 (9.9.9.9) - for the record and shows whether they already return the new value.

When to Use It

Right after pointing a domain to a new server.
When the change works for you but not for someone else.
Before cancelling an old hosting account, to be sure traffic has moved.

How to Use It

Enter the domain.
Compare the answers from each resolver.

Understanding the Result

When all resolvers return the same new value, the change is visible to most of the internet. Different answers mean some caches still hold the old record; they update once the old record's TTL expires.

Limitations

Three resolvers are a good sample, not every network - ISPs and company networks run their own caches. Lowering the TTL a day before a planned change makes propagation faster; check it with the TTL Checker.

Frequently Asked Questions

When you change a DNS record (like your A record), that change has to spread across DNS resolvers and caches around the world before every visitor sees it. This process is called propagation, and it can take anywhere from a few minutes to 48 hours depending on TTL settings and resolver caching.

Each DNS resolver caches records independently based on the TTL (time to live) you set. A resolver that queried your domain recently may still be serving the old, cached value until that TTL expires.

Lower your DNS record's TTL value before making a change (e.g. to 300 seconds), wait for the old TTL to fully expire, make your change, then raise the TTL back once propagation is confirmed.

No - this tool only checks whether DNS resolvers agree on your current record. Use our Website Status Checker to check if your site is actually up and responding.