Kalcify
Dev Tool

DNS Propagation Checker

Check DNS record propagation across 7 independent global DNS resolvers instantly. Verify that your DNS changes have propagated worldwide for A, AAAA, CNAME, MX, NS, TXT, and SOA records.

Queries are sent via DNS-over-HTTPS to 7 independent resolvers -- no data is stored or logged

Check DNS Records

Enter a domain without http:// or https://

How to Check DNS Propagation

1

Enter Your Domain

Type or paste your domain name in the input field above. Do not include http:// or https:// -- just the bare domain like example.com or sub.example.com.

2

Select Record Type

Choose the DNS record type you want to check. Use A for IPv4 addresses, AAAA for IPv6, CNAME for aliases, MX for mail servers, NS for name servers, TXT for text records, or SOA for zone authority.

3

Review Results

The tool queries 7 independent DNS resolvers worldwide simultaneously. Green means all servers agree, yellow means propagation is still in progress. Check the Result column to see the actual DNS records returned by each server.

How DNS Propagation Works

DNS Change β†’ TTL Expiry β†’ Resolver Refresh β†’ Global Propagation

When you update a DNS record at your domain registrar or DNS provider, the change does not take effect everywhere simultaneously. DNS is a distributed, hierarchical system with caching at every level.

1. You update a DNS record at your provider (e.g., change A record IP)2. Your authoritative name server reflects the change immediately3. Recursive resolvers worldwide still hold the OLD cached record4. As each cache expires (based on TTL), resolvers fetch the new record5. Eventually all resolvers serve the new record -- propagation complete

Key factors that affect DNS propagation time:

  1. TTL (Time-To-Live) -- The lower the TTL, the faster resolvers will pick up changes. Common values range from 300 seconds (5 minutes) to 86400 seconds (24 hours).
  2. Caching layers -- Your browser, operating system, router, ISP, and recursive resolvers all cache DNS records independently.
  3. ISP behavior -- Some ISPs ignore TTL values and cache records longer than specified, which can delay propagation for their users.
  4. Record type -- NS record changes can take longer because they affect the delegation chain, while A record changes within the same zone are typically faster.

This tool queries public DNS resolvers operated by companies like Google, Cloudflare, Quad9, OpenDNS, and others. Each resolver maintains its own cache, so comparing their responses gives you a picture of global propagation status.

Frequently Asked Questions

What is DNS propagation?

DNS propagation is the process of updating DNS records across all DNS servers worldwide. When you change a DNS record (such as pointing your domain to a new server), it can take anywhere from a few minutes to 48 hours for the change to fully propagate to all DNS servers globally. During this time, different users in different locations may see different results depending on which DNS server their device queries.

Why does DNS propagation take so long?

DNS propagation takes time because DNS records are cached at multiple levels: your local machine, your ISP resolver, and intermediate DNS servers. Each cache has a Time-To-Live (TTL) value that controls how long the record is stored before being refreshed. Higher TTL values mean longer propagation times. To speed up propagation, you can lower the TTL value before making changes, then increase it again after the change has fully propagated.

What DNS record types can I check?

This tool supports checking A records (IPv4 addresses), AAAA records (IPv6 addresses), CNAME records (domain aliases), MX records (mail server addresses), NS records (name servers), TXT records (text data, often used for SPF, DKIM, and domain verification), and SOA records (start of authority, containing zone metadata).

How does this DNS propagation checker work?

This tool queries 7 independent public DNS resolvers (Google, Cloudflare, Quad9, OpenDNS, AdGuard, AliDNS, DNSPod) using DNS-over-HTTPS (DoH). Each resolver maintains its own cache, so comparing their responses shows the current state of propagation. If all resolvers return the same records, your DNS change has fully propagated.

Is this tool safe and private?

Yes. DNS queries are routed through our server-side proxy to public DNS-over-HTTPS providers (Google, Cloudflare, Quad9, OpenDNS, AdGuard, AliDNS, DNSPod). No domain names or results are stored or logged. All connections use encrypted HTTPS.

Privacy Notice

DNS queries are routed through our server-side proxy to public DNS-over-HTTPS (DoH) providers including Google, Cloudflare, Quad9, OpenDNS, AdGuard, AliDNS, and DNSPod. No domain names, query results, or any other data is stored or logged. All connections use encrypted HTTPS for security. Your DNS lookups remain completely private.