We ask four independent public resolvers the same question at the same moment and show you each answer. While they disagree, the change is still spreading.
Disagreement is the normal state of a change in progress. It is only a problem if it is still there long after the old TTL has expired.
This resolver returned the same records as the majority. Nothing left to wait for here.
It is still serving an older cached answer. Not a fault - it means the change has not reached this resolver yet, and it will once the previous TTL expires.
The resolver answered, but there is no record of that type on the domain. Common and usually correct - not every domain has AAAA or CAA records.
The resolver did not respond in time. We say so rather than guessing, because a guess here is what made the old version of this tool useless.
Independence is the point. Four caches run by four different organisations agreeing is evidence; the same organisation answering four times is not.
Response times are measured on each request. They reflect how fast the resolver answered our server, not how fast it will answer your visitors.
Waiting on a change and not sure whether to worry? Open a chat with the domain name and we will look at it with you.
It depends on the TTL that was set on the old record. A resolver caches an answer for the TTL and will not ask again until it expires, so a record with a 24-hour TTL can take up to 24 hours to change everywhere. Lower the TTL a day before you plan a change and it will move much faster.
Because four of them genuinely answer us and the rest do not. We tested Quad9, OpenDNS, Mullvad, dns0.eu, Yandex and CIRA - none of them respond to the JSON DoH API from our network. Four real answers is worth more than fifty printed ones.
Because it would be fiction. These resolvers are anycast: your request goes to whichever of their sites is nearest, so "Google Public DNS in Tokyo" is not a thing that can be checked from here. We name the operator, which is the part that is true.
Almost certainly not. It means that resolver is still holding the previous answer in its cache and has not re-asked yet. Check again after the old TTL has elapsed. It only suggests a problem if it persists long after that.
Time To Live - how many seconds a resolver should keep an answer before asking again. The TTL shown next to each result counts down from when that particular resolver cached it, so different resolvers legitimately show different numbers.
No, and nothing can. It shows that four independent resolvers agree, which is a strong signal. Your visitor's ISP resolver may still be holding an old answer until its own cache expires.
Yes. Enter any fully qualified name, such as mail.example.com or www.example.com.
This one asks several resolvers whether they agree. The records lookup shows every record type a domain has, from one resolver. Use this while waiting on a change, and that one when you want the full picture.
The records lookup returns A, AAAA, CNAME, MX, NS, TXT, SOA, CAA and SRV for a domain in a single query.
