Glossary
MX Record

What Is an MX Record?

An MX (Mail Exchange) record is a type of DNS record that specifies which mail servers are responsible for accepting email on behalf of a domain. When someone sends an email to user@example.com, the sending server looks up the MX records for example.com to find out where to deliver the message.

How MX records work

MX records are stored in a domain's DNS zone file alongside A records, CNAME records, and other DNS entries. Each MX record contains two pieces of information: a priority value and a hostname of a mail server. Lower priority numbers indicate higher preference, so when multiple MX records exist, the sending server tries the lowest-priority server first and falls back to others if it is unavailable.

For example, a domain might have an MX record pointing to mail.example.com with priority 10 and a backup record pointing to backup-mail.example.com with priority 20. This ensures mail delivery continues even if the primary server goes down.

MX records in email verification and disposable detection

MX record lookup is a core step in email verification. If a domain has no MX records, it cannot receive email, which means any address at that domain is automatically invalid. This catches domains that were registered but never configured for mail, as well as typo domains that do not exist.

In disposable email detection, MX records provide an additional signal. Many disposable email providers share a small set of mail servers across dozens of domains. Recognizing these shared MX patterns helps detection systems identify new disposable domains even before they appear on known-provider lists. The DisposableCheck API uses MX analysis as one layer in its detection pipeline.

Common MX record issues

Misconfigured MX records cause silent mail loss. If the hostname in an MX record does not resolve to a valid IP address, or if the mail server at that IP is not running, inbound mail will bounce after the sending server exhausts its retry window. Organizations that migrate mail providers sometimes forget to update their MX records, which causes days of lost mail before anyone notices.

Another common issue is missing MX records entirely. Some domain owners set up a website but never configure mail, yet users still try to email addresses at that domain. Verification systems catch this immediately through MX lookup.

Frequently asked questions

Can a domain work without MX records?

Technically, RFC 5321 allows fallback to the domain's A record if no MX records exist, but most modern mail systems require explicit MX records for reliable delivery.

How do I check a domain's MX records?

You can use command-line tools like `dig example.com MX` or `nslookup -type=mx example.com`, or use an online DNS lookup tool to see the results in a browser.

Do MX records affect email sending or only receiving?

MX records only control where inbound mail is delivered. Outbound sending is handled by the sending server's configuration, SPF records, and DKIM signatures.

Try It

Check any email address for free

Test whether an email is from a disposable provider instantly, or integrate the check into your application with the free API.

Related terms

SMTP verification is a technique that checks whether a specific email mailbox exists by initiating a partial conversation with the recipient's mail server using the Simple Mail Transfer Protocol. The verifier connects to the server, issues EHLO, MAIL FROM, and RCPT TO commands, then disconnects before actually delivering a message. The server's response to the RCPT TO command reveals whether the mailbox is valid.

Email verification is the process of confirming that an email address exists, is correctly formatted, and can receive messages. It typically involves syntax checks, domain and MX record validation, and sometimes SMTP-level handshake probing to determine whether the mailbox is live without actually sending a message.

An SPF (Sender Policy Framework) record is a DNS TXT record that specifies which mail servers are authorized to send email on behalf of your domain. When a receiving server gets a message claiming to be from your domain, it checks your SPF record to verify the sending server is on the authorized list. Messages from unauthorized servers can be flagged, quarantined, or rejected.

DKIM (DomainKeys Identified Mail) is an email authentication method that attaches a cryptographic signature to outgoing messages. The sending server signs specified headers and the message body with a private key, and the corresponding public key is published in the sending domain's DNS. Receiving servers use this public key to verify the signature, confirming the message was sent by an authorized server and was not modified in transit.

Domain reputation is a score that email service providers assign to your sending domain based on your email sending history, bounce rates, spam complaints, engagement patterns, and authentication configuration. It determines whether your messages reach the inbox, land in spam, or get blocked entirely.

Related articles

View all posts

See how a disposable email detection API fits into real-time validation, fallback rules, and abuse-prevention workflows.