Fail

Your null MX record sits next to other MX records

The short version

Remove the "0 ." MX record if the domain receives email, or remove the others if it doesn't.

What it means

Your domain has a null MX record (priority 0 and the host .) next to normal MX records. A null MX means "this domain accepts no email"; the others say the opposite.

Why it matters

The standard says a null MX must be the only MX record. Senders that respect it refuse to deliver your mail, while others ignore it and use the remaining servers, so some mail is lost and some arrives depending on who sends it.

How to fix it

  1. Decide whether the domain should receive email.
  2. If it should, delete the MX record whose host is . and keep your provider's records.
  3. If it shouldn't, delete the other MX records and keep only the null MX. Pair it with v=spf1 -all and a DMARC policy of reject.

Google Workspace

The MX record is smtp.google.com with priority 1. Older setups list five aspmx hosts, which still work.

Microsoft 365

The MX record is <your domain with dashes>.mail.protection.outlook.com with priority 0; the Microsoft 365 admin center shows the exact name under Settings, Domains.

Check it worked

Run the full email check again once the old record's TTL has passed, usually within an hour. The mail servers section should list every host with its address, and the finding should be gone. Send yourself a test message from another provider to be sure mail arrives.