How to Check DNS Records for Any Domain (2026 Guide)
DNS records are the backbone of how the internet routes traffic, delivers email, and verifies domain ownership. This guide walks you through how to check DNS records for any domain, what each record type means, and how to diagnose common issues.
What Are DNS Records and Why Check Them?
DNS (Domain Name System) records are instructions stored on authoritative nameservers that tell the internet how to handle requests for your domain. They map human-readable domain names to IP addresses, define which servers handle email, verify domain ownership for third-party services, and configure security policies like SPF and DMARC.
Checking DNS records is essential for troubleshooting. When your website is down, email stops arriving, or an SSL certificate fails to issue, the root cause is often a misconfigured DNS record. By querying your DNS records directly, you can identify propagation delays, typos in record values, missing records, and conflicts between providers.
How to Check DNS Records Using Email Armory
The fastest way to check DNS records is with a dedicated lookup tool. Here is how to do it step by step using Email Armory's DNS Lookup tool:
- Open the DNS Lookup tool. Navigate to the DNS Lookup page on Email Armory.
- Enter the domain name. Type the domain you want to inspect (e.g.,
example.com) into the input field. - Select the record type. Choose which DNS record type you want to query — A, AAAA, MX, TXT, CNAME, NS, or SOA. You can also query all record types at once.
- Review the results. The tool returns the current DNS records as seen from public resolvers, including record values, TTL (time to live), and any errors or warnings.
Common DNS Record Types Explained
Every domain relies on multiple DNS record types. Understanding what each one does helps you diagnose problems faster and configure your domain correctly.
A Record (Address)
The A record maps a domain name to an IPv4 address. It is the most fundamental DNS record — when someone types your domain into a browser, the A record tells their device which server to connect to. Example: example.com → 93.184.216.34
AAAA Record (IPv6 Address)
The AAAA record is the IPv6 equivalent of the A record. As IPv6 adoption continues to grow, having AAAA records ensures your domain is accessible to modern networks and mobile carriers that prioritize IPv6.
MX Record (Mail Exchange)
MX records specify which mail servers accept email for your domain and in what priority order. Without correctly configured MX records, email sent to your domain will bounce. You can verify your MX configuration with our MX Lookup tool.
TXT Record (Text)
TXT records store arbitrary text data and are used for a wide range of purposes: SPF policies for email authentication, DKIM public keys, DMARC policies, domain ownership verification for Google and other services, and security policies like MTA-STS. Check your TXT records with our TXT Lookup tool.
CNAME Record (Canonical Name)
A CNAME record creates an alias from one domain name to another. For example, www.example.com might be a CNAME pointing to example.com. CNAME records cannot coexist with other record types at the same name, which is a common source of configuration errors.
NS Record (Nameserver)
NS records delegate a domain to specific authoritative nameservers. They determine which DNS provider is responsible for answering queries about your domain. Incorrect NS records can make your entire domain unreachable. Verify yours with our NS Lookup tool.
SOA Record (Start of Authority)
The SOA record contains administrative information about the DNS zone, including the primary nameserver, the responsible administrator's email, the zone serial number, and refresh/retry timers. It is critical for DNS zone transfers and caching behavior.
Common DNS Issues and How to Diagnose Them
DNS problems can manifest in subtle ways. Here are the most common issues and how to identify them:
- DNS propagation delays. After changing DNS records, it can take up to 48 hours for changes to propagate globally. If your changes are not visible yet, check the TTL of the old record — caching resolvers will hold the old value until the TTL expires.
- Missing MX records. If email to your domain bounces with "no MX record found," your MX records are either missing or misconfigured. Use the MX Lookup tool to verify.
- CNAME conflicts. A CNAME record at the zone apex (e.g.,
example.com) conflicts with NS and SOA records that must exist there. Use an A record or ALIAS/ANAME record at the apex instead. - Wrong nameservers. If you migrated DNS providers but forgot to update the NS delegation at your registrar, your new records will not resolve. Your registrar's NS records must point to your current DNS provider.
- SPF/DMARC failures. If emails fail authentication, check your TXT records for SPF syntax errors or missing authorized senders. Use our SPF Checker and DMARC Checker for detailed analysis.
When Should You Check DNS Records?
Proactively checking DNS records prevents outages and misconfigurations from going unnoticed. Here are the most important times to run a DNS check:
- After a DNS migration. When switching hosting providers, CDNs, or DNS providers, verify that all records transferred correctly and that delegation is pointing to the new nameservers.
- After email provider changes. Switching from one email provider to another (e.g., migrating to Google Workspace or Microsoft 365) requires updating MX, SPF, DKIM, and DMARC records.
- When troubleshooting delivery issues. If emails are bouncing, landing in spam, or not arriving at all, DNS records are the first place to investigate.
- Before issuing SSL certificates. Many certificate authorities use DNS-based validation. Incorrect CNAME or TXT records will cause validation to fail.
- During regular security audits. Periodically reviewing DNS records helps you catch unauthorized changes, dangling CNAME entries, and outdated SPF includes that could create security vulnerabilities.
For a comprehensive overview of your domain's DNS health, run a Domain Health Check which combines DNS, email authentication, and security checks in a single report.