Does this look up DNS records for me?

No, and that is on purpose. Resolving would require a server, and that server would see every domain you looked up. Run dig or nslookup yourself and paste what your own resolver returned.

Which command output does it understand?

dig in full and short form, host, and nslookup. Between them that covers Linux, macOS and Windows. Lines it cannot interpret are skipped rather than guessed at.

What does the SPF explanation mean?

It reads the qualifier before "all" at the end of the record, which is the policy for senders not otherwise listed. A hyphen means reject, a tilde means accept but mark as suspicious, a question mark means no opinion. That single character is what actually determines whether your domain can be spoofed.

Why is the TTL column showing a dash?

Because the format you pasted does not include it. dig +short and most host output print values without their time-to-live, so there is nothing to show. Use plain dig if you need the TTLs.

DNS Record Parser

Turn raw dig, host or nslookup output into a readable table.

Everything runs inside your browser. Your files never leave your device.

Input

Result

The result appears here as you type.

Ask about DNS Record Parser

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the DNS Record Parser

The output of dig, host and nslookup is designed to be complete rather than readable. Columns run together, the interesting lines are buried among comments and section headers, and each of the three tools formats things differently. This turns that output into a table.

It reads all three formats, plus the bare values that dig +short produces. Records are grouped by type, so every A record sits together and the MX records are not scattered between them, and the whole thing can be re-emitted as JSON or CSV when it needs to go into something else.

The part that saves the most time is the explanation of TXT records. An SPF record ending in "-all" means senders not on the list should be rejected outright; ending in "~all" means treat them as suspicious but deliver anyway; "?all" means the record expresses no opinion at all and is doing nothing for you. Those three characters are the entire policy, they are easy to misread at the end of a long line, and the difference between them is the difference between a domain that can be spoofed and one that cannot. The tool reads the policy and says it in words. It does the same for DMARC, and it names DKIM keys and the various site-verification records for what they are.

Nothing here performs a lookup. That is a deliberate boundary: a page that resolved names for you would need a server, and that server would learn which domains you were investigating. Run the query with your own resolver, where you can see what it returns and choose which one to trust, and paste the answer here to read it.

How to use it

1Run your query — dig example.com ANY, host example.com, or nslookup example.com.
2Paste the whole output here, comment lines and all. Anything that is not a record is skipped.
3Read the table. Records are grouped by type by default, and SPF and DMARC records are translated underneath.
4Switch the output to JSON or CSV if the records are going into a script or a spreadsheet.

Questions

Does this look up DNS records for me?: No, and that is on purpose. Resolving would require a server, and that server would see every domain you looked up. Run dig or nslookup yourself and paste what your own resolver returned.
Which command output does it understand?: dig in full and short form, host, and nslookup. Between them that covers Linux, macOS and Windows. Lines it cannot interpret are skipped rather than guessed at.
What does the SPF explanation mean?: It reads the qualifier before "all" at the end of the record, which is the policy for senders not otherwise listed. A hyphen means reject, a tilde means accept but mark as suspicious, a question mark means no opinion. That single character is what actually determines whether your domain can be spoofed.
Why is the TTL column showing a dash?: Because the format you pasted does not include it. dig +short and most host output print values without their time-to-live, so there is nothing to show. Use plain dig if you need the TTLs.