Domain-based Message Authentication, Reporting and Conformance
Also called DMARC.
A policy tying SPF and DKIM to the visible From and reporting failures.
What it is
A standard that builds on SPF and DKIM by requiring alignment with the visible 'From' domain, telling receivers what to do with failures (none, quarantine, or reject), and sending the domain owner aggregate and forensic reports.
Why it matters
DMARC is what actually closes the domain-spoofing gap and gives owners visibility into who sends as them, so its policy and reports are core both to defense and to scoping abuse of a brand.
In practice
A domain set to 'p=reject' causing receivers to drop unauthenticated mail claiming to be from it.
What to look for
- dmarc=fail with the policy applied.
- Aggregate reports showing who sends as your domain.
- Policies stuck at none.
Common mistake
Jumping straight to reject. Read the reports first so you do not block your own services.
Use it in CyberKit
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Defender for Office 365 Commercial
Filters phishing and malicious attachments in Microsoft 365 and lets you investigate messages.
-
Proofpoint Email Protection Commercial
A mail gateway that scores, rewrites and quarantines suspicious mail.
-
VirusTotal Commercial
A quick second opinion on a suspicious attachment or link.
Read next
- Sender Policy Framework: DNS record listing which servers may send mail for a domain.
- DomainKeys Identified Mail: A cryptographic signature proving an email wasn't altered in transit.
- Email Header Analysis: Reading an email's full headers to trace origin and authentication.