DNS Propagation Check
Validation Error
Global Resolvers
Change a DNS record and it doesn't update everywhere at once. Different resolvers around the world hold onto old values for different lengths of time, governed by the record's TTL, so your update spreads gradually rather than instantly.
Moreover, DNS Propagation check tool checks your domain against more than fifteen public DNS servers in different regions and shows you, server by server, whether each one has picked up the change yet.
Query DNS propagation against top-tier global recursive DNS servers from different geographic locations.
Check propagation for A, AAAA, MX, CNAME, TXT, and NS records to ensure your DNS changes are fully distributed.
Watch resolution results populate progressively with concurrent client-side batches, delivering rapid feedback.
Record types you can check
- A (IPv4 address)
- AAAA (IPv6 address)
- MX (mail server)
- CNAME (alias)
- TXT (text records, useful for SPF and verification)
- NS (nameserver)
When to actually use this
Right after you've pointed a domain at a new server, switched nameservers, or updated an MX record for a new email provider. If some locations still show the old value, that's normal and expected, it just means their cache hasn't hit its TTL expiry yet, not that anything's broken. A DNS Lookup shows you the full record set, and Clear DNS Cache can push the update along faster on the major resolvers.
FAQS
What is DNS propagation?
DNS propagation is the timeframe it takes for DNS changes (like updating your IP address or MX records) to update across all servers on the internet globally.
How does the DNS Propagation Checker work?
It performs real-time DNS queries against 15+ public DNS servers around the world using direct UDP queries from the backend. The results show whether each server has updated to the new record.
What record types can I check?
You can check A (IPv4), AAAA (IPv6), MX (Mail server), CNAME (Canonical Name), TXT (Text), and NS (Name Server) records.
Why do some locations show old records?
DNS records are cached by resolvers according to their Time to Live (TTL). Some global servers might update immediately, while others wait for the TTL cache to expire.