DNS Propagation Checker

Global DNS Checker is a free tool that looks up a domain's DNS records from servers around the world at the same time.

It supports A, AAAA, CNAME, CAA, MX, NS, PTR, SOA, SRV, and TXT records.

Yes. Every tool on the site is free and none of them ask for an account. We only ask that you use the site by hand rather than pointing scripts at it.

Enter the domain in the field at the top of the page, pick a record type, and click "Check DNS". The servers listed below then run the same query and show the answer each one received, along with its response time.

It is governed by the record's TTL, not by a fixed clock.

Resolvers keep serving the previous answer until their cached copy expires, then pick up the new one, so a record with a 300-second TTL updates within about five minutes while a one-day TTL can take up to 24 hours.

The common claim that changes always take 48 hours is a myth left over from slower name servers; lowering the TTL before a change is the real way to speed it up.

Usually it is working and you are just seeing a resolver that still holds the old value in cache until its TTL expires.

Other common causes are a name server change that has not been saved at the registrar, so the delegation still points at the old provider, and negative caching, where a resolver remembers that a name did not exist and keeps returning that until the SOA negative-cache timer runs out.

Checking from several locations shows whether the new value is spreading or genuinely missing.

On Windows, open Command Prompt and run ipconfig /flushdns.

On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

On most Linux systems using systemd-resolved, run sudo resolvectl flush-caches.

Restarting the browser or the device also clears application-level caches. Flushing only affects your own machine; it does not change what other resolvers around the world are serving.

TTL stands for time-to-live: the number of seconds a resolver is allowed to keep a cached DNS answer before it must query the authoritative servers again.

A low TTL means resolvers refresh often, so changes appear quickly but at the cost of more lookups; a high TTL means fewer lookups but slower updates.

Setting a low TTL before a planned change, then raising it afterward, gives fast propagation without permanent overhead.

A DNS check asks resolvers what values a domain's records currently return, such as its A, MX, or TXT records, which is what actually routes traffic and mail.

A WHOIS lookup instead reports registration data about the domain itself: the registrar, creation and expiry dates, and name server delegation.

DNS tells you how the domain behaves right now; WHOIS tells you who registered it and when it expires.

This tool checks a domain from resolvers in many locations at once, so if every server returns the new value, the change has propagated to the resolvers being tested.

Because there are far more resolvers worldwide than any tool can query, a fully consistent result is strong evidence rather than an absolute guarantee.

A mix of old and new answers means propagation is still in progress and some resolvers are holding a cached copy until its TTL expires.

Check the record you changed.

After moving a website to new hosting, check the A record, and the AAAA record if you serve IPv6.

After changing email hosting, check the MX record.

When you move a domain to a new DNS provider, check the NS records.

For domain verification and email policy such as SPF or DKIM, check the TXT record.

If you are unsure, start with A and MX, since those cover most site and mail changes.