Geo DNS Result
See DNS answers by region
Understand geo-based DNS routing with a regional snapshot.
Type a domain to check regional DNS results.
Regional visibility
Geo DNS answers can change depending on where queries originate.
What you will see
Cards grouped by region with record values and TTL summaries.
Use cases
Validate geo-routing, CDN steering, and localized DNS policies.
How geo DNS works
Resolvers in different regions can receive different answers for the same domain. This tool checks multiple regions to surface those differences.
- Geo-aware DNS can route users to the closest edge.
- CDNs sometimes return different IPs per continent.
- TTL affects how quickly regional changes appear.
How to interpret regional cards
Each card shows the resolver region, returned records, and TTL values.
- Resolved: at least one record returned.
- No data: the resolver timed out or returned no records.
When to run regional checks
Run geo checks after CDN changes, routing updates, or latency tuning.
- Check multiple times during rollout windows.
- Compare results to ensure expected routing.
Resolvers included
OpenDNS
North America
DNS.LA
North America
AdGuard
Europe
UncensoredDNS
Europe
Quad101
Asia Pacific
DNSPod
Asia Pacific
Brazil Resolver 1
South America
Brazil Resolver 3
South America
Argentina Resolver 3
South America
Argentina Resolver 4
South America
Saudi Arabia Resolver 1
Middle East
Saudi Arabia Resolver 2
Middle East
United Arab Emirates Resolver 1
Middle East
Turkey Resolver 1
Middle East
Jordan Resolver 1
Middle East
Australia Resolver 1
Oceania
Australia Resolver 2
Oceania
Australia Resolver 3
Oceania
New Zealand Resolver 1
Oceania
New Zealand Resolver 2
Oceania
Error glossary
Geo DNS
DNS behavior that varies by resolver location or network.
Edge routing
Directing users to the nearest or best-performing endpoint.
TTL
The caching lifetime of a DNS record before a resolver refreshes it.
Frequently asked questions
Why do regions return different answers?
Geo-aware DNS and CDN routing can return different IPs based on resolver location.
Is this the same as user geolocation?
Not exactly. Results depend on resolver location, not the end user device.
How can I verify CDN rollouts?
Run geo checks before and after the rollout to confirm expected regional changes.
What if I see no data?
The resolver may have timed out, or the domain is not published in that region yet.