Mail exchanger lookup
Every MX host a domain publishes.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Enter a domain to look up its mail exchangers, priority order and inbound routing configuration.
MX routing status: Healthy
| Priority | Mail exchanger | Routing role | Detail |
|---|---|---|---|
| 10 | mx1.mail-provider.example | Primary | Resolves to an IP |
| 20 | mx2.mail-provider.example | Backup | Resolves to an IP |
Use the domain that receives your mail.
Check the exchangers and their preference values.
Correct any route, wait for propagation and run it again.
Every MX host a domain publishes.
Lower values are tried first.
Missing, stale and null MX routes.
Confirm a migration finished.
Senders try the lowest preference value first, then move to higher values if it is unreachable.
| Preference | Typical role | What it means |
|---|---|---|
| 10 | Primary | Tried first |
| 20 | Backup | Tried if the primary does not answer |
| 30 | Secondary backup | Tried last |
| 0 with a root exchange | Null MX | The domain does not accept email |
The mail exchangers you expect are published.
Each preference value is there on purpose.
A null MX should not sit beside normal MX records.
Mail falls back to address records. Publish explicit MX records instead.
After a migration, remove routes to the previous provider.
A null MX tells senders the domain accepts no mail.
A wrong value can send mail to a backup first.
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.
See where a domain's mail is delivered.
Find out why replies or bounces go missing.
Confirm an MX update after a provider move.
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.
Lower numbers are preferred. A record with priority 10 is typically tried before one with priority 20. Equal values can represent equivalent routes.
Yes, for redundancy or during a migration. Each host and priority should be intentional.
SMTP can fall back to address records, but relying on that is not recommended for business domains. Explicit MX records make routing predictable.
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.
MX governs inbound routing. A broken MX can block replies. Outbound deliverability depends mainly on SPF, DKIM, DMARC, reputation and sending behavior.
Compare the destinations and priorities with the current Google Workspace setup guidance, since the recommended values can change.
Compare them with the tenant-specific destination in the Microsoft 365 admin center, which usually ends in mail.protection.outlook.com.
Either the authoritative zone still publishes the record, or a cached answer is appearing during propagation. Check authoritative DNS first.
No. Inbox placement depends on authentication, reputation, complaints, engagement, list quality, content and filtering.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.