Skip to content

Email deliverability

My domain cannot receive email

Anyone replying to your launch announcement gets a bounce, and the support address in your Impressum or privacy policy does not work. It also weakens outbound reputation: receivers are wary of domains that send but cannot receive.

What 13x checks

This is rule deliverability.mx in the public registry: The domain can receive mail. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.

Surface
Email deliverability
Score weight
5 of the readiness score
Scope
Runs on every audited page
Applies
Only where the market or the page shape makes it relevant

Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.

The fix

The same text the audit hands you when this check fails on your own site.

Add MX records so the domain can receive mail. For Google Workspace:

Configuration
Type: MX   Name: @   Priority: 1   Value: smtp.google.com

For Microsoft 365:

Configuration
Type: MX   Name: @   Priority: 0   Value: example.com-com.mail.protection.outlook.com

If you do not want a full mailbox, a forwarding-only service (Cloudflare Email Routing, ImprovMX) gives you a working hello@example.com for free — which is enough to satisfy the contact address in your legal pages and to receive replies to your launch announcement.

Sending from a domain that cannot receive also hurts your reputation: receivers treat it as a spam signal.

Does your site have this problem?

13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.

No signup. Results in 30 seconds.

More email deliverability checks