What Is DMARC?

Understand DMARC, how it builds on SPF and DKIM with alignment checks, policy options (none, quarantine, reject), and aggregate vs forensic reporting per RFC 7489.

What Is DMARC?

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol that builds on SPF and DKIM by adding a policy layer and a reporting mechanism. Defined in RFC 7489, DMARC lets domain owners instruct receiving mail servers on how to handle messages that fail authentication checks and provides visibility into who is sending email using their domain.

How DMARC Works

DMARC ties together SPF and DKIM through the concept of alignment. For a message to pass DMARC, at least one of the following must be true:

  1. SPF alignment. The domain in the SMTP envelope sender (MAIL FROM) matches the domain in the visible From header, and SPF passes.
  2. DKIM alignment. The domain in the DKIM signature's d= tag matches the domain in the visible From header, and DKIM passes.

Alignment can be strict (exact domain match) or relaxed (organizational domain match, meaning subdomains are allowed). Relaxed alignment is the default.

The DMARC Record

DMARC policies are published as DNS TXT records at _dmarc.domain.com:

_dmarc.example.com. 3600 IN TXT "v=DMARC1; p=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; pct=100"

Key Tags

  • v=DMARC1 -- Version (required).
  • p= -- Policy for the domain (required). Values: none, quarantine, reject.
  • sp= -- Policy for subdomains. Defaults to the p= value if omitted.
  • rua= -- URI for aggregate reports (recommended).
  • ruf= -- URI for forensic/failure reports (optional).
  • pct= -- Percentage of messages to which the policy applies (default 100).
  • adkim= -- DKIM alignment mode: r (relaxed, default) or s (strict).
  • aspf= -- SPF alignment mode: r (relaxed, default) or s (strict).

Policy Options

Policy Behavior
none Monitor only. No enforcement. Messages are delivered normally but reports are generated.
quarantine Failing messages are sent to the spam/junk folder.
reject Failing messages are rejected outright at the SMTP level.

Most organizations start with p=none to collect data, then move to quarantine, and finally reject once all legitimate senders are authenticated.

Aggregate vs. Forensic Reports

Aggregate reports (rua) are XML files sent daily by receiving mail servers. They summarize authentication results for all messages seen from your domain, including source IPs, SPF/DKIM results, and alignment outcomes. These reports are essential for identifying unauthorized senders and misconfigurations.

Forensic reports (ruf) contain details about individual messages that failed DMARC. They are useful for debugging but are not sent by all receivers (Gmail, notably, does not send forensic reports) and may raise privacy concerns.

Gmail, Outlook, and Yahoo Requirements

As of 2024, Gmail and Yahoo require bulk senders (5,000+ messages/day) to have a published DMARC record with at least p=none. Outlook followed with similar requirements in 2025. Without a DMARC record, your messages face increased scrutiny and potential delivery failures at these providers.

Check Your DMARC Configuration

Use our DMARC analysis tool to validate your record syntax, policy settings, and reporting addresses. For a complete view of your authentication setup, run a full domain analysis that checks SPF, DKIM, and DMARC together.


Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.