DNS Propagation Checker

DNS propagation typically takes anywhere from a few minutes to 48 hours, depending on the TTL of the record you changed. If your record had a TTL of 3600 seconds (1 hour) before the change, resolvers that cached it will continue serving the old value for up to an hour. Major public resolvers like Google and Cloudflare often pick up changes within minutes, but ISP-level resolvers can lag further behind.

Each DNS resolver caches records independently for the duration of their TTL. Until the TTL on the old record expires, a resolver will keep serving the cached value regardless of what the authoritative server now says. This is by design: caching reduces DNS query volume across the internet. It means propagation is not instantaneous but is a gradual process as caches expire around the world.

Yes. The best way is to lower your record's TTL to a small value (such as 300 seconds) a day or two before you plan to make the change. Once all resolvers are caching the short TTL, make your change and propagation will be much faster. After the change has fully propagated you can raise the TTL back to a higher value. You cannot force third-party resolvers to flush their cache immediately, but lowering TTL in advance is the industry-standard approach.

This tool queries three major public DNS resolvers via DNS over HTTPS: Google Public DNS (8.8.8.8), Cloudflare DNS (1.1.1.1), and Quad9 (9.9.9.9). These resolvers are among the most widely used in the world and serve a large proportion of global internet traffic, making them a good proxy for checking whether your DNS changes have reached the broader internet.