Dig-style DNS view
dig
Use the same public DNS backend with a dig-oriented presentation, including parsed records and the raw dig answer block returned by the server.
The dig page is for people who want answer-style output and comments without losing the structured record summary above it.
The raw dig block preserves the server-side command output for operators who are used to reading answer sections directly.
The table above the raw block keeps the data readable and easier to compare across record types.
You can still run reverse lookups here, but the dedicated reverse DNS page is easier when PTR is the main question.
Domain or IP
dig
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
Dig answer output
The raw dig block preserves the server-side command output for operators who are used to reading answer sections directly.
Parsed record normalization
The table above the raw block keeps the data readable and easier to compare across record types.
PTR-friendly workflows
You can still run reverse lookups here, but the dedicated reverse DNS page is easier when PTR is the main question.
02
How to use it
Choose the record type that maps to your question and run the lookup.
Read the explanation and parsed records first, then open the dig block for the raw answer view.
Compare the dig page with nslookup when you need to show the same target in two familiar command-line formats.
03
How to read the result
Parsed and raw can both be useful
The parsed records help with clarity, while the dig block helps when you want to reason about the exact answer section returned on this server.
No answer is still a result
An empty answer section does not always mean the domain is broken. It can simply mean the selected type is not published for that host.
TTL visibility depends on the source
The dig block may show TTL that the higher-level resolver API does not expose in the parsed table.
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.
dig FAQ
Why show both dig and parsed data?
Because raw dig output is familiar, but normalized records are easier to scan on the web and easier to localize cleanly.
Can I use this for MX, TXT, and CAA records too?
Yes. The record type switch is not limited to A and AAAA queries.
Does the server follow a custom resolver chain?
The page uses the resolver available to this deployment, then shows the raw dig output returned by the system tool when available.