DNS Records Explained: A, CNAME, MX, TXT, SPF and DMARC
Short answer: DNS records explained simply: paste your DNS records or a zone snippet (from dig, a BIND zone or a registrar export) into the DNS Analyzer and it shows each record's type, name, value, TTL and structure, and flags common mistakes. It works in your browser on the text you provide. Live lookups are optional, off by default and ask for your consent first.
What the records mean
- A and AAAA: an IPv4 or IPv6 address for a name. The tool adds notes on private, documentation, loopback and other special ranges. For address ranges, see the CIDR cheat sheet.
- CNAME: an alias to another name. The tool checks things like a CNAME sitting beside other records on the same name.
- NS: the name servers for a zone.
- MX: priority and mail host, including the null MX (
0 .) that says a domain accepts no mail. - TXT: text values. Multiple quoted strings are joined the way DNS does. SPF, DMARC and DKIM records are broken into their tags.
- SOA: primary server, contact address, serial and timers.
- CAA: flags, tag and value, which say which certificate authorities may issue for the domain (to read an issued certificate, see how to decode a PEM certificate).
- SRV: priority, weight, port and target.
Other record types are displayed but not analysed in depth.
The SPF 10-lookup limit
SPF records that pull in other records through include: and similar terms can exceed the limit of 10 DNS lookups. The analyzer counts the lookups for you, which is much easier than counting by hand.
What the parser understands
$ORIGIN, $TTL, @, blank owner names, multi-line parentheses, comments, quoted strings and escapes. Internationalised names are shown in both Unicode and Punycode (xn--) form, with a warning for mixed-script names that may be look-alikes.
Parsed is not verified
A record that parses has valid syntax. That does not make it published, correct, safe or DNSSEC-validated. The tool says so plainly, and so should you whenever you read its output.
Why a browser cannot do dig
A web page cannot open UDP or TCP connections, so no browser-only tool can query a DNS server directly the way dig does. For a current answer, run dig or nslookup yourself, or use the optional lookup.
The optional live lookup
- It is a request from your browser to Cloudflare Public DNS or Google Public DNS using DNS-over-HTTPS. You choose the provider, and the exact request is shown before anything is sent.
- The button stays disabled until you tick a consent box, and the box clears after each request.
- The provider sees the domain you ask about and your IP address, under its own privacy policy. Do not look up names you consider confidential.
- The tool does not validate DNSSEC. The answer is labelled as reported by the resolver.
- Live results appear in their own panel and are compared with your pasted records without being merged.
DNS records explained: how to use the DNS Analyzer
- Open the DNS Analyzer.
- Paste records, set the origin and default TTL if names are relative, and press Analyze.
- Read the type-by-type breakdown and the warnings. Large zones show 100 records at a time.
- If you need current data, use the optional live lookup after ticking consent.
- Download the result as JSON if you need it.
Limits to know
- Syntax checks, not proof that a record is live.
- Punycode conversion follows RFC 3492 with simplified IDNA rules. It is not a full IDNA 2008 validator.
- Input size and record count are capped.
Frequently asked questions
What does a CNAME conflict mean? A CNAME should not sit beside other records on the same name.
What is the SPF 10-lookup limit? SPF evaluation allows only a limited number of DNS lookups. The tool counts them.
What is a null MX?
0 .: the domain does not accept email.
Can a browser run dig? No. It cannot send raw DNS queries.
Is the live lookup private? No. The provider sees the domain and your IP address, which is why it asks for consent.