Skip to content

Home Topics Email Authentication DMARC report analysis

Email Authentication · DMARC report analysis

How DMARC aggregate reports affects inbox placement

Short answer

DMARC aggregate reports affects inbox placement because reports are the only way to see who is sending as your domain, including vendors you forgot and attackers you never knew about. Moving to p=reject safely depends on reading them.

What DMARC aggregate reports are#

DMARC aggregate (RUA) reports are daily XML files sent by mailbox providers listing, per sending IP, how many messages claimed your domain and whether they passed SPF, DKIM, and alignment. Forensic (RUF) reports contain samples of individual failures.

Why it matters#

Reports are the only way to see who is sending as your domain, including vendors you forgot and attackers you never knew about. Moving to p=reject safely depends on reading them.

How mailbox providers use it#

Gmail, Microsoft, and Yahoo combine authentication results, sender reputation, and recipient engagement into a placement decision made per message. DMARC aggregate reports feeds directly into that model, and weaknesses compound with other signals.

How to measure the impact#

  1. Baseline inbox placement with seed tests before any change.
  2. Make one change at a time and hold volume steady.
  3. Re-test after 48 to 72 hours; provider models need time to update.
  4. Track Postmaster Tools and SNDS alongside your seed results.

Improving it#

  1. Publish rua=mailto: pointing to a dedicated mailbox or a report processor.
  2. Collect reports for at least two weeks before drawing conclusions.
  3. Group sources by IP owner and match each to a known vendor.
  4. Fix alignment for legitimate sources; treat unknown high-volume sources as spoofing.
  5. Track pass rate weekly and tighten policy as it approaches 100%.
Fragment of an aggregate report record
<record>
  <row><source_ip>203.0.113.10</source_ip><count>412</count>
    <policy_evaluated><disposition>none</disposition><dkim>pass</dkim><spf>fail</spf></policy_evaluated></row>
  <identifiers><header_from>example.com</header_from></identifiers>
</record>

Frequently asked questions#

How do I read a DMARC report?

Each record lists a source IP, message count, SPF and DKIM results, and alignment. Use an analyzer to aggregate by source; the goal is to name every IP range.

Why do I see mail from IPs I do not recognize?

Common causes are forwarding, a vendor you forgot, an employee's personal tool, or spoofing. Volume and geography usually tell them apart.

Analyse your own setup

All analysers
Technical analysis

DMARC record analyser

Grade a DMARC record on enforcement, not just syntax.

Runs in your browser

Keep reading on DMARC report analysis