What the result means
Each card shows what one public resolver answers right now. When every resolver returns the same records, your change has reached the large public resolvers. When they differ, some resolvers still hold the previous answer in cache until its TTL (time to live) runs out.
- Answer: the resolver returned records of the type you asked for.
- No record: the domain exists, but it has no record of that type.
- Domain not found: the resolver says the name does not exist (NXDOMAIN).
- Server failure: the resolver could not get a valid answer (SERVFAIL). A broken DNSSEC setup can cause this.
- Could not be checked: the resolver did not respond to our server in time.
Example
Checking an A record for a domain that points to a web server:
example.com A 203.0.113.10 TTL 300
If Google and Cloudflare return 203.0.113.10 but another resolver still returns an older address, the change is still spreading.
Limits
- Only a few large public resolvers are queried (Google Public DNS, Cloudflare, Quad9, DNS.SB). They are anycast services, so this is not a map of every country.
- The queries start from our server, not from your device. Your own ISP or office resolver may still hold older answers.
- Some providers return different answers by region on purpose (CDN, geo DNS), so a difference is not always a problem.
- Lookups are read-only. Nothing in your DNS is changed.
FAQ
How long does DNS propagation take?
It depends mostly on the TTL of the old record. Resolvers may keep it until the TTL ends, so changes with a 300 second TTL often show within minutes, while a one-day TTL can take a day. Nameserver changes at the registrar can take longer.
Why do two resolvers show different results?
One may have refreshed its cache and the other not yet. It can also be intentional, for example geo-based or load-balanced answers.
Can I check a subdomain or a TXT record?
Yes. Enter the full name, such as mail.example.com or _dmarc.example.com, and pick the record type.