Skip to main content
Resources/Guides
Guide

DMARC reports: the two types, how to receive them and what to act on

There are two kinds of DMARC report. An aggregate (rua=) report is a compressed XML file that one receiving mail service sends about the mail it saw using your domain, typically covering one UTC day. Each row gives a sending IP address, a message count, the SPF and DKIM results and what the receiver did with the mail. Google, for example, sends one for each day it sees your mail, from noreply-dmarc-support@google.com. Forensic (ruf=) reports are per-message failure reports, and Google, Microsoft and Yahoo rarely or never send them.

By ShieldMarc · Updated October 2026

Facts checked against live DNS, the relevant RFC or the provider’s own documentation.

This guide covers what each report type is for, how to start receiving them, and what to do with what they show: which senders to fix, which to leave alone and which to investigate. For a field-by-field read of the XML itself, see How to read a DMARC RUA XML report on our blog.

Two types of DMARC report

The DMARC specification defines two reporting mechanisms. They serve different purposes and are configured with separate tags in your DMARC record.

Report typeDMARC tagFormatPurpose
Aggregate (RUA)rua=XML (gzip or zip compressed)Summary of the mail one receiver saw using your domain over its reporting period (usually a day), grouped by source IP and authentication results
Forensic (RUF)ruf=AFRF (email format)Per-message failure report with headers from individual emails that failed DMARC

Aggregate reports (RUA)

Aggregate reports are the backbone of DMARC monitoring. Mailbox providers that support DMARC reporting, including Gmail, Microsoft and Yahoo, send them to the address in your rua= tag. Each report summarises the mail that one receiver saw using your domain during its reporting period.

Reports come from receivers that send them, on days they see your mail. A quiet day is not proof that nothing was sent. Mail refused early in the SMTP conversation never appears in aggregate reports (RFC 9989, section 7.1).

The receiver sets that period, not you. The standard (RFC 9990, section 3.1.1.4) says it typically covers a single UTC day starting at 00:00 UTC, and a receiver may report more often. Each report states its own start and end times, so read those rather than assume a day.

What is inside an aggregate report

An aggregate report is an XML file, usually sent as a gzip or zip attachment, in three parts: who sent it and the period it covers, the DMARC record the receiver found in your DNS, and rows that group the mail by sending IP address, each with a message count, what the receiver did with the mail and the SPF and DKIM results.

How to read a DMARC RUA XML report walks through each part, from decompressing the file to telling the aligned results from the raw ones. To see a single report as a table, drop it into the free DMARC Report Viewer, which reads it in your browser.

Forensic reports (RUF)

Forensic reports provide per-message detail when an email fails DMARC. Unlike aggregate reports which group data by source IP, forensic reports include the actual email headers (and sometimes a redacted body) of each failing message.

What forensic reports contain

  • The full email headers of the failing message
  • The specific authentication failure (SPF, DKIM, or both)
  • The sending IP address
  • The subject line (sometimes redacted for privacy)
  • Timestamps and receiving server details

Limitations of forensic reports

Most major providers rarely or never send forensic reports. Google, Microsoft, and Yahoo rarely (or never) send RUF reports due to privacy concerns. Forensic reports are most useful when your recipients are on enterprise mail systems that do support them. Do not rely on RUF as your primary data source.

Controlling forensic report detail with fo=

The fo= tag in your DMARC record controls when forensic reports are generated:

ValueMeaning
fo=0Generate a report only if both SPF and DKIM fail alignment (default)
fo=1Generate a report if either SPF or DKIM fails alignment (recommended)
fo=dGenerate a report if DKIM signature verification fails
fo=sGenerate a report if SPF evaluation fails

How to set up DMARC reporting

Step 1: Add rua to your DMARC record

Your DMARC record is a DNS TXT record at _dmarc.example.com. Add the aggregate reporting tag:

v=DMARC1; p=none; rua=mailto:dmarc-rua@example.com

The mailto: prefix is required. You can specify multiple addresses separated by commas. Forensic reporting (ruf=) can be added alongside rua= and points at a mailbox that accepts per-message failure reports. Send ruf= to an endpoint that is equipped to parse and store the data safely, not a general-purpose inbox.

Step 2: Sending reports to a different domain

