MX Records by Email Provider: Setup Guides and Record Values
Find the correct MX records for every major email provider. Quick-reference table and setup guides for Google, Microsoft 365, Zoho, and more.
Last updated: 2026-04-06
Every email provider requires different MX records. Getting the wrong hostname or priority value means email won't reach your inbox.
This page is a quick-reference for the correct MX records across all major providers, with links to detailed setup guides. If you're setting up email for the first time or switching providers, start here.
For the broader context on how MX records work, see the Complete Guide to MX Records.
Quick Reference Table
| Provider | MX Records | Primary Hostname | Type |
|---|---|---|---|
| Google Workspace | 5 | aspmx.l.google.com | Business |
| Microsoft 365 | 1 | *.mail.protection.outlook.com | Business |
| Zoho Mail | 3 | mx.zoho.com | Business |
| ProtonMail | 2 | mail.protonmail.ch | Business/Personal |
| Fastmail | 2 | in1-smtp.messagingengine.com | Business/Personal |
| iCloud | 2 | mx01.mail.icloud.com | Personal |
| Yahoo Business | 2 | mx1.biz.mail.yahoo.com | Business |
| Amazon WorkMail | 1 | inbound-smtp.*.amazonaws.com | Business |
| Rackspace | 2 | mx1.emailsrvr.com | Business |
| Titan | 2 | mx1.titan.email | Business |
| Migadu | 2 | aspmx1.migadu.com | Business/Personal |
| MXroute | 2 | Account-specific | Business/Personal |
| IceWarp | 2 | mx1.icewarp.com | Business |
| Tuta | 1 | mail.tutanota.de | Business/Personal |
| Mailgun | 2 | mxa.mailgun.org | Transactional |
| SendGrid | 1 | mx.sendgrid.net | Transactional |
Tenant-specific hostnames
Microsoft 365, Amazon WorkMail, and MXroute generate unique hostnames per account. You'll find yours in the provider's admin console. The guides below explain where to find it.
Business Email Providers
These are full email platforms for organisations: mailboxes, calendars, contacts, and collaboration tools.
Google Workspace
Google uses five MX records with a tiered priority structure for maximum redundancy:
| Priority | Hostname |
| 1 | aspmx.l.google.com |
| 5 | alt1.aspmx.l.google.com |
| 5 | alt2.aspmx.l.google.com |
| 10 | alt3.aspmx.l.google.com |
| 10 | alt4.aspmx.l.google.com |
All five records are required. Google load-balances across them automatically.
Full guide: Google Workspace MX Records
Microsoft 365
Microsoft uses a single tenant-specific MX record:
| Priority | Hostname |
| 0 | yourdomain-com.mail.protection.outlook.com |
Replace yourdomain-com with your actual domain (dots become dashes). Find the exact value in the Microsoft 365 admin center under Domains.
Full guide: Microsoft 365 MX Records
Zoho Mail
Zoho uses three MX records with regional variants depending on where your account is hosted:
| Priority | Hostname (US) |
| 10 | mx.zoho.com |
| 20 | mx2.zoho.com |
| 50 | mx3.zoho.com |
If your account is on a regional instance, use the matching domain: .eu, .in, .com.au, or .jp.
Full guide: Zoho Mail MX Records
Yahoo Business Email
| Priority | Hostname |
| 1 | mx1.biz.mail.yahoo.com |
| 5 | mx5.biz.mail.yahoo.com |
Full guide: Yahoo Business MX Records
Amazon WorkMail
Amazon uses a single region-specific MX record:
| Priority | Hostname |
| 10 | inbound-smtp.[region].amazonaws.com |
Replace [region] with your WorkMail region (e.g. us-east-1, us-west-2, eu-west-1).
Full guide: Amazon WorkMail MX Records
Rackspace Email
| Priority | Hostname |
| 10 | mx1.emailsrvr.com |
| 20 | mx2.emailsrvr.com |
Full guide: Rackspace MX Records
Titan Email
| Priority | Hostname |
| 10 | mx1.titan.email |
| 20 | mx2.titan.email |
Full guide: Titan MX Records
IceWarp
| Priority | Hostname |
| 10 | mx1.icewarp.com |
| 20 | mx2.icewarp.com |
For on-premise IceWarp installations, use your own mail server hostname instead.
Full guide: IceWarp MX Records
Privacy-Focused Providers
ProtonMail
| Priority | Hostname |
| 10 | mail.protonmail.ch |
| 20 | mailsec.protonmail.ch |
Full guide: ProtonMail MX Records
Tuta (Tutanota)
| Priority | Hostname |
| 10 | mail.tutanota.de |
Tuta uses a single MX record with no backup. Their infrastructure handles redundancy internally.
Full guide: Tuta MX Records
Independent and Developer-Friendly Providers
Fastmail
| Priority | Hostname |
| 10 | in1-smtp.messagingengine.com |
| 20 | in2-smtp.messagingengine.com |
Full guide: Fastmail MX Records
Migadu
| Priority | Hostname |
| 10 | aspmx1.migadu.com |
| 20 | aspmx2.migadu.com |
Full guide: Migadu MX Records
MXroute
| Priority | Hostname |
| 10 | [your-server].mxrouting.net |
| 20 | [your-server-backup].mxrouting.net |
MXroute assigns unique server hostnames per account. Check your welcome email or account panel for the exact values.
Full guide: MXroute MX Records
iCloud Custom Domain
| Priority | Hostname |
| 10 | mx01.mail.icloud.com |
| 20 | mx02.mail.icloud.com |
Available with iCloud+ subscriptions.
Full guide: iCloud Custom Domain MX Records
Transactional Email Services
These services are for sending application email (receipts, notifications, password resets). They're not full mailbox providers. You typically only point MX records here if you want to receive and process inbound email programmatically.
Mailgun
| Priority | Hostname |
| 10 | mxa.mailgun.org |
| 10 | mxb.mailgun.org |
Equal priorities for load balancing across both servers.
Full guide: Mailgun MX Records
SendGrid
| Priority | Hostname |
| 10 | mx.sendgrid.net |
Full guide: SendGrid MX Records
Switching Providers
When you migrate between email providers:
- Lower your TTL to 300 seconds a day or two before the switch
- Remove old MX records completely. Don't leave them alongside the new ones.
- Add new MX records with the exact values from your new provider
- Verify delivery by sending test emails from an external account
- Raise TTL back to 3600 seconds once everything is confirmed working
Don't leave old and new MX records in place simultaneously. Email will split between providers unpredictably based on priority values and server availability.
For migration specifics, see MX Records After Domain Transfer. For step-by-step instructions on adding records at your DNS host, see How to Add MX Records.
Identify Your Current Provider
Not sure which email provider you're currently using? Run an MX lookup on your domain. The mail server hostnames reveal the provider. See Who is My Email Provider? for how to read the results.
Monitor Your MX Records
After configuring your provider's MX records, don't just set and forget. DNS changes, expired domains, and accidental edits can silently break email delivery.
References
- RFC 5321: Simple Mail Transfer Protocol - Specifies SMTP delivery and MX record lookup procedures
- RFC 1035: Domain Names - Implementation and Specification - Defines the DNS record format, including MX records
- Google Workspace MX record values - Official Google MX setup documentation
- Microsoft 365 DNS records - Official Microsoft 365 DNS configuration guide
Never miss an MX issue
Monitor your SPF, DKIM, DMARC and MX records daily. Get alerts when something breaks.
Start Monitoring