An MX lookup shows which mail servers receive inbound mail for a domain and in what priority order other mail systems should try them.
If you are searching for , , , or , the practical goal is usually one of three things: confirm the domain can receive mail, verify a provider migration, or troubleshoot why inbound mail is going to the wrong place.
Quick answer
An MX lookup should tell you:
- whether the domain publishes MX records at all
- which hostnames receive inbound mail
- which server is preferred based on priority
- whether the published targets match the provider you expect
If MX records are missing or wrong, the domain may stop receiving email even when SPF, DKIM, and DMARC are configured correctly.
What an MX lookup result means
MX stands for Mail Exchanger. These records tell sending systems where to deliver mail for the domain.
A typical result looks like this:
That means:
is the preferred inbound targetis the lower-priority backup
Lower numbers mean higher priority.
What to check in an MX lookup
Do not stop at "records found." Review all of these:
- at least one MX record exists
- priority values make sense
- every MX hostname resolves correctly
- the published hostnames belong to the intended provider
- old provider targets are not still present after migration
This matters because a record can be syntactically valid while still routing mail to the wrong place.
How to run an MX lookup
Use this workflow:
- query the domain for MX records
- list the target hostnames and priority values
- confirm the highest-priority server matches your intended provider
- verify all target hostnames resolve
- compare the result with live inbound behavior
If you need the broader reference guide behind the DNS concepts, use MX records guide.
How MX priority works
Priority numbers determine the order in which remote mail systems should try the listed destinations.
| Priority value | Meaning |
|---|---|
| Lower number | Higher preference |
| Higher number | Lower preference |
| Equal numbers | Usually load sharing or provider-specific behavior |
Priority does not reflect trust or reputation. It only reflects routing preference.
If the backup server has the lower number by mistake, mail can be routed into the wrong environment even though the domain technically has valid MX records.
When to use an MX lookup
An MX check is especially useful during:
- new domain setup
- mailbox-provider migration
- support incidents involving missed inbound email
- verification and signup workflow testing
- catch-all and alias troubleshooting
Teams also use MX lookups before enabling email verification or inbound routing features to confirm the domain is configured to receive mail at all.
MX lookup vs SPF, DKIM, and DMARC
These are related but different controls.
| Record type | Main purpose |
|---|---|
| MX | Inbound mail routing |
| SPF | Outbound sender authorization |
| DKIM | Message signing and domain integrity |
| DMARC | Alignment and receiver policy |
A domain can have perfect SPF and DKIM and still fail to receive email if MX records are wrong. Likewise, clean MX records do not guarantee outbound trust.
Use MX checks with:
Common MX record problems
No MX records published
If a domain has no MX records, many systems treat it as not properly configured for mail reception.
Wrong provider after migration
The domain still points to the previous mailbox provider, or only part of the migration completed.
Priority order is reversed
A backup or legacy system is accidentally preferred over the primary destination.
Target hostname does not resolve
The MX record exists, but the hostname it points to has broader DNS issues or was decommissioned.
Mixed-provider configuration
Two different providers appear in the MX set without a deliberate design, which can create inconsistent routing and hard-to-debug support issues.
MX troubleshooting workflow
When inbound mail is not arriving as expected:
- run an MX lookup
- confirm the intended provider hostnames are present
- verify every target resolves
- send test mail and compare observed routing
- check whether support issues align with DNS-change timing
If the domain is used in account signup or email verification flows, pair routing checks with Check Email Verification and Email deliverability test so you validate both inbound readiness and send-side behavior.
MX lookups in verification workflows
MX checks are useful because they help answer a simple but important question: can this domain receive mail in a sane way right now?
That is relevant for:
- signup and verification emails
- contact forms
- inbound parsing and reply handling
- domain-quality reviews during onboarding
Supporting pages:
Use MailSlurp for MX-dependent email checks
MX lookup sits in the Messaging foundation: it tells you whether a domain is ready to receive mail before you layer on verification, parsing, or automated tests.
MailSlurp is useful when MX lookups need to feed into a broader implementation workflow instead of staying as a one-off DNS check.
Use:
- DNS lookup to inspect related records
- Check Email Verification when recipient and domain quality matter before send
- Email integration testing when inbound and outbound message flows need automated assertions
Create an account at app.mailslurp.com to start wiring MX checks into your email QA and verification workflow.
FAQ
What is an MX lookup?
It is a DNS lookup that shows which mail servers receive email for a domain and what order remote systems should try them in.
What does MX stand for?
MX stands for Mail Exchanger.
What is the difference between MX lookup and SPF check?
MX is about inbound routing. SPF is about who is allowed to send outbound mail for the domain.
Can a domain receive email without MX records?
Sometimes mail systems fall back to the A record, but that is not a reliable production setup. A proper mail-receiving domain should publish explicit MX records.
Final take
An MX lookup is one of the fastest ways to verify whether a domain is actually ready to receive mail. It is especially valuable during migrations, onboarding, and troubleshooting because routing mistakes are easy to publish and easy to miss until users stop receiving messages.