DNS Lookup

Look up any DNS record for a domain through Cloudflare, Google Public DNS or Quad9. Pick a record type, or check all the main types at once.

What this tool checks

The DNS lookup asks a public recursive resolver for the records of a name, exactly as a browser, mail server or app would. You choose:

  • The name: a domain (example.com), a subdomain (www.example.com) or a service name (_sip._tcp.example.com). International domain names are converted to their ASCII form (punycode) automatically.
  • The record type: A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV, PTR, HTTPS, SVCB, DS, DNSKEY and others. You can also enter a numeric type.
  • The resolver: Cloudflare (the default), Google Public DNS or Quad9.
  • DNSSEC: when enabled, the query asks for signatures, so RRSIG records are included and you can see whether the resolver validated the answer.

The all records option queries A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, HTTPS, DS and DNSKEY in parallel and groups the results. SRV is not included because it needs a service name.

Queries are sent from our server, not from your browser, over DNS over HTTPS (RFC 8484). The resolver sees our server’s address, not yours.

How to read the result

Status

Status Meaning
NOERROR with records The name exists and has records of this type.
NOERROR with no records The name exists but has no records of this type (often called NODATA).
NXDOMAIN The name does not exist at all.
SERVFAIL The resolver could not get a valid answer: the nameservers are unreachable, misconfigured, or DNSSEC validation failed.
REFUSED A server refused to answer the query.

Flags

  • AA (authoritative answer) is normally off here, because answers come from a resolver’s cache, not from the zone’s own servers.
  • RD and RA show that recursion was requested and available.
  • AD (authenticated data) means the resolver validated the answer with DNSSEC.
  • TC means the answer was truncated.

Sections

  • Answer: the records you asked for. Each line shows the name, the TTL, the type and the data.
  • Authority: for NXDOMAIN or empty answers, the zone’s SOA record, which also sets how long the negative answer is cached.
  • Additional: extra records the server chose to include.

TTL

The TTL shown is the time left in the resolver’s cache, in seconds. It counts down between queries and resets when the cache refreshes. Comparing TTLs between resolvers tells you roughly when each will pick up a change.

Dig view

The text view mirrors the output of the dig command, so you can paste it into a ticket or a chat. The result URL can be shared too: anyone opening it runs the same query again and sees fresh data.

Common problems and fixes

  • The record is there at my provider but the lookup shows the old value. Caching. Wait for the TTL to expire, or compare resolvers with the propagation checker, which also shows the authoritative answer.
  • NXDOMAIN for a name I just created. A resolver may have cached “does not exist” from an earlier lookup. The SOA minimum value caps how long that lasts.
  • SERVFAIL on one domain only. Often a DNSSEC problem, such as a DS record at the registrar that does not match the zone’s keys, or nameservers that do not answer. Run the query with DNSSEC turned off to see whether the zone itself answers.
  • A CNAME appears when I asked for A. The name is an alias. The resolver followed it and returned both the CNAME and the target’s records. The CNAME checker shows the full chain.
  • Different answers from different resolvers. Normal right after a change, and also normal for services that return different addresses depending on the location of the query, such as CDNs.

Record guides

Every record type has a guide explaining its fields and typical mistakes: A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV, PTR, HTTPS and SVCB, and DS and DNSKEY.

For specific jobs, dedicated tools give a more focused view: MX lookup, TXT lookup, NS lookup, the email checker and the WHOIS lookup.

Frequently asked questions

Is this the same as running dig?

It gives you the same information: status, flags, answer, authority and additional sections, plus a dig-style text view you can copy. The difference is that the query is sent by our server to a public resolver over DNS over HTTPS, not from your computer to your own resolver.

Why don't I see the change I just made?

The resolver may still hold the old answer in cache until its TTL runs out. Try another resolver, or use the DNS propagation checker, which also asks your domain's authoritative nameservers directly.

Why is ANY not supported?

Many servers no longer answer ANY queries fully (RFC 8482 allows them to return a minimal answer), so the results would be misleading. Use the 'all records' option instead, which queries each main type separately.

Can I look up records on my internal network?

No. Queries go to public resolvers on the internet, so names that exist only on a private or corporate DNS server will return NXDOMAIN.