b2KIT

DNS Record Lookup

Query A, AAAA, MX, TXT, CNAME, NS, SOA, and SRV records for any domain using DNS over HTTPS.

Tested tool guide Tested browser tools Checked August 16, 2026

What DNS Record Lookup does and how it behaves

Query a DNS owner name for A, AAAA, MX, TXT, CNAME, NS, SOA, or SRV records through DNS over HTTPS. The result shows the data published for the requested name and record type, such as IP addresses, mail exchangers, aliases, authoritative name servers, or service endpoints. A common mistake is treating one lookup as a complete description of the domain. DNS answers are type-specific, so an empty AAAA result, for example, says nothing about whether an A, MX, or TXT record exists.

How the result is produced

1

Record-specific questions

Each lookup asks for one DNS record type at one owner name. A and AAAA contain IPv4 and IPv6 addresses. CNAME points to another name. MX identifies mail exchangers and their preferences. NS lists name servers, while SOA contains administrative zone data. TXT carries text strings. SRV supplies a priority, weight, port, and target for a named service.

2

DNS over HTTPS transport

The browser sends the DNS question to a DNS-over-HTTPS resolver and receives a standard DNS response over HTTPS. The response can contain answers, aliases, authority information, or an error status. HTTPS protects the question and response while they travel to that resolver. It does not alter the DNS records, prove their correctness, or make the query invisible to the resolver.

Good uses

  • Check A, AAAA, and CNAME records while diagnosing why a hostname reaches an unexpected server or works over IPv4 but not IPv6. Query each relevant type separately because the absence of one does not imply the absence of another.
  • Inspect MX records and email-related TXT records when investigating mail routing, SPF publication, or domain-verification failures. MX results identify mail exchanger hostnames and preferences; they do not directly test whether those hosts accept mail.
  • Review NS and SOA data during a DNS delegation change, or query an SRV owner name such as _sip._tcp.example.com when checking how clients discover a service, its port, and its ordered targets.

Limits and checks

  • An empty answer is not automatically an error. A DNS response can report that the name exists but has no records of the selected type. That differs from NXDOMAIN, which indicates that the queried name does not exist.
  • Results reflect the DNS-over-HTTPS resolver's current view. Cached data can persist until its TTL expires, and a public resolver may see different records from a corporate or split-horizon DNS resolver. If a TTL is displayed, it may already have decreased in cache.
  • Published records do not establish reachability, ownership, or security. An MX or SRV target may require a separate A or AAAA lookup, and this query does not show whether the resulting host is online, whether a port is open, or whether an application is configured correctly.

Common questions

Why does an MX lookup return hostnames instead of IP addresses?

That is the defined shape of an MX record: it contains a preference value and the domain name of a mail exchanger. It does not contain the exchanger's IP address. Query the returned hostname for A and AAAA records to find its published addresses. A lower MX preference value has higher priority, but the lookup does not test delivery.

Does DNS over HTTPS make this lookup private?

It encrypts the DNS exchange between the browser and the selected DNS-over-HTTPS resolver, which prevents ordinary on-path observers from reading that exchange directly. No file or record set is uploaded, but the requested domain name and record type must reach the resolver. The resolver can therefore see the query, so DNS over HTTPS does not provide anonymity.

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

Password Generator

Generate strong, random passwords with customizable length, character sets, and complexity requirements.

Password Strength Checker

Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.

Random String Generator

Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.

QR Code Generator

Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.

QR Code Reader

Scan and decode QR codes from uploaded images or your device camera to extract embedded data.

File Checksum Calculator

Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.