Global DNS Check
Check DNS propagation across major resolvers
Compare global resolver responses in one place.
Type a domain to check global DNS propagation results.
Why global checks matter
Resolvers in different regions can cache different answers. A global check highlights mismatches early.
What you will see
A resolver list with record values, TTLs, and a quick propagation status.
Use cases
Verify DNS changes, troubleshoot CDN rollouts, and confirm propagation after updates.
How a global check works
Each resolver has its own cache. This tool queries multiple resolvers at the same time so you can compare answers and spot inconsistencies.
- Resolver caches may keep old answers until TTL expires.
- Different regions can receive different answers from geo-aware DNS.
- Propagation status compares each resolver to the baseline answer.
How to read the status
Use the status labels to understand how consistent the DNS answers are across the resolver list.
- Propagated: answers match the baseline resolver.
- Mismatch: answers differ between resolvers.
- No data: resolver returned no usable response.
Best time to run checks
Run a global check right after a DNS change and again after one full TTL period.
- Short TTL = faster propagation but more queries.
- High TTL = slower propagation but stable caching.
Resolvers included
Cloudflare
Global
Global
Quad9
Global
OpenDNS
North America
AdGuard
Europe
Error glossary
NXDOMAIN
The domain does not exist in DNS.
SERVFAIL
The resolver failed to answer the query due to an upstream error.
Timeout
No response was received before the lookup timed out.
Frequently asked questions
Why do resolvers disagree?
Caches expire at different times and some resolvers are in different regions or networks, so results can vary during propagation.
How long does DNS propagation take?
Propagation usually completes after one full TTL cycle, but some caches can keep answers longer.
Does this tool change my DNS?
No. This tool only performs read-only queries against public resolvers.
Why do I see no data?
The resolver may have timed out, blocked the query, or the domain may not exist.