What this check looks at
“Who receives mail for this domain.” - the wording shown beside this check while it runs.
An MX record - mail exchanger - tells the rest of the world which servers accept mail for your domain. It governs mail coming in. It says nothing about who may send mail as you; that is what SPF, DKIM and DMARC are for.
Why it matters
It tells you which mail platform you are actually on, which decides where your DKIM keys come from and which sending servers your SPF record needs to authorise. A finding of Microsoft 365 or Google Workspace here is the strongest hint about what the rest of your setup should look like.
A domain with no MX cannot receive mail - including replies, and including the verification mail a provider sends you. That is a real outage if it is unintended, and completely correct if the domain was never meant to receive.
What each verdict means here
- Pass
- The domain publishes mail servers and they look sane.
- Warn
- The records are present but questionable - for example a host that does not resolve.
- Not applicable
- No MX records, and nothing here suggests the domain is meant to receive mail. A parked or send-only domain with no MX is configured correctly, so this is not counted against the score.
What to do
- If the domain should receive mail and has no MX, publish the records your mail provider gives you.
- If the domain should never receive or send mail, the strongest configuration is an empty SPF and a reject DMARC policy - see the SPF and DMARC checks.
What this check does not do
We read the records. We do not connect to your mail servers, send test mail, or read any mailbox.