Command-style DNS view
nslookup
Run a parsed DNS lookup and keep the nslookup-style raw output visible when you want the classic command-line view.
This page shares the DNS backend but frames the result for people who think in nslookup output first and tables second.
The raw output block mirrors the command-line perspective, which is often useful for debugging legacy workflows or documentation.
You still get normalized records so you do not have to mentally reformat the nslookup output every time.
A single page can move between A, MX, TXT, NS, SOA, CAA, and PTR without changing the rest of the workflow.
Domain or IP
nslookup
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
Classic nslookup output
The raw output block mirrors the command-line perspective, which is often useful for debugging legacy workflows or documentation.
Parsed records beside it
You still get normalized records so you do not have to mentally reformat the nslookup output every time.
Helpful record-type switching
A single page can move between A, MX, TXT, NS, SOA, CAA, and PTR without changing the rest of the workflow.
02
How to use it
Enter the target, choose the record type, and run the lookup.
Read the parsed answer first if you only need the data, then open the raw nslookup block if you want the exact server-side command output.
When you need dig-specific comments or answer formatting, jump to the dig page next.
03
How to read the result
Raw output is not the source of truth
The parsed records are easier to compare and render consistently, while the raw output is there to preserve familiarity and extra hints.
Resolver comments vary
Nslookup output can differ across operating systems. This page shows what the server returned rather than pretending every environment prints the same thing.
Empty output still matters
If the command returns nothing useful, the page keeps the parsed explanation visible so you still know whether the record type simply had no answer.
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.
nslookup FAQ
Why have a separate nslookup page at all?
Because intent matters. Some operators want the command-style output as their primary frame, while others prefer a cleaner DNS table first.
Does this page use the same resolver logic as DNS Lookup?
Yes. The difference is the presentation emphasis, not a separate DNS stack.
When should I switch to dig?
When you want the dig answer and comments view specifically, especially for TTL-focused or delegation-oriented troubleshooting.