Global DNS Propagation Checker
Check real-time DNS record propagation (A, AAAA, CNAME, MX, TXT, NS, SOA) across multiple worldwide recursive DNS servers via DNS-over-HTTPS.
| DNS Resolver Node | Location / Anycast | Status | Resolved Records | TTL | Latency |
|---|---|---|---|---|---|
| Enter a domain and click "Check Global DNS" to probe Cloudflare, Google, Quad9, AdGuard, and AliDNS resolvers via DNS-over-HTTPS. | |||||
How to Check Global DNS Propagation
When you update DNS records with your domain registrar or cloud hosting provider (such as adding a new A record, switching nameservers, or configuring email MX records), the changes do not take effect across the entire world instantly. This tool queries multiple authoritative recursive resolvers globally in parallel via DNS-over-HTTPS (DoH) to verify real-time propagation:
- Enter your Domain Name: Type the apex domain (e.g.,
example.com) or subdomain (e.g.,mail.example.com) into the input box. - Select DNS Record Type: Choose the record type you want to verify:
A(IPv4),AAAA(IPv6),CNAME(Aliases),MX(Mail exchangers),TXT(SPF / DKIM / Verification),NS(Nameservers), orSOA(Start of Authority). - Execute Query: Click "Check Global DNS". Your browser queries Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8), Quad9 (9.9.9.9), AdGuard, and AliDNS simultaneously.
- Compare Results & Consistency: The status table displays whether each global node has resolved your updated record, including TTL and response latency.
Why Does DNS Propagation Take Time? (TTL & Recursive Caching)
DNS is a globally distributed, hierarchical caching system designed to minimize load on authoritative nameservers. Two key factors dictate how long DNS changes take to propagate:
- Time to Live (TTL): Every DNS record includes a TTL value (measured in seconds). When an ISP or recursive resolver fetches your record, it caches the answer locally for the duration of the TTL. If your previous TTL was set to
86400(24 hours), worldwide resolvers will continue serving the old cached record until that 24-hour countdown finishes. - ISP Recursive Cache Policies: Some internet service providers ignore short TTLs and enforce minimum cache retention windows (e.g. 1 to 2 hours) to conserve upstream bandwidth, creating temporary regional discrepancies.
- NS (Nameserver) Delegation Delays: When changing domain nameservers at your registrar, the root TLD zone file (such as
.comor.org) must update, which typically takes 24 to 48 hours to fully propagate worldwide.
Common DNS Record Types Explained
| Record Type | Standard Purpose | Example Value | Recommended TTL |
|---|---|---|---|
A | Maps a hostname to an IPv4 address | 192.0.2.1 | 300 – 3600 seconds |
AAAA | Maps a hostname to an IPv6 address | 2001:db8::1 | 300 – 3600 seconds |
CNAME | Canonical Name alias pointing to another domain | app.vercel-dns.com | 300 – 1800 seconds |
MX | Mail Exchange server for receiving email | 10 mail.google.com | 3600 – 14400 seconds |
TXT | Human/machine readable text (SPF, DKIM, DMARC, SSL verification) | v=spf1 include:_spf.google.com ~all | 3600 seconds |
NS | Delegates a DNS zone to authoritative nameservers | ns1.cloudflare.com | 86400 seconds (24 hrs) |
SOA | Start of Authority (zone serial number, refresh intervals) | ns1.example.com admin.example.com 2026110401 | 86400 seconds |
How DNS-over-HTTPS (DoH) Works
Traditional DNS queries are sent over plaintext UDP port 53, making them vulnerable to eavesdropping, ISP manipulation, and DNS spoofing. DNS-over-HTTPS (RFC 8484) encapsulates DNS queries inside an encrypted HTTPS connection over standard TCP port 443.
This tool communicates directly with global DoH JSON endpoints (Cloudflare, Google Public DNS, and Quad9). Because the browser requests data directly via secure HTTPS APIs, local ISP DNS interception is bypassed, giving you an authentic snapshot of global DNS records.
How to Flush Your Local DNS Cache
If our tool shows that global DNS has propagated, but your computer still cannot reach the new server, your local operating system or browser cache is likely holding the old IP. Follow these terminal commands to flush your cache:
- Windows (CMD as Administrator): Run
ipconfig /flushdns - macOS (Terminal): Run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux (systemd-resolved): Run
sudo resolvectl flush-cachesorsudo systemd-resolve --flush-caches - Google Chrome Browser: Navigate to
chrome://net-internals/#dnsand click "Clear host cache".
Step-by-Step Setup & Troubleshooting Guides
Helpful technical tutorials for router login, password recovery, and network setup:
Default Gateway Directories & Subnets
Access login sheets and diagnostic consoles for major private IP addresses: