DNS propagation checker

Use this DNS propagation checker to compare 21 public resolvers with authoritative answers or an expected value. Review disagreements and follow changes.

Free, no account. Thirty DNS checks per hour. Results are cached for 30 seconds.

A DNS propagation checker compares public resolvers after a DNS change. This tool asks 21 operators for one record type, compares authority or your expected values, and shows TTLs. Its grid groups operators by their base region. Queries come from one server, so countries describe operators rather than regional measurements. Automatic refresh stops after five checks.

How to use this tool

Enter the domain and record type: Use the exact hostname and choose A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV or DS. Use the full service name for SRV. For PTR, enter a public IP. URLs use only the hostname. Each run stops within ten seconds.
Where the expected answer comes from: We ask up to four authoritative name servers. If authority is unavailable, the most common public answer becomes a labelled fallback. You can enter a complete expected value on each line to override the comparison. Unknown responses never count as matches.
Read each row: Each row names the operator, its base country, the returned values, TTL and comparison verdict. Filtering, CDN routing and stale caches can all produce differences. TTL is a cache timer; it does not promise when an answer will change.
Follow and share the query: Optional refresh runs every 30 seconds, up to five additional checks, and stops on hidden pages, edits or failures. A query link fills the form without starting a check or saving results. Copy JSON to keep the answers. Each IP has 30 checks per hour; results are cached for 30 seconds.

Questions before you start

The previous TTL affects how long a cached answer can remain. Resolvers can also serve stale data, filter names or route a CDN differently. This check shows observed answers and cache timers; it cannot predict when every visitor will see a change.

They identify the operator’s base. Most resolvers use anycast, and we query from one API server. We do not run probes in those countries or claim which data centre answered. A visitor on another network may reach a different cache.

Sites behind a content delivery network often give different addresses to different locations, and filtering resolvers block some domains on purpose. In both cases a different answer is expected and waiting will not change it. Check whether your provider answers by location before you treat it as a delay.

Not once the change is made. Before a planned move, lower the TTL to 300 seconds a day ahead, make the change, then raise it again. Google Public DNS and Cloudflare also have public pages where you can ask them to drop their cached copy of a name.

The DNS checker reads eight common types together, compares three public resolvers with authority and explains owner findings. This propagation tool reads one selected type from 21 operators and supports expected values and capped refresh.

Check your business in AI answers

Technical checks help you repair a page. The free AI visibility scan shows the answers checked for your business and what to work on next.

Run the free AI visibility scan

DNS propagation checker

Questions before you start

01How long does DNS propagation take?

02What do the country and region labels mean?

03Why does one resolver return a different address for my site?

04Can I make propagation faster?

05How is this different from the DNS checker?

Check your business in AI answers