Documentation

Learn how to integrate and use DDMARC.

Docs/Using DDMARC/Reading Reports
10 minutesEssential

Reading DMARC Reports

Learn how to interpret DMARC aggregate and forensic reports to understand your email authentication status.

Report Types

Aggregate Reports (RUA)

Daily summaries of authentication results from receiving servers. Contains statistics about pass/fail rates, source IPs, and policy actions taken.

  • Sent daily (usually)
  • XML format, compressed
  • No PII included

Forensic Reports (RUF)

Detailed reports for individual failed messages. Contains full message headers to help diagnose specific authentication failures.

  • Sent per failure
  • Contains message headers
  • Limited provider support

Aggregate Report Structure

Aggregate reports contain metadata about the report and individual records for each source/result combination:

FieldDescriptionExample
org_nameOrganization that sent the reportGoogle Inc.
emailContact email for the reporting orgnoreply@google.com
report_idUnique identifier for this report12345678901234567890
date_rangeTime period covered by the reportbegin: 1704067200, end: 1704153600
domainYour domain being reported onexample.com
policy_publishedYour DMARC policy at time of reportp=reject; sp=reject

Authentication Results

Each record shows the SPF and DKIM authentication results and the action taken:

Result
pass
SPF
Pass
DKIM
Pass
Action
Email delivered normally
Result
fail
SPF
Fail
DKIM
Fail
Action
Email rejected or quarantined (per policy)
Result
softfail
SPF
SoftFail
DKIM
N/A
Action
Email marked suspicious but delivered
Result
neutral
SPF
Neutral
DKIM
N/A
Action
No assertion made

Understanding Alignment

DMARC requires alignment between the From header domain and the authenticated domain. There are two alignment modes:

Relaxed Alignment (r)

The organizational domains must match. Subdomains are allowed.

mail.example.com aligns with example.com
news.example.com aligns with example.com

Strict Alignment (s)

The domains must match exactly. No subdomain variations allowed.

example.com aligns with example.com
mail.example.com does not align with example.com

Tip: Start with relaxed alignment (default) while deploying DMARC. Switch to strict alignment once you have verified all legitimate sending sources.

Common Report Scenarios

High volume from unknown IPs

Unknown servers sending as your domain — likely spoofing attempts or misconfigured third-party services

Action: If the IPs belong to legitimate services, add them to SPF. Otherwise, this is likely spoofing.

SPF pass but DKIM fail

Email sent from authorized IP but missing or invalid DKIM signature

Action: Enable DKIM signing on the sending service. Check if email is being modified in transit.

DKIM pass but SPF fail

Valid DKIM signature but sent from unauthorized IP

Action: This is often OK with relaxed alignment. Consider adding the IP to SPF if it's a legitimate source.

Forwarded mail failures

Legitimate emails failing after being forwarded by recipients

Action: This is expected behavior. ARC (Authenticated Received Chain) can help preserve authentication through forwards.

Where reports land in DDMARC

DDMARC parses every report as it arrives and spreads the results across several pages. These are the ones you will use most when working through report data:

The DDMARC Reports page listing aggregate reports by reporter, date range, policy, email count, pass percentage, and failures.
Every aggregate report DDMARC has received, with total reports, total emails, and pass rate above the table.

Going from “something failed” to “here is the fix”

Aggregate reports tell you that mail failed, not why. The Failures page does that step for you:

  • Failures grouped by root cause, each with a concrete fix and links to the senders involved
  • Spoof campaign clusters — related failures grouped by IP range, From: domain, and week
  • Top failing sources and the most-spoofed header-From domains
  • A failure trend with anomalies highlighted, over 7 to 90 days
  • Time-to-resolution stats for DNS misconfigurations, derived from monitoring checks
  • Recent forensic (RUF) samples where the receiver sent them

Full walkthrough: Failure Analysis.

Report Analysis Best Practices

  • Review reports weekly during initial DMARC deployment
  • Investigate any unknown IPs before tightening policy
  • Document all legitimate sending sources in a sender inventory
  • Set up alerts for sudden changes in pass/fail rates
  • Compare reports across multiple providers for a complete picture

Next Steps