If your RUA address is on a different domain (e.g. you want reports sent to a monitoring service), the receiving domain must publish an authorisation record:

example.com._report._dmarc.example.net TXT "v=DMARC1"

Without this record, receiving mail servers will not send reports to the external address. This is a common gotcha when setting up third-party DMARC monitoring.

Step 3: Wait for reports to arrive

Each receiver sends aggregate reports on its own schedule, usually one report a day. After updating your DMARC record, allow 24 to 48 hours for the first reports to arrive. The volume depends on how much email your domain sends.

Step 4: Parse and analyse

Raw DMARC aggregate reports are XML files that can be hundreds of kilobytes each. Reading them by hand is impractical at any scale. You have two options:

  • Manual: Download the XML attachments, decompress them, and read the records. Feasible for a single domain with low volume, but does not scale.
  • Automated: Use a DMARC reporting platform to ingest, parse and visualise the reports. This gives you dashboards showing sending sources, pass/fail rates, and alignment trends over time.

What should I do with what the reports show?

Sort every source in your reports into one of four groups, then work through the groups in turn. Group by service rather than by IP address: one platform can send from many addresses, and reports name only the last server that handed the mail over, so a relay or signature service can hide the sender behind it.

  • Your own services, passing and aligned. No action. Note them, so that a change stands out in later reports.
  • Your own services, failing. Fix these first, largest volume first. Set each one up to sign with DKIM for your domain, or to send from a bounce (MAIL FROM) domain under yours with its own SPF record that authorises the service. Forgotten SaaS tools that were allowed to send but never added to SPF or DKIM turn up here. Microsoft sources repay a second look, because mail can pass SPF against the tenant onmicrosoft.com domain and still fail alignment; DMARC for Office 365 and Microsoft 365 explains why and how to fix it.
  • Forwarders and mailing lists. A forwarding service relays your mail from its own servers, so SPF fails, though a DKIM signature generally survives the relay (RFC 9989, section 7.4). Lists that add a subject tag or a footer usually break DKIM as well. These failures are not attacks, so do not chase them as spoofing.
  • Sources you cannot attribute. Use reverse DNS and IP range lookups to find the owner before you act. High-volume sources with no link to you that fail both SPF and DKIM are the likely spoofers, and they are the mail enforcement is for. At p=reject you ask receivers to refuse mail that fails DMARC, and each receiver makes the final call (RFC 9989, section 5.4).

Judge a source across several days and receivers, not from one report. Reports come from receivers that send them, on days they see your mail. A quiet day is not proof that nothing was sent.

Once every service you use passes in alignment, the reports are your evidence for enforcement: move to p=quarantine, keep reading, then move to p=reject on the same evidence. DMARC p=none to p=reject: a stage-by-stage rollout runbook sets out what to check at each stage, how long to stay and how to roll back.

Common problems with DMARC reports

Not receiving any reports

  • Check that your DMARC record has a valid rua=mailto: tag. Use our DMARC Checker to verify.
  • If your RUA address is on a different domain, ensure the external authorisation DNS record is in place.
  • Check your spam folder. Some email providers classify DMARC report emails as bulk mail.
  • Allow at least 48 hours after publishing your DMARC record.

Unrecognised source IPs

Not every unfamiliar IP in your reports is an attacker: forwarders, mailing lists and forgotten SaaS tools show up too. What to do with what the reports show sorts them into four groups.

Report volume overwhelming your mailbox

Domains with high email volume can receive hundreds of aggregate reports per day. Sending these to a regular mailbox quickly becomes unmanageable. A dedicated DMARC reporting tool parses the XML automatically and presents the data in a visual dashboard, making it practical to monitor multiple domains at scale.

DMARC reporting tags quick reference

TagPurposeExample
rua=Where to send aggregate reportsmailto:dmarc@example.com
ruf=Where to send forensic reportsmailto:forensic@example.com
fo=When to generate forensic reports1

RFC 7489 also had an ri= tag for requesting a reporting interval. The current standard removed it (RFC 9989, Appendix C.5.2), so each receiver chooses its own period. Leave it out of new records.

Check your DMARC record now

