DNS Lookup

Look up DNS records with six public resolvers. Inspect TTL, DNSSEC flags, mail records and reverse DNS, then copy a zone file or raw JSON.

Runs in your browser

DNS-over-HTTPS · explicit queries only · six public resolvers · IPv4/IPv6 reverse lookup

Your browser sends the queried domain or reverse-IP name and your public IP to the selected resolver. Nothing is sent until you press Look up DNS.

This is the selected public resolver’s cached answer, not a direct query to an authoritative server. AD means that resolver reports DNSSEC validation; its absence does not prove a problem.

Choose the right DNS record

A and AAAA map names to IPv4 and IPv6 addresses. CNAME points to another name; MX identifies mail servers. TXT stores verification and email-policy text. NS identifies name servers and SOA describes the zone.

TTL and cached answers

TTL is a cache lifetime in seconds. A recursive resolver may return the remaining lifetime, so repeated lookups can show decreasing values. Different resolvers can temporarily return different cached data after a change.

NXDOMAIN, NODATA and SERVFAIL

NXDOMAIN means the queried name does not exist. NODATA means the name exists but the requested record is absent. SERVFAIL means resolution failed; it does not prove that the domain is missing.

Reverse DNS and email

Entering an IP address automatically requests its PTR record under in-addr.arpa or ip6.arpa. A PTR name is controlled by the address owner and does not prove ownership of a website. Null MX explicitly declares that a domain does not receive email.

Limits of a browser DNS lookup

Requests go to the selected public resolver over HTTPS. This tool cannot inspect your operating system cache, local hosts file, private DNS server or every authoritative server. AD reports validation by the resolver; missing AD alone is not a DNSSEC failure.

How to use

  1. Enter a domain, URL or IP address.
  2. Choose a record type and public resolver.
  3. Press Look up DNS and inspect the records, TTL and resolver status.
  4. Copy individual records, the zone file or the raw JSON response.

FAQ

Does this use my local DNS server?

No. It queries the public DNS-over-HTTPS resolver you select.

Why do resolvers return different answers?

Cached data, split DNS and location-based routing can differ. Compare resolvers and wait for old TTLs to expire.

Can I look up an IPv6 address?

Yes. IPv6 input is converted into its ip6.arpa reverse name and queried for PTR records.

Who receives my query?

The selected resolver receives the queried name and your public IP. No lookup runs automatically.

Related tools

More Internet tools: Internet

Send feedback

Found a bug or have an idea? Tell us — it helps make the tools better.

Only needed if you would like a reply.

Page: /internet/dns-lookup/