DNS Propagation Checker

Kutafuta - tafuta tovuti ya kituo fulani,

How to use this tool

1

Enter a domain

Type the domain whose DNS change you want to track — the root domain like example.com.

2

Query global resolvers

ns6 asks several public resolvers around the world — Google, Cloudflare, Quad9 and more — for the record at the same moment.

3

Compare the answers

If every resolver returns the same value, your change has fully propagated. If they disagree, some are still serving the old cached record.

4

Wait and re-check

Propagation follows the record’s TTL and can take minutes to 48 hours. Re-run the check until every resolver agrees.

When you change a DNS record — moving your site to a new host, updating an MX record, or adding a verification TXT — the change doesn’t reach everyone at once. Resolvers around the world cache the old value until it expires, so for a while some visitors see the new record and others still see the old one. That in-between state is called propagation.

This checker queries several major public resolvers at the same time and compares their answers. When they all return the same value, your change has propagated everywhere; when they differ, some resolvers are still serving a cached copy. How long it takes depends on the record’s TTL, which you set at your DNS host.

Frequently asked questions

It’s the time it takes for a DNS change to reach resolvers everywhere. Until it finishes, some resolvers still serve the old cached record while others have the new one.

It asks several major public resolvers — Google, Cloudflare, Quad9, OpenDNS and more — for the same record at once, then compares their answers. Matching answers mean the change has propagated.

Each resolver caches records for the length of their TTL. If you changed a record recently, resolvers that cached the old value keep serving it until their cache expires.

Usually minutes to a few hours, but it can take up to 24–48 hours. It depends on the record’s TTL and how aggressively resolvers along the path cache it.

Lower the record’s TTL before you make a change, so resolvers cache it for less time. If you forgot, you can only wait for the existing caches to expire.