DNS Record Types Explained

The box matches your text against each record's type, full name, purpose and notes, all case-insensitive. So searching mail returns MX, TXT, SOA, PTR, SPF, DKIM and DMARC because the word appears somewhere in each of their descriptions, not only in the type name.

An A record points a hostname to an IPv4 address such as 93.184.216.34, while an AAAA record, pronounced quad-A, points it to an IPv6 address. Many hosts publish both so clients can connect over either protocol.

Use a CNAME to alias one hostname to another canonical name, for example pointing www to the root domain. A CNAME cannot coexist with other records on the same name, so never place one at the zone apex. Providers offer ALIAS or ANAME records to get apex aliasing safely.

That number is a priority. When several mail servers are listed, senders try the lowest priority value first, so 10 mail.example.com is preferred over 20 backup.example.com. MX targets must be hostnames, never bare IP addresses.

They are email authentication policies, and all three are published as TXT records rather than dedicated types. SPF lists which servers may send for the domain, DKIM publishes the public key that verifies signatures, and DMARC tells receivers how to treat mail that fails SPF or DKIM and where to send reports.

A TXT record stores free-form text, with each string limited to 255 characters. It is the workhorse behind domain-ownership verification and email policy, so SPF, DKIM and DMARC all ride on TXT records under specific names.

DNSKEY holds the public key used to validate signatures, RRSIG carries the actual signature over a record set with explicit validity dates, and DS is placed in the parent zone to link to the child's key and build the chain of trust. If the DS and child DNSKEY disagree, validation breaks.

No. It is a static reference that explains what each record type means and shows a sample value. To see a real domain's records you would run a query tool such as dig or nslookup, or use your registrar's DNS panel.

No. The search runs entirely in your browser over a built-in list, so nothing you type leaves your device and the page works offline once loaded.