Enter a domain and run a lookup to see results.
DNS Propagation Checker
Check DNS record propagation across 6 public resolvers (Cloudflare, Google, DNS.SB, NextDNS, AdGuard, OpenDNS) in real time.
Detected
—
Tool Features
Related Guides
Coming Soon When a DNS record changes, monitoring checks daily and emails you.
DNS Propagation Checker
See how a DNS record looks on 6 public resolvers: Cloudflare, Google, DNS.SB, NextDNS, AdGuard and OpenDNS. Supports A, AAAA, MX, CNAME, TXT and NS records. Resolvers that return a different value from the majority are highlighted — useful for diagnosing DNS change delays and CDN or load-balancer setups.
How It Works
Queries go in parallel to 6 public DNS-over-HTTPS resolvers (Cloudflare, Google, DNS.SB, NextDNS, AdGuard, OpenDNS), and each answer is compared with the majority. Differences are flagged with the resolver name and the value it returned. They are differences between resolver operators, not between countries: they show which operators still serve an old cached value. For A/AAAA records, when every resolver answers, the values differ and the TTL is short (300 seconds or less), the result is reported as likely geo-DNS or CDN load balancing (info) rather than a warning.
FAQ
How long does DNS propagation take?
Typically 5 minutes to 48 hours, depending on the record's TTL (Time To Live). Records with a 300-second TTL propagate within minutes. Records with a 86400-second (24-hour) TTL may take up to a day. Before making DNS changes, lower the TTL in advance to speed up propagation.
Why do different resolvers show different values?
Each resolver caches DNS responses independently based on the TTL. After a DNS change, resolvers that haven't had their cache expire yet will still return the old value. Once the TTL expires, they query the authoritative server and get the updated record.
My DNS change shows propagated but the site still shows old content — why?
This is likely browser or OS-level DNS cache. Try flushing your local DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS). Also check if a CDN layer is caching the old content independently of DNS.