Check DNS Mail Records: A Complete Guide to MX, SPF, DKIM & DMARC
Having trouble with email delivery? Learn how to check DNS mail records, find MX records, and understand SPF, DKIM, and DMARC so you can identify configuration problems and make informed decisions about your domain.
You've sent an email, but it never arrived. Or perhaps you're setting up a new business email address and want to make sure everything is configured correctly.
Before assuming something is wrong with your email provider, check your domain's DNS records. These records help determine where incoming emails should go and provide information that receiving mail servers use to authenticate messages.
In this guide, you'll learn how to check DNS mail records, find MX records, inspect SPF settings, and understand DKIM and DMARC. You'll also learn what the results mean and which problems deserve further investigation.
If you're working with business contact lists, you can also explore the email validation tools available at Sokolov Systems.
What Are DNS Mail Records?
Every domain relies on DNS, or the Domain Name System, to publish information that other computers can look up. Some of that information helps email systems route messages and verify who is allowed to send them.
Four record types are particularly important when investigating email configuration:
- MX records: Tell sending mail systems which servers are designated to receive email for a domain.
- SPF records: Publish a policy identifying servers authorized to send email for a domain.
- DKIM records: Publish public keys used to verify DKIM signatures on email messages.
- DMARC records: Tell receiving systems what policy the domain owner requests for messages that fail DMARC authentication and support reporting.
Each record serves a different purpose. Checking the right ones can help you understand whether a domain's email configuration matches what you expect.
Why Check Your Domain's Mail Records?
Imagine moving your business email to a new provider. You've created your accounts, but messages still aren't arriving as expected. The problem could be related to DNS configuration, so checking the records is a sensible place to start.
There are several other situations where a DNS mail record check can help.
When emails aren't being received
MX records are an important part of incoming email routing. If the records are missing or point to the wrong servers, a domain may not receive messages as intended.
Checking them can help you identify a possible configuration issue before spending time troubleshooting unrelated settings.
When setting up a new email provider
Email hosting providers usually give you specific DNS records to publish when connecting a domain. Checking your records after making those changes can help you confirm that the expected information is visible.
When investigating email authentication
Messages can encounter authentication problems when SPF, DKIM, or DMARC is missing or incorrectly configured.
Checking these records can help you find potential problems, although a DNS lookup alone cannot confirm that every outgoing message will pass authentication.
When reviewing business email domains
Sales and marketing teams often work with long lists of business email addresses. Examining domain configuration can help identify domains that need further investigation before a campaign begins.
Keep in mind that a domain can have correctly configured mail records while a particular mailbox is nonexistent or unable to receive messages.
How to Check DNS Mail Records
You don't need to be a network engineer to perform a basic DNS lookup. A DNS checking tool can retrieve the records published for a domain and help you understand what they contain.
Step 1: Choose the domain you want to check
Start with the domain name, such as example.com. If you're investigating a business email address, use the domain portion after the @ symbol.
For example, if an address is alex@example.com, the domain to investigate is example.com.
Step 2: Look up the MX records
Use a DNS lookup tool that supports MX records. Enter the domain and select the MX record type.
The results should show the mail server hostnames published for that domain, along with their priorities.
If the domain is supposed to receive email but the expected MX records are missing, compare the results with your email provider's configuration instructions.
Step 3: Inspect the SPF record
SPF records are normally published as DNS TXT records. Look for a policy that begins with v=spf1.
Check whether the policy reflects the services authorized to send email for the domain. If you use several email platforms, make sure the configuration accounts for the legitimate sending services.
Don't simply copy an SPF record from another website. The correct policy depends on your own email infrastructure.
Step 4: Check DKIM
DKIM uses a public key published in DNS to help receiving systems verify a signature attached to an email.
The DNS record is associated with a selector. If you don't know the selector, consult your email provider's instructions or inspect the headers of an appropriately signed message.
A missing lookup result doesn't necessarily mean DKIM is completely absent. You may be checking the wrong selector.
Step 5: Review DMARC
DMARC records are normally published as TXT records at a hostname beginning with _dmarc.
For example, the DMARC lookup name for example.com is _dmarc.example.com.
Review the published policy and confirm that it matches your intended configuration. If you're considering a stricter policy, make sure legitimate sending services are properly configured first.
Step 6: Understand what the results tell you
A successful DNS lookup tells you that a record was retrieved. It doesn't automatically mean that the entire email system is working correctly.
Likewise, a failed lookup may be caused by a temporary DNS problem rather than a missing record. Distinguishing confirmed negative results from inconclusive lookups is important when troubleshooting.
MX Records: Where Incoming Email Goes
When someone sends a message to your domain, the sending mail system needs to determine where that message should be delivered.
MX records provide the designated mail server information used for that process.
Each MX record includes a priority and a mail server hostname. When several records are published, lower priority numbers indicate a higher preference.
For example, a domain might publish more than one mail server to support its intended routing configuration. The sending system uses the published priorities and its mail-routing logic to select a destination.
What if no MX records are found?
If a domain is expected to receive email but has no MX records, investigate its DNS configuration.
However, don't assume that the absence of an MX record always makes email delivery impossible. Mail standards allow fallback behavior involving address records in certain circumstances.
The important question is whether the domain's actual configuration supports its intended email service.
SPF: Which Servers Can Send Email?
SPF stands for Sender Policy Framework. It allows a domain owner to publish a policy identifying systems authorized to send email using that domain.
An SPF record is normally stored as a TXT record and starts with v=spf1.
For example, an illustrative policy might look like this:
v=spf1 include:example.net -all
This is only an example. You should not copy it into your own DNS settings without checking what your email provider requires.
When checking SPF, pay attention to three common issues:
- Missing policy: The domain may not have an SPF record published where expected.
- Conflicting policies: Publishing multiple SPF records for the same domain can cause SPF evaluation errors.
- Incorrect authorization: The policy may not include all legitimate sending services.
SPF helps authenticate outgoing email. It does not confirm that a recipient's mailbox exists.
DKIM: Verifying Email Signatures
DKIM stands for DomainKeys Identified Mail. It allows an email to carry a cryptographic signature that receiving systems can verify using a public key published in DNS.
When an email is signed, the receiving system can use the relevant DKIM selector to find the public key.
If DKIM verification fails, possible causes include a missing or incorrect DNS key, a selector mismatch, or changes to signed message content during transit.
To investigate a DKIM problem, check the selector, compare the DNS record with your provider's instructions, and examine the authentication results reported by the receiving mail system.
DMARC: What Happens When Authentication Fails?
DMARC connects email authentication results with a domain owner's published policy.
It builds on SPF and DKIM and allows domain owners to specify how receiving systems should handle messages that fail DMARC authentication.
Three common DMARC policies are:
- p=none: Requests monitoring without a quarantine or rejection policy under DMARC.
- p=quarantine: Requests that failing messages receive suspicious or quarantine-style treatment.
- p=reject: Requests rejection of messages that fail DMARC.
Actual handling depends on the receiving system. Before applying a stricter policy, administrators should review legitimate sending services and authentication results to reduce the risk of affecting genuine messages.
Common DNS Mail Record Problems
If your DNS lookup doesn't return the expected result, start by checking the most likely causes.
Problem What to investigate Expected MX records are missing Confirm the domain and compare the DNS configuration with your email provider's instructions. Emails aren't being received Review MX records, mail server configuration, and any reported delivery errors. SPF evaluation fails Check for conflicting policies, missing sending services, and syntax problems. DKIM verification fails Confirm the selector and compare the published key with the provider's configuration. DMARC isn't found Check the TXT record at the correct _dmarc hostname. A DNS lookup times out Investigate resolver or network problems before concluding that the record is absent. Recent changes aren't visible Check the authoritative DNS configuration and consider caching and TTL values.If the records appear correct but email still isn't working, examine the relevant delivery error or authentication report. DNS is only one part of the email delivery process.
Can Checking DNS Records Tell You Whether an Email Address Exists?
This is where domain checks and email verification are often confused.
Suppose you check the DNS records for gmail.com. The results can tell you about the domain's mail infrastructure, but they cannot establish that a particular address ending in gmail.com belongs to an existing mailbox.
Similarly, a business domain may have valid MX records while individual addresses at that domain are invalid, disabled, or unable to receive mail.
Individual email verification attempts to assess a specific address using additional checks. Results may still be uncertain because some providers restrict mailbox-level verification.
If you're cleaning a B2B contact list, combine appropriate domain checks with address-level validation rather than relying on DNS alone.
DNS Checker vs. Email Domain Checker
A DNS checker can look up different record types for a wide range of purposes. An email domain checker focuses on information relevant to email configuration.
Tool What it checks DNS checker DNS records such as A, AAAA, CNAME, MX, NS, and TXT. MX checker Mail server records used for email routing. SPF checker The domain's published SPF policy. DKIM checker A DKIM public key at a specified selector. DMARC checker The domain's published DMARC policy. Email domain checker Email-related domain configuration, depending on the checks offered. Email address verifier An assessment of an individual email address using available verification methods.Choosing the right tool depends on your goal. If you're troubleshooting mail routing, an MX lookup may be enough to start. If you're investigating authentication, you'll need to look at the relevant SPF, DKIM, and DMARC configuration as well.
Frequently Asked Questions
How do I check DNS mail records?
Use a DNS lookup tool to inspect the domain's MX and TXT records. SPF and DMARC are generally published as TXT records, while DKIM requires the correct selector-specific DNS name.
How do I check MX records for a domain?
Enter the domain into an MX lookup tool and select the MX record type. Review the returned mail server hostnames and priorities.
Can I check DNS mail records for free?
Many DNS lookup services offer basic record checks for free. Available record types, query limits, and additional features vary between services.
Does an MX record mean an email address is valid?
No. An MX record provides information about a domain's designated mail servers. It doesn't prove that a specific mailbox exists.
Why can't I find an SPF record?
The domain may not have an SPF policy published, you may be querying the wrong domain, or the lookup may have failed. Confirm the TXT records and distinguish a confirmed negative response from a temporary DNS error.
Where can I find my DKIM record?
DKIM records are published under selector-specific DNS names. Your email provider's setup instructions should identify the correct selector and record value.
How do I check a DMARC record?
Query the TXT record at _dmarc followed by your domain name. Review the policy and any other tags that are published.
Will fixing DNS records guarantee email delivery?
No. Correct DNS configuration can resolve some problems, but successful delivery also depends on mail server behavior, recipient validity, authentication, sender reputation, and receiving-server policies.
Make Email Validation Part of Your Workflow
Checking DNS mail records is a practical way to investigate how a domain is configured for email. MX records help explain mail routing, while SPF, DKIM, and DMARC provide information about different parts of email authentication.
The key is to understand what each result actually tells you. A domain lookup can reveal useful technical information, but it cannot guarantee that a particular mailbox exists or that a message will reach the inbox.
If you work with business contact lists, start with reliable data and use appropriate validation methods to identify records that deserve further attention.
Explore Sokolov Systems for email validation tools designed to help you work with email data.
Visit Sokolov Systems to explore the available tools.