Parsed DNS answers
DNS Lookup
Query A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and PTR records with normalized output, raw resolver views, clear empty states, and two-location comparison where resolver-sensitive answers matter.
This is the clean, parsed DNS view. Use it when you want the records first and the raw dig or nslookup text second.
The parsed record table is normalized so you can compare answers without reading the raw command format first.
If the resolver returns no data for the selected type, the page says so clearly instead of rendering an empty table with no explanation.
Dig and nslookup output are shown underneath when the local command returned useful text and the deployment supports the tool.
Domain or IP
DNS Lookup
Report
ReadySummary
Server-side diagnostic report
Run a check to generate a structured report with status, timings, technical details, and raw output where available.
01
What this tool checks
Normalized record output
The parsed record table is normalized so you can compare answers without reading the raw command format first.
Resolver empty states
If the resolver returns no data for the selected type, the page says so clearly instead of rendering an empty table with no explanation.
Raw views when available
Dig and nslookup output are shown underneath when the local command returned useful text and the deployment supports the tool.
02
How to use it
Pick the record type that matches your question before you run the lookup.
Use A or AAAA for direct address answers, NS and SOA for delegation questions, and TXT or CAA for policy records.
Switch to the dedicated dig or nslookup pages when you specifically want to read the raw command-style output first.
03
How to read the result
TTL is only shown when the resolver exposes it
A and AAAA often include TTL from the Node resolver API, while some other record types may not expose TTL in the parsed output.
PTR answers are reverse DNS
PTR records tell you which hostname maps back from an IP address, which is useful for mail servers, hosting clues, and trust checks.
Raw command output can differ
The parsed table aims for consistency. Raw dig and nslookup text keep the original command perspective and may contain extra comments.
Guides that help you get more from this tool
Interpret the output, understand common failure modes, and choose the next diagnostic step without leaving the product.
DNS Lookup FAQ
Why do some domains return no AAAA records?
Because not every hostname is published on IPv6. That is not automatically an error; it simply means the resolver had no AAAA answer.
Which page should I use for reverse DNS?
Use the dedicated Reverse DNS page when the input is an IP and your main goal is a PTR answer, even though this page can also query PTR records.
Why include raw command output at all?
Because many operators still think in dig or nslookup terms. The parsed table is faster to scan, while the raw text is useful for confirmation.