Ready to explore your connection
DNS record lookup
Choose a domain and a record type to inspect the answer returned by Google Public DNS. This is a public resolver observation, not a scan of your device’s system DNS.
DNS lookup
Your next insight starts with a single lookup.Verified risk data required.
No guessed scores.
IP databases estimate a network exit, not your device location.
Optional: requires browser location permission. Device coordinates are excluded from reports.
Open device location map ↗Enable JavaScript to run this tool on demand.
Related network tools
Go deeper. Everything you need to understand your connection.IP intelligence
Geolocation, ASN and network ownership.
DNS lookup
Inspect A, AAAA, MX, TXT and DNSSEC.
WebRTC exposure
See which addresses your browser exposes.
Network exit
Compare IPv4 and IPv6 network exits.
Run a focused DNS query
- Enter a hostname such as example.com. Test the root domain and www separately when investigating a migration.
- Select the record type related to your symptom, then run the diagnostic.
- Read DNS status and the answer list. Save the resolver and check time before comparing another result.
The domain and record type are sent to Google Public DNS only when you run the check.
Choose the right record type
| Type | What to inspect |
|---|---|
| A / AAAA | IPv4 / IPv6 addresses; check both after moving hosting. |
| CNAME | An alias target, which may itself resolve elsewhere. |
| MX | Mail exchanger targets and preference values. |
| TXT | Published text such as verification or mail-policy entries. |
| NS / SOA / CAA | Delegation, zone information and certificate-authority policy. |
Interpret missing records and errors carefully
A successful HTTP response is different from DNS status. Status 3 indicates NXDOMAIN; a successful DNS answer can also contain no record of the requested type. A timeout or blocked browser request does not prove the domain is absent.
TTL describes caching of an answer, not a countdown for every resolver worldwide. The AD field reports validation by the queried resolver; a false value alone does not establish that DNSSEC is broken.
Continue the investigation
Follow the hosting-change DNS checklist, or read the DNS record guide. Compare addresses with the IP lookup and test an IPv6 symptom using the IPv6 tool.