Skip to content

DNS propagation

See where your DNS records have propagated

Query public resolvers across 40 locations worldwide and watch each answer arrive live. No invented data, no fake global grid.

Match answers against an expected value

Resolvers

Resolved

No answer

Progress

Answers by resolver

of responded

Resolver locations

·

Server location
Resolved
Not resolved
Not checked

Check a resolver you trust

Add any public resolver to the list and query it alongside the defaults.

Full propagation can take up to 48 hours to reach every resolver worldwide.

How this works

  1. 1 Query in parallel Every resolver is asked directly from this server, five at a time.
  2. 2 Show the raw answer Records appear exactly as returned, with a timestamp-free response and the latency we measured.
  3. 3 Flag what did not answer Empty and failed responses stay visible instead of being hidden.

DNS propagation

How to check DNS propagation globally

After you change DNS records, switch hosts, or launch a new site, resolvers around the world keep serving cached answers until their TTL expires. dnscheckers.org queries public resolvers from this server so you can see exactly what each one returns right now.

Check propagation in three steps

  1. 01

    Enter the domain

    Type the hostname you changed, such as example.com.

  2. 02

    Pick the record type

    Choose the record you are verifying: A, AAAA, MX, TXT, NS, or any other supported type.

  3. 03

    Compare the answers

    Every resolver is queried in parallel. Records that have not caught up stay visible instead of being hidden.

Record types we support

All standard record types are available for lookup and propagation checks.

A

Maps a hostname to an IPv4 address, for example 192.0.2.1.

AAAA

Maps a hostname to an IPv6 address, for example 2001:db8::1.

CNAME

An alias that points one hostname at another.

MX

Mail exchange servers and their routing priority.

NS

The authoritative nameservers delegated for the zone.

PTR

Reverse DNS, mapping an IP address back to a hostname.

TXT

Free text used for SPF, DKIM, DMARC and ownership proofs.

SOA

Start of authority: the zone’s administrative record.

CAA, DS, DNSKEY

Certificate authority rules and DNSSEC signing keys.

Reading the results

Each resolver row reports one of four states, and the state is never carried by colour alone.

Resolved

The resolver returned records matching your query or expected value.

Not resolved

Records are stale, or the resolver returned no answer for this type.

Not checked

Queued or idle: no query has been sent to this resolver yet.

Checking

A query is in flight and the answer has not arrived yet.

A resolver still showing old records usually just means its cache has not reached the record’s TTL yet. Full global propagation can take up to 48 hours.

Checking a resolver of your own

If you want to test against a resolver that is not in the default list, choose Add a custom resolver above and supply its label, IP address, provider, and map coordinates. It is then queried alongside the defaults, and you can optionally contribute it to the public list.

Frequently asked questions

Quick answers about propagation, resolvers, and how this checker works.

What is DNS propagation? +

DNS propagation is the time it takes for updated DNS records to appear consistently across recursive resolvers worldwide after you change nameservers or records at your DNS host.

Why do resolvers show different answers? +

Each public resolver caches answers independently based on TTL and prior queries. DNS Checkers queries those resolvers from this server so you can compare what they currently return.

Does DNS Checkers probe 100 countries? +

No. We query well-known public resolver IPs and authoritative nameservers from this application server. Labels are honest: this is not a multi-VPS global grid.

Which record types can I check? +

A, AAAA, CNAME, MX, NS, PTR, SRV, SOA, TXT, CAA, DS, and DNSKEY.

What does the expected value filter do? +

Exact, contains, and regexp filters highlight matching answers client-side so you can spot whether a change has reached each resolver.

Can I add my own DNS server? +

Yes. Add a custom public resolver name and IP for the current browser session. Private and metadata IPs are blocked for security.

Add a custom resolver

DNS Checkers uses essential cookies to run. Optional advertising cookies (Google AdSense) load only if you accept. See the Cookie Policy and Privacy Policy.