Verify DNS changes across global resolvers
DNS propagation is the process by which updated DNS records spread across the global network of DNS resolvers. When you change a DNS record at your domain registrar or DNS provider, the update does not take effect everywhere simultaneously. Instead, each DNS resolver around the world must wait for its cached copy of the old record to expire before fetching the new one. This tool checks multiple major DNS resolvers in parallel so you can see exactly which resolvers have picked up your changes and which are still serving the old data.
Our propagation checker queries well-known public resolvers including Cloudflare (1.1.1.1), Google (8.8.8.8), OpenDNS, Quad9, AdGuard, and NextDNS, among others. By comparing the responses from these different resolvers, you can determine whether your DNS change has fully propagated or whether some resolvers are still returning cached results. This is especially useful after migrating to a new hosting provider, changing name servers, or updating any DNS record.
To use the tool, enter your domain name and select the record type you want to check (A, AAAA, MX, TXT, NS, or CNAME). The tool will query each resolver and display the results side by side, making it easy to spot inconsistencies. If all resolvers return the same value, your DNS change has fully propagated.
DNS propagation refers to the time it takes for DNS record changes to be reflected across all DNS resolvers on the internet. When you update a record, your authoritative DNS server has the new data immediately, but recursive resolvers worldwide may still be serving cached copies of the old record. Propagation is complete once every resolver's cache has expired and been refreshed with the updated information.
DNS propagation takes time because of caching. Every DNS record has a TTL (Time to Live) value that tells resolvers how long to store the record before checking for updates. Until the TTL expires, a resolver will continue serving the cached version even if the authoritative record has changed. Additionally, some ISPs and corporate networks operate their own resolvers with aggressive caching policies that may hold onto records longer than the specified TTL.
The most effective way to speed up propagation is to lower your DNS record's TTL well before making the change. Set the TTL to a low value like 300 seconds (5 minutes) at least 24-48 hours in advance. Once the old TTL period has passed, all resolvers will be using the short TTL, so when you make the actual change, caches will expire quickly. After propagation is complete, you can raise the TTL back to a higher value to reduce query load on your DNS servers.
DNS propagation typically takes anywhere from a few minutes to 48 hours, depending on the TTL of the old records. If the previous TTL was set to 3600 (1 hour), most resolvers will pick up the change within an hour. Records with very high TTLs of 86400 (24 hours) can take a full day. In rare cases, some ISP resolvers may ignore TTL values and cache records longer, which can extend propagation to 48 hours or more.
TTL (Time to Live) is a value in seconds attached to every DNS record that controls how long resolvers cache it. A TTL of 3600 means resolvers will store and reuse that record for one hour before fetching a fresh copy. TTL directly controls propagation speed: lower TTL values mean faster propagation but more DNS queries hitting your authoritative servers, while higher TTL values reduce server load but mean changes take longer to spread globally.
