What Are MX Records and Why They Matter
An MX record is a DNS entry that says which servers accept email for a domain. Without one, a domain cannot receive mail at all — which makes MX lookup the fastest way to rule out an entire domain's worth of addresses.
What they look like and how they work
An MX record pairs a priority number with a hostname. A domain usually publishes several:
example.com. MX 10 mail1.example.com. / example.com. MX 20 mail2.example.com.
Lower numbers are tried first. The second record is a fallback for when the first is unreachable, which is why a verifier that gives up after one failed connection produces false negatives on domains that are perfectly healthy.
When anyone sends mail to the domain, their server looks up these records, picks the lowest-priority host available, and connects to it.
Checking a domain's MX records
On macOS or Linux: dig MX example.com +short
On Windows: nslookup -type=mx example.com
If the command returns nothing, the domain has no mail servers. Every address at that domain will bounce, no matter how plausible it looks.
Why they matter for verification
MX lookup is the cheapest meaningful check available. It is a single DNS query, it covers every address at a domain at once, and on a neglected list it eliminates a real share of the work before anything expensive happens.
The common case it catches is an expired or parked domain: the company folded, the registration lapsed, and the domain now resolves to a holding page with no mail configuration. Every contact there is dead, and one lookup tells you so.
What it cannot do is tell you about an individual mailbox. A domain with healthy MX records may still have deleted the specific person you are asking about, which is why the SMTP stage exists.
Cases that confuse people
- A null MX record — a single record pointing at '.' which explicitly declares that the domain accepts no mail. Treat it as definitive.
- MX pointing at a provider — most domains point at Google, Microsoft or a hosting provider rather than their own servers. Entirely normal.
- No MX but an A record — some senders will fall back to the A record, but this is legacy behaviour and unreliable in practice. Treat the domain as not accepting mail.
- Records that resolve to nothing — the MX hostname exists but has no address, which means mail cannot be delivered despite the record being present.
If you are configuring your own domain
Publish at least two MX records with different priorities so a single server failure does not stop your mail. Point them at hostnames, never at IP addresses, which is invalid. Allow for DNS propagation after changes — up to 48 hours, though usually far less.
MX records govern receiving only. Sending is governed by SPF, DKIM and DMARC, and a domain with perfect MX records can still have all its outbound mail rejected if those are wrong.
Common questions
Can a domain receive email without MX records?
In principle some senders fall back to the domain's A record, but this is legacy behaviour that many modern servers no longer follow. In practice, no MX records means mail will not arrive reliably, and verification treats the domain as unable to receive.
Why does a domain have multiple MX records?
For redundancy. The priority number decides the order; lower is tried first, and the others take over when the preferred server is unreachable.
Does having MX records mean an address is valid?
No. It means the domain can receive mail. Whether one particular mailbox exists requires an SMTP check against the server those records point to.