--- title: What are the different types of DNS records used for? description: Our DNS database covers A, MX, NS, TXT, CNAME, and SOA records. --- [Skip to content](https://knowledge.whoisxmlapi.com/dns-records-data#main-content) English Show submenu for translations ![Logo inline notagline (1)-1.png\]](https://knowledge.whoisxmlapi.com/hs-fs/hubfs/Logo%20inline%20notagline%20(1)-1.png?height=40&name=Logo%20inline%20notagline%20(1)-1.png) Open main navigation Close main navigation - English Show submenu for translations - Go to whoisxmlapi.com Go to whoisxmlapi.com What do you want to know? - There are no suggestions because the search field is empty. 1. [Knowledge Base](https://knowledge.whoisxmlapi.com/?hsLang=en) 2. [DNS Data](https://knowledge.whoisxmlapi.com/dns-data?hsLang=en) # What are the different types of DNS records used for? Our DNS database covers A, MX, NS, TXT, CNAME, and SOA records. A brief description of the business rationale for each record and use case(s) is available below: | **DNS Record Type** | **Description** | **Security and other use cases** | | --- | --- | --- | | **A** | ‘A’ or address is a resource record (RR) that maps a name to an IPv4 IP address.  | Verifying A records is critical to a sanitized DNS database.  An incorrect A record could be catastrophic and open various vulnerabilities, including leading up to a compromise. | | **AAAA** |  Commonly referred to quad-A records, which map a name to an IPv6 IP address. | AAAA verification. | | **CNAME** | The ‘canonical name’ maps to a domain, which is very different from A or AAAA records.     | CNAME’s are often used in phishing attacks, particularly on mobile devices where it’s often difficult to see what a FQDN gets expanded to.  Other concerns include CNAME cloaking, anonymizers, shortened URLs, etc. Subdomain takeovers are becoming more common these days as well.  | | **NS** | Name Server records point to the server that’s authoritative for the given domain name.   | Whoever controls the NS records owns the zone, hence there can be major security implications if the wrong person gets control of records. | | **MX** | MX stands for “Mail Exchange”. This record type designates where email should be sent to.   | MX cannot point to a CNAME record; it has to point to an A or AAAA record. | | **SOA** | A ‘Start of Authority’ record contains data for a given domain or DNS zone. Important information such as the name server authoritative for the domain in question, the TTL (Time-to-Live) which instructs how long before you should refresh your cache, email address of the domain administrator, and other information is stored here. | SOA verification. | | **TXT** | TXT records can contain free-form textual strings which can be read by others upon demand. | Careful what you give away!  TXT records are public and can be read by anyone. TXT records can be used to define a token, or public key string, but it can also be used in malicious ways, such as DNS tunneling for data exfiltration. | | **PTR** | A PTR record, also known as reverse DNS or rDNS record, is a reverse record for an IP address that allows an IP to map to a domain. You can think of PTR records as the opposite of A / AAAA records (which map a domain to an IP address). PTR records are entirely optional. | - Anti-spam and mail server verification, notably to see if an IP is expected to correspond to legitimate servers. \- Missing or wrongly set PTR records can create email delivery issues. \- Logging, as they offer human-readable information instead of numerical IP addresses. | You can download a DNS data sample for each record type [here](https://dns-history.whoisxmlapi.com/database/specifications).   - [NRD2](https://knowledge.whoisxmlapi.com/nrd2?hsLang=en#main-content) - [Tutorials](https://knowledge.whoisxmlapi.com/nrd2?hsLang=en#tutorials) - [General Support](https://knowledge.whoisxmlapi.com/general-support?hsLang=en) - [WHOIS Domain Data](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#main-content) - [WHOIS vs. Historical WHOIS](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#whois-vs-historical-whois) - [Quarterly feeds](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#quarterly-feeds) - [WHOIS data fields](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#whois-data-fields) - [Bulk WHOIS Lookup](https://knowledge.whoisxmlapi.com/whois-domain-data?hsLang=en#bulk-whois-lookup) - [DNS Data](https://knowledge.whoisxmlapi.com/dns-data?hsLang=en) - [APIs](https://knowledge.whoisxmlapi.com/apis?hsLang=en#main-content) - [WHOIS API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#whois-api) - [WHOIS History API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#whois-history-api) - [DNS Lookup API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#dns-lookup-api) - [IP Geolocation API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#ip-geolocation-api) - [Email Verification API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#email-verification-api) - [Domain Reputation API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#domain-reputation-api) - [Subdomain Lookup API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#subdomain-lookup-api) - [Reverse WHOIS API](https://knowledge.whoisxmlapi.com/apis?hsLang=en#reverse-whois-api) - [Databases / Data Feeds](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#main-content) - [Threat Intelligence Data Feeds (TIDF)](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#threat-intelligence-data-feeds-tidf) - [IP Geolocation / IP Netblocks Databases](https://knowledge.whoisxmlapi.com/databases-data-feeds?hsLang=en#ip-geolocation-ip-netblocks-databases) - [Legacy](https://knowledge.whoisxmlapi.com/legacy?hsLang=en) - [Dev & Data Science Corner](https://knowledge.whoisxmlapi.com/dev-data-science-corner?hsLang=en#main-content) - [Dev resources](https://knowledge.whoisxmlapi.com/dev-data-science-corner?hsLang=en#dev-resources) - [Domain Research Suite (DRS)](https://knowledge.whoisxmlapi.com/domain-research-suite-drs-1?hsLang=en) - [IP Data](https://knowledge.whoisxmlapi.com/ip-data?hsLang=en) [![Chill listening crop-3](https://knowledge.whoisxmlapi.com/hs-fs/hubfs/Logo%20eye%20icon%20(1).png?width=37&height=24&name=Logo%20eye%20icon%20(1).png "Chill listening crop-3")](http://whoisxmlapi.com) Copyright © 2026, whoisxmlapi.com