MX records tell other mail servers where to deliver email for your domain. Each has a priority and a host. Senders try the lowest number first and fall back to higher ones; records with the same number share the load.
- Google Workspace: new setups use one record,
1 smtp.google.com. Older setups with five aspmx.l.google.comrecords still work. - Microsoft 365: one record like
0 example-com.mail.protection.outlook.com (your domain with dashes). - No MX at all: mail to the domain bounces. A "null MX" (
0 .) is the standard way to say a domain receives no email. - The MX host must be a name with its own A or AAAA record: not an IP address and not a CNAME. Some senders reject mail when the MX points to an alias.
Delivery also depends on two TXT records. SPF (v=spf1 …) lists the servers allowed to send as you; a domain may have only one, and evaluating it may take at most 10 DNS lookups (each include:, a, mx, exists: and redirect= counts, nested includes too). DMARC at _dmarc.example.com tells receivers what to do when SPF and DKIM fail: p=none only monitors, p=quarantine sends to spam, p=reject blocks. The Email tab checks all of these, counts the SPF lookups, and can test a DKIM selector.