Email authentication
DMARC setup checklist and deliverability diagnostics
The five-step setup status, the ranked diagnostic that answers why mail is going to spam, and the two-week / 95% rule before tightening policy.
Updated · 2 min read
Two endpoints do the thinking so you do not have to read reports by hand. Both are Starter and up, because they join the DNS scan with 30 days of DMARC reports.
The setup checklist
GET /api/dmarc/setup-status?domain=… (the setup panel on the web and in the app; tool get_dmarc_setup_status) returns five steps, each with a state:
- SPF - a valid TXT record at the apex.
- DKIM - a key published for the provider that sends your mail.
- DMARC - the
_dmarcTXT record, generated by DomainGuard with your report address. - Wait for reports - the first should arrive within 24 to 48 hours.
- Inbox routing -
rua=points at DomainGuard's address and not somewhere else.
Steps 4 and 5 are the two people get wrong. A checklist that looks finished but has rua= pointed at a mailbox nobody reads produces no reports and looks broken.
The diagnostic
GET /api/dmarc/diagnostics?domain=… (the "Why is my email going to spam?" card; tool get_dmarc_diagnostics) returns the inputs it used and a ranked list of findings, most likely cause first, each with its own fix:
| Input | Meaning |
|---|---|
dmarc_status, current_policy, current_pct |
From the latest DNS scan |
days_observed |
Days of reports received |
total_messages, alignment_rate |
Volume and the share passing SPF or DKIM |
days_since_latest_report |
Whether reports have stopped |
The failure modes it distinguishes: missing DMARC record, broken DMARC record, an unrecognised sender with material failure, a misconfigured sending service, and reports having stopped arriving. Lead with the first entry; the rest are ordered by likelihood.
When to tighten the policy
A domain is safe to move off p=none when it has two weeks of reports with 95% of mail passing SPF or DKIM. Both halves matter: high alignment with four days of data is not evidence, and two weeks at 60% alignment means something is still misconfigured. The diagnostic reports days_observed and alignment_rate against that rule.
Move none to quarantine, watch another two weeks, then reject. Managed email authentication can make those moves for you without further DNS edits.
Where
- Web: Monitor, DMARC, the Setup and Diagnostics cards; also the domain's Email & DMARC module.
- iOS: the DMARC page under a domain's Email & DMARC module.
Common questions
The diagnostic says "reports stopped". Check that the DMARC record still carries the current rua= address (rotating the inbox changes it) and that the record was not replaced by a provider's setup wizard.
Alignment is 99% but one sender fails. That sender is usually a form plugin, a CRM or a printer sending as your domain without being in SPF. Add it to SPF or configure DKIM for it; the senders list names the IP and, where recognised, the provider.
Keep reading
Related articles
- The domain setup guideThe per-domain checklist computed from what is actually set up: first check, alerts, email records, DMARC reports, ownership proof, monitoring and more.Getting started ·Updated
- MX, MTA-STS, TLS-RPT and BIMIWhere your mail is delivered, the records that force encrypted delivery and report on failures, and the optional brand-logo record.Email authentication ·Updated
- Managed email authenticationDelegate your DMARC record to DomainGuard with one CNAME so the policy can be advanced without further DNS edits, and let DomainGuard flatten your SPF.Email authentication ·Updated
