b2KIT

DNS Record Lookup

Look up DNS records (A, AAAA, CNAME, MX, TXT, NS) for any domain using public DNS-over-HTTPS APIs.

Tested tool guide Tested browser tools Checked August 16, 2026

What DNS Record Lookup does and how it behaves

DNS Record Lookup asks a public DNS-over-HTTPS resolver for one selected record type: A, AAAA, CNAME, MX, TXT, or NS. It is suited to checking records visible through recursive public DNS rather than reading a zone file or listing everything under a name. The important surprise is that the result is a resolver's current view. Caches, TTLs, and location-dependent answers can make it differ from an authoritative server or another lookup performed at the same time.

How the result is produced

1

Record-specific query

The entered domain name and selected type become a DNS question sent over HTTPS to a public resolver. Each type requests distinct data: A for IPv4 addresses, AAAA for IPv6 addresses, CNAME for aliases, MX for mail exchangers, TXT for text strings, and NS for a zone's name servers. Changing the type changes the DNS question.

2

Recursive resolver view

The response reflects what the chosen public recursive resolver can currently answer, including information it may have cached. DNS answers are type-specific, so a name can exist while returning no records for the selected type. A negative result can therefore mean either that the name does not exist or that the requested record type is absent.

Good uses

  • Check whether a newly deployed hostname has the expected A and AAAA addresses visible through public DNS.
  • Inspect MX records during mail-delivery troubleshooting or NS records while checking a delegation change.
  • Retrieve TXT records used for email policy, domain verification, or other DNS-published configuration.

Limits and checks

  • A public recursive answer is not a direct snapshot of the authoritative zone. Cached data can remain visible until its TTL expires.
  • An empty answer for one type does not establish that the domain is unregistered or nonexistent. The name may have records of other types.
  • CDNs and traffic-management systems can return different addresses according to resolver location or other query context, so one lookup is not necessarily universal.

Common questions

Why does this result differ from dig or another DNS website?

The queries may reach different recursive resolvers with different cached data or network locations. Records can also change while older answers remain cached according to their TTLs. Location-aware DNS may deliberately return different addresses. Compare the record type, queried name, resolver, and timing before treating either result as incorrect.

Can this tool list every record belonging to a domain?

No. It looks up the supported A, AAAA, CNAME, MX, TXT, and NS types for the name you enter. DNS does not provide a generally available query that enumerates every name and record in a zone. Records attached to other hostnames, such as service labels or DKIM selectors, require separate lookups.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools