Built for agencies and B2B sales teams.

Start free →

Free MX Record Checker

Enter a domain to look up its mail exchangers, priority order and inbound routing configuration.

Current DNSPriority analysisActionable results
MX CheckerFreeExample result
No email address needed
HEALTHY

MX routing status: Healthy

MX records2
Primary priority10
Mail providerDetected from MX
Priority orderClear
DNS responseComplete
PriorityMail exchangerRouting roleDetail
10mx1.mail-provider.examplePrimaryResolves to an IP
20mx2.mail-provider.exampleBackupResolves to an IP
Explicit MX routing found
Priority order is visible
How it works

How to use the MX Checker

  1. 01

    Enter the receiving domain

    Use the domain that receives your mail.

  2. 02

    Review hosts and priorities

    Check the exchangers and their preference values.

  3. 03

    Fix DNS and recheck

    Correct any route, wait for propagation and run it again.

What it checks

What the MX Checker checks

Mail exchanger lookup

Every MX host a domain publishes.

Priority explained

Lower values are tried first.

Routing diagnostics

Missing, stale and null MX routes.

Post-change verification

Confirm a migration finished.

Reading results

How MX priority works

Senders try the lowest preference value first, then move to higher values if it is unreachable.

PreferenceTypical roleWhat it means
10PrimaryTried first
20BackupTried if the primary does not answer
30Secondary backupTried last
0 with a root exchangeNull MXThe domain does not accept email
Details

A healthy MX configuration

At least one intended route

The mail exchangers you expect are published.

Intentional priority order

Each preference value is there on purpose.

No accidental null MX

A null MX should not sit beside normal MX records.

Common issues

Common problems and how to fix them

No expected MX records

Mail falls back to address records. Publish explicit MX records instead.

Old provider routes still published

After a migration, remove routes to the previous provider.

Null MX on a mail-enabled domain

A null MX tells senders the domain accepts no mail.

Unexpected priority values

A wrong value can send mail to a backup first.

Provider detection is best-effort

Automated platform detection is best-effort. The authoritative configuration comes from your mailbox provider or mail administrator. For Google Workspace and Microsoft 365, compare the live MX records with the provider's admin console or documentation. Microsoft 365 destinations commonly end in mail.protection.outlook.com.

Use cases

When to run this check

Mail exchanger lookup

See where a domain's mail is delivered.

Routing diagnostics

Find out why replies or bounces go missing.

Post-change verification

Confirm an MX update after a provider move.

FAQ

MX Checker FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is an MX record checker?

It queries DNS for a domain's Mail Exchange records and shows their destinations and preference values, so you can confirm how inbound mail is routed.

What does MX priority mean?

Lower numbers are preferred. A record with priority 10 is typically tried before one with priority 20. Equal values can represent equivalent routes.

Can a domain have multiple MX records?

Yes, for redundancy or during a migration. Each host and priority should be intentional.

What happens when there is no MX record?

SMTP can fall back to address records, but relying on that is not recommended for business domains. Explicit MX records make routing predictable.

What is a null MX?

A record with preference 0 and a root exchange. It means the domain accepts no email, and it should not coexist with normal MX records.

Does MX affect cold email deliverability?

MX governs inbound routing. A broken MX can block replies. Outbound deliverability depends mainly on SPF, DKIM, DMARC, reputation and sending behavior.

How do I verify Google Workspace MX records?

Compare the destinations and priorities with the current Google Workspace setup guidance, since the recommended values can change.

How do I verify Microsoft 365 MX records?

Compare them with the tenant-specific destination in the Microsoft 365 admin center, which usually ends in mail.protection.outlook.com.

Why do I still see an old provider in my MX records?

Either the authoritative zone still publishes the record, or a cached answer is appearing during propagation. Check authoritative DNS first.

Does a healthy MX result guarantee inbox placement?

No. Inbox placement depends on authentication, reputation, complaints, engagement, list quality, content and filtering.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.