What it means
One of your mail servers resolves to a private or reserved address, such as 10.0.0.25 or 192.168.1.10. These addresses work only inside a local network.
Why it matters
Senders on the internet can't reach a private address, so they skip that server or fail to deliver. It usually happens when an internal DNS record leaks into public DNS, or when a server moved and its public record was replaced with the internal one.
How to fix it
- Find the mail server named in the finding's detail.
- Change its A record in your public DNS to the public address your provider or firewall uses for incoming mail.
- Keep internal addresses in your internal DNS only.
- If the server is no longer used, remove its MX record.
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.