MX (Mail Exchange) records tell the internet which servers handle email for your domain. Without MX records, your domain cannot receive email.
When someone sends an email to you@yourdomain.com, their mail server needs to find out where to deliver it. It does this by looking up the MX records for yourdomain.com.
Sender's server queries DNS for MX records of your domain.
Records are sorted by priority (lower number = higher priority).
Sender tries the highest priority server first, falling back to others if needed.
The mail server accepts the email and places it in your mailbox.
MX records have a priority value. Lower numbers = higher priority. If you have multiple MX records, mail servers will try them in order of priority.
Example:
10 mail1.example.com (tried first)
20 mail2.example.com (tried if mail1 fails)
30 mail3.example.com (tried if mail2 fails)Without MX records, mail servers don't know where to deliver email for your domain. Any email sent to your domain will bounce.
Adding MX records depends on your email provider. You need to:
A null MX record (priority 0, server ".") is a special record defined in RFC 7505 that explicitly states "this domain does not receive email."
A null MX looks like:
0 .A null MX is appropriate for:
If your domain should receive email, you need to replace the null MX with actual mail server records. Simply:
Here are the MX records for popular email providers. Copy these exactly, including priorities.
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.COM0 yourdomain-com.mail.protection.outlook.comReplace "yourdomain-com" with your domain (dots become dashes).
Microsoft's official documentation10 mx.zoho.com
20 mx2.zoho.com
50 mx3.zoho.comUse zoho.eu or zoho.in if your account is in those regions.
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com10 mail.protonmail.ch
20 mailsec.protonmail.chAfter making changes, use our checker to confirm everything is configured correctly.