MX records decide where mail for a domain goes. When mail stops arriving, or bounces with a “domain not found” style error, the MX set is the first thing to read. This page shows how to check MX records and what each outcome means.
Key facts:
- An MX record names a mail server and a priority number, and senders try the lowest number first (RFC 5321).
- Records with the same priority share the load, and higher numbers act as backups (RFC 5321).
- A Null MX is a single record with priority 0 and the host
., which says the domain accepts no mail (RFC 7505). - Per the BillionVerify MX Lookup, results are sorted by priority and the tool names the provider when the host matches a known one.
- Per the BillionVerify MX Lookup, known providers include Google Workspace, Microsoft 365, Zoho Mail, Proton Mail, Fastmail, Mimecast and Proofpoint.
How to check MX records
- Enter the domain after the @ sign, such as
example.com. Do not enter a full email address or a URL. - Run the lookup.
- Read the priority column first, then the mail server names.
Each row is one server. A typical business domain shows a handful of rows from the same provider.
What the MX result tells you
A list of servers with priorities
The lowest number gets mail first. If the list matches the provider you pay for, the domain is wired to receive mail. A mismatch is a common cause of lost mail after a migration. The old host may still be listed, or a new one may be missing.
A mail provider line
When a host belongs to a provider the tool knows, it adds a line such as “Mail provider: Google Workspace”. Use it to confirm which system receives mail. If the line is absent, the host belongs to a self-hosted or less common provider, so read the host names yourself.
Null MX
The tool says the domain accepts no email. This is a deliberate setting. Mail sent to such a domain is rejected, and you should remove those addresses from your list.
No MX records found
The domain has no MX records, or the name does not exist. The tool does not tell those two cases apart, and both show the same message. Some servers fall back to the domain’s A record when no MX exists (RFC 5321), so a missing MX is not always a hard failure. Check the spelling first.
When the MX is right but mail still fails
An MX set only shows where a domain receives mail. It does not show whether one mailbox exists. A domain can have perfect MX records and still reject a user name that was never created. That rejection is what bounces your campaign.
To see if a mailbox exists, check the address directly. The free tier is 20 checks every 24 hours per IP, no sign-up.
MX records also need working hosts behind them. Each MX name must resolve to an address, and it should not be a CNAME (RFC 2181). Use a DNS lookup on the host to confirm.
What to check next
If receiving works, look at sending. Check the SPF, DKIM and DMARC records for the domain you send from. For single addresses that bounce, run the verifier on billionverify.com to separate a bad address from a bad domain.