🌍 DNS Propagation Checker
After changing DNS settings, use this to check what the current public DNS resolver sees for a domain right now.
About DNS Propagation Checker
After changing DNS settings — pointing a domain to a new host, switching name servers, updating an A record — it takes time for that change to be visible everywhere, because DNS resolvers around the world cache records for a period of time set by the record's TTL (time to live) rather than checking on every single request. This tool queries Google's public DNS-over-HTTPS resolver (dns.google) for the domain's current A record and shows you exactly what that resolver sees right now, which is a fast way to confirm whether your change has taken effect at all, at least from one well-known vantage point.
It's most useful right after making a DNS change, as a quick sanity check: if the A record shown here already matches your new server's IP, the change has propagated at least to Google's resolver, and any users still seeing the old site are most likely hitting a resolver with an older cached copy that hasn't expired yet, or their own device or browser has stale DNS cached locally. If it still shows the old IP, either the change hasn't taken effect at your DNS provider yet, or the TTL on the old record hasn't run out.
This single check isn't a complete picture of global propagation, since different resolvers around the world cache independently and will update on their own schedules — for a fuller view across many locations at once, a dedicated multi-location propagation checker is more thorough. This tool is best used as a quick, immediate confirmation rather than proof the change is visible everywhere yet.
Frequently asked questions
Why do different tools show different results?
DNS results depend on which resolver answers your query — different regions and providers cache DNS records for different lengths of time (the TTL), so it's normal to see old and new values simultaneously during propagation.
How long does full DNS propagation usually take?
It depends on the TTL set on the previous record — often anywhere from a few minutes to 48 hours. Lowering the TTL before making a planned change is a common way to speed up future propagation.
Why does my own computer still show the old site even though this tool shows the new IP?
Your operating system and browser keep their own local DNS cache, separate from any public resolver. Flushing your local DNS cache (or simply waiting for it to expire) usually resolves this once the public record has already updated.