Not sure if your domain has DMARC reporting configured? Use our free DMARC Checker to see your current DMARC record, including whether RUA and RUF tags are present and correctly formatted. If you need to create or update your record, use our DMARC Generator to build a valid record with the right reporting tags.

For a broader view of one domain, including SPF, SSL, DNSSEC and domain registration, try our Security Grade.

Need automated report parsing?

Reading raw XML reports is fine for a single domain, but it does not scale. ShieldMarc automatically ingests your DMARC aggregate reports, parses them, and gives you a visual dashboard showing sending sources, pass/fail rates, and alignment trends over time.

Sign up for ShieldMarc to start parsing your DMARC reports automatically. Free tier available.

Frequently asked questions

How do I find out who is spoofing my domain?

Your aggregate DMARC reports list the source IPs that receivers saw sending mail as your domain, so spoofers can show up there. Reports come from receivers that send them, on days they see your mail. A quiet day is not proof that nothing was sent. Reconcile your known senders first: match each source IP to a service you authorised (your mail platform, CRM, marketing tool and so on). The likely spoofers are the high-volume sources you do not recognise that fail both SPF and DKIM alignment, because legitimate senders almost always pass at least one. Treat unfamiliar IPs with care, since forwarders and mailing lists can also fail alignment without being malicious, so confirm before acting. At p=reject you ask receivers to refuse mail that fails DMARC, and each receiver makes the final call (RFC 9989, section 5.4). Aggregate reports cover abuse of your own domain. For attackers using similar-looking domains instead, see what to do about lookalike domains.

What is a DMARC report?

A DMARC report is one of two types. An aggregate (rua=) report is a compressed XML file that one receiving mail service sends about the mail it saw using your domain, typically covering one UTC day. Each row gives a sending IP address, a message count, the SPF and DKIM results and what the receiver did with the mail. Forensic (ruf=) reports are per-message failure reports, and Google, Microsoft and Yahoo rarely or never send them.

What is the difference between DMARC RUA and RUF?

RUA reports are aggregate XML summaries, usually one a day from each receiver, grouping email by source IP and authentication result. RUF reports are per-message forensic reports generated when an individual email fails DMARC, containing the actual headers. Most major providers (Google, Microsoft, Yahoo) rarely or never send RUF reports due to privacy concerns, so RUA is your primary data source.

Why am I not receiving any DMARC reports?

Check that your DMARC record has a valid rua=mailto: tag and that the mailbox exists. If the rua= address is on a different domain from your main domain, you need to publish an external authorisation DNS record at example.com._report._dmarc.example.net with the value v=DMARC1. Also check your spam folder and allow at least 48 hours after publishing.

What does fo=1 mean in a DMARC record?

The fo= tag controls when forensic reports are generated. fo=0 (the default) only generates a report if both SPF and DKIM fail alignment. fo=1 generates a report if either SPF or DKIM fails alignment and is the recommended setting when you want detailed failure visibility. fo=d triggers on DKIM signature failure and fo=s on SPF evaluation failure.

How long does it take to go from p=none to p=reject using DMARC reports?

There is no fixed timeline: the gate is report cleanliness, not the calendar. A simple setup with one or two senders needs at least four weeks, because ShieldMarc's readiness check wants 14 days of reports at each step; the stages, gates and roll-back are in DMARC p=none to p=reject: a stage-by-stage rollout runbook.

What does RUA stand for in DMARC?

RUA stands for Reporting URI of Aggregate reports. It is the DMARC tag (rua=) that names the address (or addresses) where receiving providers send their aggregate XML reports, usually one a day: a summary of the mail they saw using your domain. Point rua= at a mailbox you control, or at a platform that parses the reports for you. ShieldMarc gives you a dedicated rua address and turns the raw XML into readable dashboards, free for your first domain.

What does RUF stand for in DMARC?

RUF stands for Reporting URI of Forensic reports, also called failure reports. It is the DMARC tag (ruf=) that names the address where receivers send per-message failure detail when a message fails authentication. In practice, Google, Microsoft and Yahoo rarely or never send RUF reports for privacy reasons, so aggregate (rua) reports remain your primary data source. Point ruf= only at an endpoint equipped to parse and store the message content safely.

We use optional analytics cookies (Google Analytics) to understand how visitors use the site. Essential cookies are always on. Privacy policy