← All Tools
DNS Record Viewer🔒 100% local
Parse pasted dig or nslookup output into a clean, readable DNS record table. Privacy-first, no server uploads, no tracking.
Related Tools
Reads DNS records out of text you paste - a dig answer section, a zone file, nslookup output, or plain name TTL IN TYPE value lines - and prints them as an aligned table grouped by type, followed by a list of structural problems and some suggested follow-up commands. Recognised types are SOA, NS, A, AAAA, CNAME, MX, TXT, SRV, CAA, PTR, DS, DNSKEY, and NAPTR. No query is made: the tool only parses text you already have.
How to use it
- Get the records as text - for example run dig +noall +answer example.com ANY - and paste them into the box.
- Press Process.
- Work through the table first, then the Findings block, which flags things such as private addresses in A records, a lone NS record, MX without SPF, or an SPF record with no -all qualifier.
Worked example
example.com. 3600 IN A 192.168.1.10
mail.example.com. 3600 IN A 203.0.113.9
example.com. 3600 IN MX 10 mail.example.com.
example.com. 3600 IN NS ns1.example.com.becomesParsed 4 record(s) — 2 A, 1 MX, 1 NS
By type:
A 2 192.168.1.10 | 203.0.113.9
MX 1 10 mail.example.com.
NS 1 ns1.example.com.
Records:
NAME TTL TYPE VALUE
example.com. 3600 A 192.168.1.10
mail.example.com. 3600 A 203.0.113.9
example.com. 3600 MX 10 mail.example.com.
example.com. 3600 NS ns1.example.com.
No SOA record in the pasted data (that is normal for dig answers — query the zone apex with type SOA).
Nameservers: ns1.example.com.
Findings:
⚠ 1 A record(s) point to RFC1918 private addresses — public resolvers cannot reach them.
⚠ Only one NS record — always publish at least two (ideally in different networks) for redundancy.
⚠ MX records exist but no SPF TXT record — expect your mail to land in spam.
Next steps:
dig +short example.com A # authoritative answer
dig @1.1.1.1 example.com A # ask a specific resolver
dig +trace example.com # walk from the root
Propagation: TTL is in seconds — an old record stays cached for up to that long. Check multiple resolvers (1.1.1.1, 8.8.8.8) before assuming a problem.example.com. 300 IN A 93.184.216.34
example.com. 3600 IN MX 10 mail.example.com.
example.com. 3600 IN TXT "v=spf1 include:_spf.example.com -all"becomesParsed 3 record(s) — 1 A, 1 MX, 1 TXTA clean set: quotes are stripped from the TXT value for display, the SPF check passes because the value ends in -all, and the Findings block reads "No structural problems detected in these records."
When to use it
- Auditing a zone you copied out of a hosting control panel before you save the change.
- Working out which record is wrong when a domain resolves in one place and not another.
- Turning a wall of dig output into something you can paste into a ticket.
What it does not do
- It does not resolve anything. Pasting only a domain name returns the no-records-recognised help text rather than live records - run dig, nslookup, or the DNS panel first, then bring the text here.
- Lines are matched against the known type list or against nslookup Name:/Address: pairs. Unknown record types, and SOA records wrapped across several lines, are dropped from the table without a warning.
- The findings are heuristics over the slice you pasted. A dig answer carries no NS or SOA records, so a nameserver warning can simply mean you did not paste that section.