What is an MX record?
An MX (Mail Exchange) record is a DNS entry that specifies which mail server is responsible for receiving email for a domain. Without a valid MX record, a domain cannot accept email, so checking MX is a fast first step in verifying an address.
What MX records do
When a sender wants to deliver mail to user@example.com, it queries DNS for example.com's MX records to learn which server handles incoming mail. The MX record points to a hostname (like mail.example.com), and a domain can list several with priority values so mail can fail over to a backup server.
MX records are what make email routing work across the internet. They're configured by whoever manages the domain's DNS, and they change when a company switches email providers — for example from self-hosted mail to Google Workspace or Microsoft 365.
Why MX matters for verification
If a domain has no MX record (and no fallback A record set up for mail), it simply cannot receive email — every address at that domain is undeliverable. Checking MX is therefore a cheap, fast filter that rules out entire dead domains before any slower SMTP probing.
A valid MX record doesn't prove a specific mailbox exists, but its absence proves the address can't work. Mailbeam returns an mx_check boolean in every response and uses it as an early gate in the verification pipeline.
MX checks in practice
An MX lookup is a DNS query, so it's fast and puts no load on the recipient's mail server. It's ideal for pre-filtering large lists: drop the addresses on domains with no mail infrastructure, then run the more expensive checks only on the survivors.
It also helps diagnose delivery problems — if your mail to a domain is failing, a missing or misconfigured MX record is a common culprit.
An MX answer, and the one that means 'never'
MX records list the hosts that accept mail for a domain, lowest preference first. One special form says the opposite.
$ dig +short MX example.com
10 mx1.example.com.
20 mx2.example.com.
^
preference: try 10 first, fall back to 20.
Equal values are used in no guaranteed order.
$ dig +short MX no-mail.example.com
0 .
^
null MX (RFC 7505): this domain accepts no mail at all.
Not a misconfiguration - an explicit, citable declaration.A null MX record of “0 .” is a domain declaring under RFC 7505 that it accepts no mail, which makes every address at that domain undeliverable by definition.
Sources
Checked against these sources on .
In practice
Verifying contact@deadstartup.io, Mailbeam queries DNS and finds no MX record — the domain was abandoned and no longer receives mail. It returns mx: false and marks the address undeliverable immediately, without wasting an SMTP probe.
Frequently asked questions
Verify emails with confidence
Mailbeam handles all of this for you — syntax, MX, SMTP, catch-all, and disposable checks in one API call. 1,000 free verifications/month, no credit card.