{{ error }}
#ResolverResponse
{{ i+1 }} {{ row.resolver }} {{ row.answer }}
Categories: DNS , Networking
Export to PDF Fullscreen

Domain Name System (DNS) propagation describes the period between updating a DNS record and its visibility across the internet. During propagation, authoritative information gradually replaces outdated entries cached by recursive resolvers worldwide. Understanding this delay helps you anticipate how soon users will reach your new server, email host, or verification target.

The Global DNS Propagation Checker lets you observe that process in real time. It queries several public DNS-over-HTTPS resolvers for A, AAAA, CNAME, MX, and TXT records, then displays their current answers side by side. Comparing these responses highlights where propagation has completed and where caches still deliver previous values.

By confirming propagation status, you can schedule cut-overs confidently, validate email configurations, and streamline troubleshooting. Instant visual feedback alerts you to mismatched records before customers notice downtime. Because lookups run entirely in your browser and only contact the chosen resolvers, the tool safeguards privacy and security while accelerating your deployment workflow.

Technical Details:

This section outlines the key capabilities that drive accurate, dependable lookups.

  • DNS-over-HTTPS requests secure each query against interception.
  • Three globally distributed resolvers: Cloudflare, Google Public DNS, and DNS.SB.
  • Supports A, AAAA, CNAME, MX, and TXT record types.
  • Instant in-browser updates without page reloads.
  • Automatic re-check when you modify the domain or record type.
  • Em dash (—) marks unanswered queries for fast fault spotting.
  • All processing happens locally; no logs are retained.

Step-by-Step Guide:

Follow these steps to test record visibility across resolvers.

  1. Click in the Domain field and type the fully qualified hostname. Tip
  2. Select the required record type from the drop-down list.
  3. Press Check to start the lookup.
  4. Watch the spinner until the query completes.
  5. Review answers in the results table; mismatches are highlighted. Caution
  6. If records differ, update your DNS provider, wait, then repeat the test.

FAQ:

Find quick answers to common questions.

Why do different resolvers show different answers? DNS servers cache records for the duration of their TTL. A resolver that has not yet refreshed its cache will continue to serve the previous answer until the timer expires.
How often should I refresh the test? Refresh whenever you change the record or when the TTL interval has likely passed. Frequent checks during propagation help confirm when every resolver has updated.
Does this tool send my query to your server? No. Lookups run fully in your browser and are sent only to the chosen public resolvers; nothing is transmitted to or stored by simplified.tools.
What does the em dash (—) mean in the results table? The em dash indicates that the resolver returned no answer or that the request failed. It helps you spot incomplete propagation or resolver-specific issues quickly.
Will resolver answers match users worldwide? They usually do, but local networks or enterprise DNS filters can override public resolver data. Test several resolvers for a representative picture of global visibility.

No data is transmitted or stored server-side.

Embed this tool into your website using the following code: