Clear, practical technology insightsExecution and privacy scope shown per tool
TMTipsMake
Home›Utility Lab›DNS Propagation Checker
🌍 Compare DNS answers across resolvers

DNS Propagation Checker

Compare DNS answers from multiple configured public resolvers to see whether they currently agree after a DNS record change.

Updated July 25, 2026✓ Free to useExternal data lookup
🌍 External data lookup · Provider results may be used

Use the DNS Propagation Checker

External-dataThe lookup may use external resolver or IP data providers. Results reflect the providers and server location used.
About this utility

How does the DNS Propagation Checker work?

DNS Propagation Checker performs a server-side DNS check because browser JavaScript cannot directly reproduce a full resolver query from the TipsMake server environment. Enter a public hostname and record type you recently changed or want to compare.

The utility reports the answers returned by each configured resolver, shown separately. Compare the answer with your authoritative DNS configuration and other resolvers when troubleshooting. Resolver agreement is not proof of worldwide propagation. Caches, TTLs, anycast routing, geography, and resolver policy can produce different answers.

Provider-backed data

Use configured external data sources when the requested information is not available locally.

Useful network context

Present provider or resolver results in a form that supports troubleshooting and research.

Accuracy caveat

Keep approximate or resolver-dependent fields clearly separated from hard facts.

Best practices

How to get a useful DNS Propagation Checker result

  1. Use a public hostname you control or are authorized to troubleshoot and enter a public hostname and record type you recently changed or want to compare.
  2. Check the authoritative DNS provider or zone file so you know what answer you expect.
  3. Consider TTL and resolver caching before treating a different answer as an error.
  4. Repeat from another resolver or location when users in different networks report different DNS behavior.

Important: Resolver agreement is not proof of worldwide propagation. Caches, TTLs, anycast routing, geography, and resolver policy can produce different answers.

Common use cases

When to use the DNS Propagation Checker

DNS migrationsCompare resolver answers after moving a domain to a new server.
Nameserver changesSee whether configured resolvers return consistent public records.
TTL troubleshootingCheck whether old and new answers are still appearing.
Incident responseCompare resolvers when some users report stale DNS results.
Continue troubleshooting
Related utilityDNS Leak TestCollector availability and, when configured, the authoritative-zone context needed for real resolver observations.Related utilityHostname LookupThe address records observed by the tipsmake server resolver.Related utilityIP Address LookupAvailable network and enrichment data returned by the configured provider.

Browse all TipsMake utilities →

Questions and answers

Frequently Asked Questions

What does the DNS Propagation Checker tell me?

It returns the answers returned by each configured resolver, shown separately. Resolver agreement is not proof of worldwide propagation. Caches, TTLs, anycast routing, geography, and resolver policy can produce different answers.

What should I enter in the DNS Propagation Checker?

Use a public hostname and record type you recently changed or want to compare. Enter only the information needed for the check and verify it before running the tool.

Does the DNS Propagation Checker send my input anywhere?

The lookup can use configured external data or resolver providers. Avoid entering private information and treat provider-derived location or network data as approximate.

How accurate is the DNS Propagation Checker?

The tool is designed to report the calculation or observation available to its execution method. Resolver agreement is not proof of worldwide propagation. Caches, TTLs, anycast routing, geography, and resolver policy can produce different answers.