DNS Propagation Checker
Check DNS propagation status across 8 global resolvers (Cloudflare, Google, Quad9, OpenDNS, and more). Supports A, AAAA, CNAME, MX, TXT, NS records. Shows propagation percentage and consensus value.
How to Use DNS Propagation Checker
- 1Enter your domain name and select the DNS record type (A, AAAA, CNAME, MX, TXT, NS).
- 2The tool queries 8 major DNS resolvers simultaneously across different providers.
- 3Results show which resolvers have your updated record and which still serve the old value.
- 4The propagation percentage tells you how far your DNS change has spread globally.
Zenovay
Track your website performance
Real-time analytics, session replay, heatmaps, and AI insights. 2-minute setup, privacy-first.
Related Tools
JSON Formatter & ValidatorFormat, validate, and beautify JSON data with syntax highlighting and error detection.
JWT DecoderDecode and inspect JWT tokens. View header, payload, and verify signatures.
Base64 Encode/DecodeEncode text to Base64 or decode Base64 back to text. Supports UTF-8 and binary data.
URL Encode/DecodeEncode or decode URL components. Handle special characters, query strings, and full URLs.
Frequently Asked Questions
How long does DNS propagation take?▾
DNS propagation typically takes between 15 minutes and 48 hours, depending on the TTL (Time to Live) of your old record and how aggressively resolvers cache results. Most major resolvers (Cloudflare, Google) will pick up changes within 15–30 minutes. ISP-level resolvers may take 24–48 hours to flush their caches. To speed up propagation, lower your TTL to 300 seconds (5 minutes) at least 24 hours before making the change.
What does NXDOMAIN mean in DNS propagation?▾
NXDOMAIN (Non-Existent Domain) means the resolver returned a "this domain does not exist" response. This can mean: (1) the domain genuinely doesn't exist, (2) the resolver hasn't received the new record yet, or (3) the resolver is serving a cached NXDOMAIN response from before the domain was created. For new domains, NXDOMAIN from some resolvers is normal during propagation.
Why do different resolvers show different values?▾
Each DNS resolver has its own cache with its own expiration timers. When you change a DNS record, the old value stays cached at each resolver until its TTL expires. Different resolvers may have different cache ages, causing some to show the new value while others still serve the old one. This is normal and expected during propagation. The "Different value" status indicates a resolver returned a different answer than the consensus.
What is TTL and how does it affect propagation speed?▾
TTL (Time to Live) is the number of seconds resolvers are allowed to cache your DNS record. A TTL of 3600 means resolvers will cache the record for 1 hour before re-querying your authoritative nameserver. Lower TTL = faster propagation (resolvers check for updates more often) but more DNS queries and slightly higher load on your nameservers. Before a migration, set TTL to 300 (5 min). After the migration, you can raise it back to 3600.
What is the difference between DNS propagation and DNS replication?▾
DNS replication refers to the synchronization between your primary and secondary authoritative nameservers — this is usually near-instant (seconds to minutes). DNS propagation refers to how long it takes for recursive resolvers (the ones your users actually query) to flush their caches of the old record and pick up the new one. This is what takes minutes to hours. This tool checks recursive resolver propagation, not nameserver replication.