Troubleshooting
Each page starts from what you see and lists what to check, in order. If none of them fits, write to support.
- No DMARC reports are arriving
When no DMARC reports arrive: check the record at _dmarc, the rua address, whether the domain sent any mail, and whether we refused the report mail.
- The domain does not verify
When the domain does not verify: the TXT record's name and value, DNS hosts that add your domain to the name, when we check, and Cloudflare.
- Publishing through Cloudflare fails
Each error the Cloudflare publish button can show, from a token Cloudflare no longer accepts to a zone in another account, and what to change.
- I set up DKIM, but the source still fails
DKIM is set up but the source still fails DMARC: old days in the reports, a service that still signs with its own domain, a wrong key, strict alignment.
- An alert says a DKIM key is missing
A selector that signed your mail lately has no DKIM key in DNS now. Find the service, publish its key again, or let the alert clear by itself.
- Forwarded and mailing-list mail fails DMARC
Why forwarding and mailing lists make mail fail DMARC, what the explanations say about it, and why there is usually nothing to fix on your side.
- DMARC passes, but mail still goes to spam
Passing DMARC proves the mail is yours, not that recipients want it. What else mailbox providers weigh, and what your DMARC reports can and cannot show.
- SPF has too many DNS lookups
Your SPF record needs more DNS lookups than the limit allows. How we count them, which includes cost the most, and what to remove first.
- Alert or summary emails do not arrive
Alert or summary emails missing: your own settings, the plan's pace, alerts that are quiet on purpose, and what summaries need before they are sent.
- A chat channel says it failed
An alert did not reach Slack, Microsoft Teams or another shared channel: what each result and error in the delivery log means, and how to fix it.
Published 27 October 2026 · Checked 27 October 2026