Network Diagnostics
DNS Lookup
Check the DNS records behind any domain or IP address. Queries run over encrypted DNS-over-HTTPS against Cloudflare or Google, and results appear instantly.
What a DNS lookup actually shows you
Every domain name has to be translated into an IP address before your browser can reach it. That translation lives in the domain's DNS records, which are public. A lookup asks a resolver for those records and shows you exactly what it gets back — the same answer your own device receives when it loads the site.
This tool queries Cloudflare or Google over DNS-over-HTTPS, so the request is encrypted and answered directly by a major public resolver rather than whatever your ISP happens to be running. If you enter an IP address instead of a domain, you'll get registration and network details for that address rather than a record table.
The record types, and what each one is for
| Type | Answers the question |
|---|---|
| A | Which IPv4 address does this domain point to? |
| AAAA | Which IPv6 address does it point to? |
| MX | Which servers receive email for this domain? |
| TXT | Free-form text records — where SPF, DKIM and domain-verification strings live. |
| NS | Which name servers are authoritative for this domain? |
| CNAME | Does this name simply forward to another name? |
How to read the results
The Name column echoes back the record that answered. Watch this one: if you asked about www.example.com and the name comes back as something else entirely, a CNAME redirected your query somewhere you may not have expected.
TTL is time-to-live in seconds — how long resolvers are allowed to cache this answer before asking again. A TTL of 300 means five minutes. Low values usually signal a domain whose owner wants the freedom to move things quickly; very high values mean a change you make today could take a day or more to reach everyone.
Data is the answer itself: an IP address for A and AAAA, a mail server hostname for MX, raw text for TXT.
The status badge shows NOERROR when the query succeeded. That is not the same as "records exist" — a domain can resolve perfectly and still have no MX records at all, which simply means it isn't set up to receive email.
Common reasons to run one
- You've just changed hosting or DNS providers and want to confirm the new records are live. Try both resolvers; if they disagree, propagation is still in progress.
- Your email is going missing. Check MX to confirm mail is routed where you think it is, then check TXT for an SPF record.
- A site loads for other people but not for you. If the public resolvers return a valid A record, the problem is local — your own DNS settings, cache, or network.
- You're checking a suspicious domain. A brand-name site whose NS records point at free hosting is a strong signal something is off.
When a lookup returns nothing
An empty result is information too. It can mean the record type genuinely doesn't exist for that domain, the domain isn't registered, or you've hit a typo. It can also mean the change you made hasn't propagated — old answers stay cached for the length of the previous TTL, not the new one, so a record you shortened yesterday may still be answering from the old value today.
Frequently asked questions
Is this DNS lookup free?
Yes. There is no signup, no account and no query limit. Lookups run directly from your browser against public DNS-over-HTTPS resolvers.
What is the difference between the Cloudflare and Google resolvers?
Both are large public resolvers that should return the same authoritative records. Comparing them is useful during a DNS change: if one has the new value and the other still has the old one, propagation is still in progress.
Why does my new DNS record not show up yet?
Resolvers cache answers for the length of the previous record's TTL. If the old record had a TTL of 86400 seconds, the old value can keep being served for up to 24 hours after you change it, regardless of the new TTL.
Can I look up an IP address instead of a domain?
Yes. Enter an IPv4 or IPv6 address and the tool returns registration, network and geolocation details for that address rather than a DNS record table.
Does a NOERROR status mean records were found?
No. NOERROR means the query itself succeeded. A domain can return NOERROR with zero answers, which simply means that record type is not configured for it.
Last reviewed: · Reviewed by the ShowMyIP team