Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
DMARC
- Domain
- email authentication 1 source
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email-authentication standard 1 that enables domain owners to publish policies specifying how mail servers should handle messages claiming to originate from their domain.
DMARC works by allowing organizations to declare authentication requirements and desired handling of unauthenticated mail through DNS-published policies. It builds on existing SPF and DKIM authentication mechanisms, requiring that messages pass at least one of these checks and that the authenticated domain aligns with the domain visible to end users in the "From" header.
The standard defines three policy modes: monitor (p=none), which instructs receivers to report results without taking action; quarantine (p=quarantine), which suggests suspicious messages be isolated; and reject (p=reject), which instructs receivers to refuse delivery of unauthenticated mail. Organizations typically deploy in monitor mode initially, then transition to stricter policies as authentication coverage improves.
DMARC also mandates aggregate and forensic reporting mechanisms. Aggregate reports provide statistical summaries of authentication results, while forensic reports deliver samples of failed messages. These reports help domain owners identify authentication gaps, detect spoofing attempts, and monitor third-party mail senders.
The standard addresses a critical gap in email security: while SPF and DKIM authenticate mail server behavior, they do not prevent attackers from spoofing the visible sender address. DMARC closes this by requiring alignment between authenticated identities and user-visible addresses, making domain spoofing significantly more difficult.
DMARC adoption has grown substantially among high-profile organizations and is increasingly recommended as part of email security best practices. However, deployment complexity—particularly managing third-party senders and forensic report processing—remains a barrier to widespread strict-policy enforcement.
Facts 2
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| Body | IETF disputed | low | 1 | source ↗ |
| Domain | email authentication | low | 1 | source ↗ |
Neighbourhood
Mitigates 2
Frequently mentioned together 15
Sources 38
- Open Source vs Commercial Email Security: Operational Choices and Risks · LinuxSecurity: Articles
- podcast SANS Stormcast Tuesday, November 10th, 2026: SAP NetWeaver Webshells (CVE-2025-31324); N-able N-central Offline; Chrome XML 0-Day (CVE-2026-125350); Outlook DMARC Required · SANS ISC: Daily Podcast
- The race to secure record-like information for domains · Lobsters
- Microsoft are rejecting your mail · Lobsters
- Outlook.com bounces legit emails as Microsoft's authentication crackdown goes sideways · The Register: Security
5 of 38 sources shown · Pro unlocks the full list