Email deliverability
How to set up a DMARC record
What 13x checks
This is rule deliverability.dmarc in the public registry: DMARC record is present and enforcing. 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
- 11 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.
Publish a DMARC record on the _dmarc subdomain:
Type: TXT
Name: _dmarc (i.e. _dmarc.example.com)
Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com; pct=100; adkim=s; aspf=sThen walk the policy up. Do not start at reject:
1. `p=none` for two to four weeks. Nothing is blocked; the rua address receives daily XML reports showing every source sending as you. Read them — the surprise is usually a forgotten invoicing tool or CRM.
2. `p=quarantine` once only your own senders pass. Failures go to spam rather than the inbox.
3. `p=reject` once quarantine causes no complaints. Failures are refused outright.
The reports are XML and unreadable by hand; point rua at a free parser such as Postmark's DMARC digests or dmarcian.
Since February 2024, Google and Yahoo require DMARC for anyone sending more than 5,000 messages a day to their users. Below that it is still what stops your domain being spoofed.
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.