Skip to main content
SiteIndex
Internet & NetworkReady to use

DNS Propagation Checker

Check DNS propagation by comparing a domain's latest record across public resolvers and its authoritative nameserver.

Guide

Interactive workspace

No account required
Check DNS propagation

Queries 8 public DNS resolvers and the domain's own authoritative nameserver, then shows which resolvers already return the new record.

Record type
Enter a domain to see which public DNS resolvers already return its current record.

How to use it

  1. Enter the domain name and choose the record type to compare.
  2. Start the check to query public resolvers and the authoritative nameserver.
  3. Compare each answer with the expected record value and note resolvers still returning older data.
  4. Allow for cached TTLs, then retry later if the change is not visible everywhere.
What is DNS Propagation Checker?

Check whether a DNS change has propagated by comparing a record across 8 public resolvers and the domain's authoritative nameserver.

How it works

SiteIndex asks the domain's authoritative nameserver for the source-of-truth answer, then queries the same record on Cloudflare, Google, Quad9, AdGuard, NextDNS, DNS.SB, AliDNS, and DNSPod. Each resolver keeps its own cache, so the table shows which ones already return the new value and which still serve the old one until its TTL expires. You can also enter the value you expect, such as a new server IP.

Common uses
  • Confirm a new A record or IP address is live after moving hosting.
  • Check whether MX records for a new email provider have propagated.
  • Verify TXT records for domain verification, SPF, or DMARC before the provider checks them.
Limitations
  • Results depend on the browser, network, input, and external service involved.
  • This tool is informational and does not replace specialist diagnostics or professional advice.
Frequently asked questions
How long does DNS propagation take?
Most record changes appear within the record's TTL, often 5 minutes to 1 hour. Nameserver changes made at the registrar can take up to 24–48 hours because the parent zone's NS records have long TTLs.
Why do some resolvers still show the old value?
Each resolver caches answers for the TTL it received. Until that cache expires, it keeps returning the previous value, even though the authoritative nameserver already has the new one.
How do I check DNS propagation?
Enter the domain, choose the record type (for example A for an IP address), and run the check. Resolvers marked Updated return the same answer as the authoritative nameserver or the expected value you entered.
Can I speed up DNS propagation?
You cannot force other resolvers to refresh, but lowering the TTL a day before a planned change makes caches expire faster when you switch.

Learn more

Related tools