Free tool

DNS propagation checker

Changed a DNS record? See whether eight public resolvers return the new value yet, compared with the answer from your domain's own nameservers.

Record type

Enter a domain, pick a record type and compare 8 public resolvers with its own nameservers.

What this checker compares

First it finds your domain's authoritative nameservers, the servers that hold the real records, and asks them for the record you chose. That answer is the target: it is what every resolver will return once the change has spread.

Then it asks eight public resolvers at the same moment: Google Public DNS, Cloudflare, Quad9, Cisco OpenDNS, AdGuard DNS, Control D, Lumen (Level 3) and DNS.SB. Each row shows the answer that resolver gives and whether it matches your nameservers.

It checks A, AAAA, CNAME, MX, TXT and NS records. If your nameservers answer with an alias (a CNAME to another domain), resolvers are compared with each other instead, and the page says so.

Reading the result

Fully propagated means every resolver already returns the new answer. Partly propagated means some still hold the old one: they will catch up once their cached copy expires, which can take as long as the record's TTL. Not propagated means none have refreshed yet, which is normal in the first minutes after a change.

If your nameservers themselves show the old value, the change has not been saved at your DNS provider, and no amount of waiting will help: check the record in your DNS host's control panel.

Watch your DNS records automatically

A record that changes when nobody meant it to can take a website or its email offline. PulseStack™ DNS monitoring checks your records on a schedule and alerts you the moment one stops matching the value you expect.

For a one-off look at every record type, use the DNS lookup tool, or check mail records with the MX lookup.

How to use this tool

STEP 1

Enter a domain

Type the name you changed, such as example.com or www.example.com.

STEP 2

Pick the record type

A for website addresses, MX for mail, TXT for verification and email security, NS for nameservers.

STEP 3

Run the check

We ask your nameservers and eight public resolvers at the same moment.

STEP 4

Compare

Matches show where the change has arrived; differences show caches still holding the old value.

Frequently asked questions

What is DNS propagation?+

When you change a DNS record, the change is live on your domain's nameservers straight away, but resolvers around the internet have cached the old answer. Each one keeps it until its time to live (TTL) runs out, then asks again and gets the new value. Propagation is simply those caches expiring, one resolver at a time.

How long does DNS propagation take?+

For an ordinary record change, up to the record's previous TTL: often five minutes to an hour, sometimes a day. Changing the nameservers for a whole domain usually takes longer, up to 48 hours, because the registry's delegation records are cached for longer.

Why do resolvers show different answers?+

Each resolver cached the record at a different moment, so each one expires and refreshes it at a different time. Resolvers that show the old value have not refreshed yet. Sites behind a content delivery network or location-based routing can also give different addresses to different resolvers on purpose; that is not a propagation problem, which is why aliases are compared rather than the addresses behind them. For A and AAAA records, the time shown under each answer is how much longer that resolver will keep its current copy.

Does this check from different countries?+

No. Every query is sent from our server in the UK to the resolvers listed and to your domain's own nameservers. Large public resolvers run many sites and answer from the nearest one, so the results show what those networks return here. Caches in other regions can differ for a short time.

How can I make a DNS change take effect faster?+

Lower the record's TTL, for example to 300 seconds, a day before a planned change, then make the change and raise the TTL again afterwards. You cannot clear other people's caches, but you can clear your own: run ipconfig /flushdns on Windows, or restart your router, and try again.

Can PulseStack™ alert me if a DNS record changes?+

Yes. DNS monitors, included from the Starter plan at £9 a month, check a record as often as every five minutes and alert you when it stops matching the value you expect, which catches hijacked or mistakenly edited records. Every paid plan starts with a 14-day free trial with no card needed.

More free tools

Every one runs a real check, live, with nothing to install.

Know when a DNS record changes

PulseStack™ DNS monitors check your records as often as every five minutes and alert you the moment one changes. Included with every paid plan from £9 a month; the Free plan covers 25 website monitors with no card required.