An MX (Mail Exchanger) record is a DNS entry that says: 'to deliver email for example.com, connect to this mail server.' Without it, no inbound email reaches you — the sender's server queries DNS, finds no MX, and bounces. Check any domain's MX in a second with Zro7 MX Lookup.
The 30-second mental model
- You send mail to [email protected].
- Your outgoing server asks DNS: 'MX for example.com?'
- DNS answers with a list of hostnames + priorities, e.g. '10 aspmx.l.google.com'.
- Your server connects to the lowest-priority (highest preference) host and delivers the message.
Anatomy of an MX record
- Priority: lower = tried first. Ties are load-balanced.
- Exchange: a hostname (not an IP). That hostname must have its own A/AAAA records.
- TTL: how long resolvers cache it. Lower TTLs make migrations faster.
Typical MX configurations
- Google Workspace: single line,
1 smtp.google.com(new style) or five aspmx entries (legacy). - Microsoft 365:
0 example-com.mail.protection.outlook.com. - Fastmail: two records, priority 10 and 20.
- Self-hosted: usually
10 mail.example.com.
MX alone isn't enough — the deliverability trio
- SPF (TXT): which servers may send as your domain.
- DKIM (TXT): cryptographic signature proving the message wasn't tampered.
- DMARC (TXT): what to do when SPF/DKIM fails.
Common MX mistakes
- Pointing MX at an IP address — invalid, must be a hostname.
- Missing A record for the MX hostname.
- Trailing dot confusion — cPanel and Cloudflare handle it differently.
- Two identical priorities when only one is intended.
How to check yours
- Open Zro7 MX Lookup.
- Enter your domain (no @, no www).
- Confirm the hostname matches your email provider's documentation.
- Cross-check SPF/DKIM/DMARC with DNS Lookup.
Updated December 28, 2026 · Zro7 editorial team.
Zro7