DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers what to do when a message fails SPF and DKIM alignment, and asks them to send aggregate and forensic reports back to the domain owner.
Checkers and validators#
Free lookup tools confirm that records resolve and are syntactically valid. Primary Deliverability runs SPF, DKIM, DMARC, and BIMI checks in one report and flags alignment problems.
Provider dashboards#
Google Postmaster Tools and Microsoft SNDS are free and authoritative for their networks. Register every sending domain and IP.
Report analyzers and monitoring#
DMARC aggregate reports are XML and unreadable by hand; an analyzer turns them into a per-source view. Monitoring services alert on reputation drops, blocklistings, and record changes.
Sending platforms#
Your ESP or outreach tool should expose authentication setup, bounce and complaint handling, and per-mailbox limits. For AI-drafted sequences with reply detection, Mailflow in MailMaid Engine handles the sending side.
How to choose#
- Start with the free provider dashboards and a checker.
- Add a DMARC analyzer once you have more than two sending sources.
- Add monitoring when email is revenue-critical.
- Choose sending platforms by their deliverability controls, not template libraries.
Frequently asked questions#
What is DMARC alignment?
The domain in the visible From header must match (exactly or organizationally) the domain that passed SPF or DKIM. Set adkim=s and aspf=s for strict matching.
How long until I can reach p=reject?
Typically 4 to 12 weeks depending on how many third-party senders you have to fix.
What are RUA and RUF reports?
RUA are daily aggregate XML reports of pass/fail counts per source. RUF are per-message forensic samples; many receivers no longer send them.