Domain has no MX records — when that is fine and when it is not
MX records tell other servers where to deliver mail addressed to your domain. Without them, inbound mail bounces.
For a send-only domain used purely for marketing, that can be intentional — but replies and bounce notifications then vanish, which is a poor experience and a deliverability signal in its own right.
If a domain will never receive mail, say so explicitly with a null MX record rather than leaving it blank.
How to fix it
- 1If the domain should receive mail, add the MX records your provider documents.
- 2If it should never receive mail, publish RFC 7505 null MX: an MX record with priority 0 and a single dot as the target.
- 3Either way, keep SPF and DMARC published — a non-receiving domain can still be spoofed.
Check whether your domain has this problem
Free, no signup, about two seconds. You get the exact record to paste.
Related guides
- DKIM record with empty p= — a revoked key still in use
- SPF include points at a domain with no SPF record — a silent PermError
- DMARC record syntax errors that make receivers skip your policy
- DMARC external destination not authorized — why you receive no reports
- Two DMARC records at _dmarc — why your policy is being ignored