Skip to content

Glossary · Mail Exchange record

What is an MX record?

Quick answer

An MX record is the DNS entry that tells other mail servers where to deliver email for your domain. Each record names a mail host and a preference number; senders try the lowest number first and fall back to higher ones when a host is unreachable. If a domain has no MX record and no address record either, mail to it has nowhere to go.

Definition

MX record (Mail Exchange record): A DNS record naming a server that accepts mail for a domain, with a preference number; senders try the lowest number first. When a domain has no MX record, RFC 5321 has senders fall back to its A or AAAA record.

How MX records work

A sending server looks up the MX records for the recipient's domain, sorts them by preference and connects to the lowest one on port 25. Records with equal preference share the load.

Each MX record must point to a hostname that has its own A or AAAA record. Pointing an MX at a bare IP address or at a CNAME breaks delivery at some senders.

What a null MX record means

RFC 7505 defines a null MX: a single record with preference 0 and a host of just a dot. It says the domain accepts no mail at all.

Senders seeing a null MX fail the message at once instead of queuing it. Domains that only host a website or only send mail publish one to stop bounce traffic and spoofed replies from piling up.

How to check MX records

Run dig MX on the domain, or use an online MX lookup. The output shows each host and its preference.

The hostnames also tell you who runs the mailbox. Google Workspace domains point at Google's mail hosts and Microsoft 365 domains at a host under mail.protection.outlook.com, which tells you what kind of server a verification will be talking to.

$ dig +short MX example.com
10 mx1.example.com.
20 mx2.example.com.

$ dig +short MX parked.example.org
0 .
A domain with a primary and a backup mail host, and a domain that publishes a null MX to say it takes no mail.

How RocketVerifier handles it

Our free MX lookup lists the mail servers for any domain in priority order. During verification we look up MX once per domain per batch, try up to 3 MX hosts and move on only when a host cannot be reached, and an accept from a backup MX is never trusted as proof. A domain with a null MX or no mail route comes back as undeliverable with sub_status does_not_accept_mail, and a domain that does not exist as invalid_domain.

Go further

Sources

  1. RFC 5321: Simple Mail Transfer Protocol
  2. RFC 7505: A "Null MX" No Service Resource Record

FAQ

MX record: common questions

Can a domain receive mail without an MX record?

Technically yes. RFC 5321 has senders fall back to the domain's A or AAAA record when no MX exists. In practice most domains that receive real mail publish MX records, and a domain with neither has no mail route.

How long do MX record changes take to apply?

Up to the TTL on the old record, because resolvers cache it until then. Lower the TTL a day before a migration so the switch takes minutes instead of hours.

Does an MX record at Google or Microsoft mean an address is valid?

No. MX records describe the domain, not the mailbox. Any address at a Google Workspace or Microsoft 365 domain shares the same MX, real or not, which is why we never treat MX hosting alone as deliverable.

Turn definitions into a cleaner list

Verify your first emails in minutes. Credits never expire, and unknown results are always free.

100 free credits · No card required · Credits never expire