MXBreaks authentication
No MX record: this domain can't receive email
Without MX records, mail to your domain can't be delivered, so replies to your outreach bounce. Add the MX records from your email provider.
What it means
MX records tell other servers where to deliver mail addressed to your domain. With none, senders fall back to the domain's own address, which almost never runs a mail server, and the mail bounces.
Why it matters for cold email
Prospects reply to the address you sent from. With no MX, every reply bounces, and receivers treat a domain that can't receive mail as suspicious for sending too.
How to fix it
- In your email provider's setup guide, find the MX records for your domain.
- Add them at your DNS provider with the priorities given, and remove MX records from any provider you've left.
- Re-check the domain.
Google Workspace (host @)
Record
MX 1 smtp.google.com
Questions
I only send from this domain. Do I still need MX?
Yes, if anyone might reply. For a sending-only subdomain, point replies to your main domain with a Reply-To address and keep MX on the main domain.
Related problems
Last checked 2026-10-21 against RFC 7208 (SPF), RFC 6376 (DKIM) and RFC 7489 (DMARC). Full setup guide
Sending cold email? Outsquid re-checks these records for every sending domain every hour, so a broken one doesn't go unnoticed. How deliverability works