What is an MX record? Explained for non-engineers

MX stands for Mail eXchange. An MX record is a DNS entry that tells the rest of the internet which server handles incoming email for a domain. Without an MX record, a domain cannot receive mail at all. With a broken one, mail goes nowhere visibly. It is one of the most important pieces of email infrastructure most people never look at.

The plain analogy

When you send a letter to "Acme Corp, 100 Main Street", the postman needs to know which building accepts mail for Acme. The MX record is the equivalent: it says "for mail addressed to acme.com, deliver to mail.acme.com". The actual mailboxes (people's inboxes) live behind that server.

Reading an MX record

Open a terminal and run:

dig MX gmail.com +short

You will see something like:

5 gmail-smtp-in.l.google.com.
10 alt1.gmail-smtp-in.l.google.com.
20 alt2.gmail-smtp-in.l.google.com.
30 alt3.gmail-smtp-in.l.google.com.
40 alt4.gmail-smtp-in.l.google.com.

Two things to understand:

• The number is the priority. Lower numbers are tried first. If the priority-5 server is unreachable, the sender tries priority-10, then 20, and so on.
• The hostname is the actual mail server. It will then have its own A or AAAA record pointing to one or more IP addresses.

Why MX records matter for senders

You probably do not run a mail server. You use Gmail, Microsoft 365, Mailchimp, SendGrid. But MX records affect you in two ways:

1. Receiving. If your domain's MX is misconfigured, you stop getting email entirely. Customers cannot reach you. New signups never confirm.
2. Sending. Some mailbox providers check the sender's domain has working MX as a baseline trust signal. A domain with no MX is a red flag.

How email verification uses MX records

When you verify an address like name@acme.com, the verifier does:

1. Look up MX for acme.com.
2. If no MX record exists, mark the address invalid (the domain cannot receive mail).
3. If MX exists, connect to the highest-priority server.
4. Run the SMTP handshake to test whether the specific mailbox exists.

So MX lookup is the gate. Many obviously-bad domains fail this step in under 100 milliseconds before any SMTP probe is needed.

The most common MX mistakes

• No MX record. Domain registered but mail not configured. The domain cannot receive email at all.
• MX pointing to an A record at the same domain. Standards-compliant, but some providers reject it. Always point MX to a hostname, never to an IP.
• Multiple MX records with the same priority and no failover. Works, but if one server goes down, half your mail bounces. Use different priorities for proper failover.
• MX records for a parked domain. If you bought a domain "just in case", you probably do not have MX set up. That is fine until someone tries to email info@yourdomain.com and it bounces. Either configure MX or set up email forwarding.

Where to check your own MX

Open mxtoolbox.com or run dig MX yourdomain.com in a terminal. Confirm the records match what your mail provider (Google Workspace, Microsoft 365, Fastmail, etc.) instructed.

FAQ

Do I need an MX record to send email?

To receive, yes. To send, technically no, but mailbox providers are increasingly suspicious of domains with no MX. Set it up either way.

How quickly do MX changes take effect?

DNS changes propagate worldwide in minutes to hours. The TTL on your records tells caching resolvers how long to hold the old value. Set TTL to 300 seconds before a planned change so the swap is fast.

Can MX records be used for anything besides email?

No. They exist for one purpose only.

Verify any address now

MailoClean's verifier handles the MX lookup, SMTP handshake, and everything in between automatically. Try a free single check.