{{ summaryTitle }}
Resolver: {{ singleResult.resolver }} DNSSEC AD DNSSEC AD: off A {{ singleResult.derived.a_count }} AAAA {{ singleResult.derived.aaaa_count }} MX {{ singleResult.derived.mx_count }} NS {{ singleResult.derived.ns_count }} TXT {{ singleResult.derived.txt_count }}
Ignored {{ singleExtraLinesNotice }} extra line(s). This tool processes only the first non‑blank line.
{{ w }}
ms:
Type Name TTL Data Copy
{{ r.type }} {{ r.name }} {{ r.ttl }} {{ r.data }}
No records.
Field Value Copy
{{ row.k }} {{ row.vs.join('; ') }}
No fields available.
No record data to visualize yet.
TTL information is unavailable for the current lookup.

  

  
:

Introduction:

DNS records are the public instructions that tell clients where to send web, mail, and service traffic. A fast lookup is often the quickest way to confirm whether a name points where you think it does.

This tool performs a DNS record lookup over DNS-over-HTTPS (DoH) for one domain, host, or IP address. It returns clean tables with TTLs, answers, and a derived summary so you can troubleshoot routing issues, verify changes, or document current state.

Paste almost anything: a domain, a URL, an email address, a host:port string, or an IP. The tool normalizes the input and processes only the first non-blank line so you can paste from tickets or logs without cleanup.

If you are auditing email authentication (SPF, DMARC, DKIM, MTA-STS, TLS-RPT), use the dedicated validators so you get full policy parsing and best-practice checks.

Technical Details:

Queries are issued to the selected DoH resolver (Google, Cloudflare, or Auto fallback) for the record types you specify. For domains, Unicode hostnames are converted to ASCII (punycode) via URL parsing before queries. For IP addresses, the tool builds the reverse lookup name and queries PTR.

The results include TTLs and the raw record data string. The summary aggregates counts per record type and highlights DNSSEC behavior:

  • DO (DNSSEC OK) requests DNSSEC-related data.
  • CD (Checking Disabled) asks the resolver not to validate DNSSEC.
  • AD (Authenticated Data) indicates the resolver asserts validation for the response.

Processing pipeline

  1. Parse input, extract hostname if a URL is provided, and trim trailing dots.
  2. Classify as domain or IP; for IPv6, expand and build the ip6.arpa reverse name.
  3. Normalize the record type list from comma/space-separated text.
  4. Issue parallel DoH queries for each record type with the requested DO/CD flags.
  5. Normalize answers (for example, trim trailing dots where appropriate) and compute simple counts.
  6. Render the Records overview, Field breakdown, charts, and a JSON snapshot for export.
Interpretation note. Resolver choice and caching can change what you see. Treat this as a snapshot, and use a propagation tool when you need a multi-resolver view.

Common Follow-ups:

  • Published a change? Use a DNS propagation checker to compare answers across resolvers and locations.
  • Debugging delegation issues? Use a DNS delegation trace to see where the chain breaks.
  • Mail deliverability work? Validate SPF, DMARC, DKIM, and MTA-STS with dedicated tools.