Aggregate (RUA) vs forensic (RUF) reports
A DMARC report is feedback that mail receivers send you about mail that used your domain. There are two kinds, requested by two different tags, and they're nothing alike. Aggregate reports (rua) are daily, machine-readable summaries: for each sending IP, how many messages used your domain and whether they passed SPF, DKIM, and DMARC alignment. They contain no message content. Failure reports (ruf, usually called forensic reports) describe individual failed messages, can include headers or the whole message, and are sent by few receivers. Gmail and Microsoft 365 don't send them at all. In practice, your DMARC work runs on aggregate reports.
If you're comparing rua vs ruf because you're editing your record, the tag syntax and external-address authorization are in rua, ruf, and report authorization.
Two report types, three current standards
The DMARC standard was split in three in May 2026: DMARC itself, aggregate reports, and failure reports. Together they replace the older 2015 standard.
"Failure report" is the current term. "Forensic report" is the older name you'll still see everywhere. Google and Microsoft use both names. They're the same thing. We'll say failure reports from here on.
Neither report type is automatic. If your DMARC record has no rua, receivers must not send you aggregate reports. If it has no ruf, they must not send failure reports. And publishing p=none doesn't change how your mail is handled; it only gets you reports if rua is there.
What a DMARC aggregate report is
An aggregate report is one receiver's summary of the mail it got using your domain over one reporting period. That period is usually one UTC day, starting at 00:00 UTC. Receivers should send aggregate reports at least once every 24 hours. In practice, Google and Microsoft typically send them once a day.
Each report arrives as an email with an XML attachment, usually gzip-compressed. The subject line follows a fixed pattern, which is why these emails look odd the first time you see them:
Subject: Report Domain: example.com
Submitter: mail.receiver.example
Report-ID: <sample-ridtxt@example.com>
Inside, you get the policy as that receiver saw it, then one record per sending IP with a message count, what the receiver did, whether DKIM and SPF produced an aligned pass, and the raw SPF and DKIM results, including the DKIM signing domain and selector. The field-by-field walk-through is in A field-by-field walk-through of a DMARC aggregate report.
What aggregate reports don't contain matters just as much. No personal information such as individual mail addresses, IP addresses of individuals, or the content of any messages is included in reports. The IPs are those of sending mail servers. That doesn't mean there's nothing sensitive in them, though. They still show your traffic patterns, and sending them to a third party can be subject to receivers' policies.
Two more limits to keep in mind:
- Not every receiver sends them. Sending is recommended, not required. Resource limits, local policy, and user privacy are the common reasons receivers opt out. Microsoft 365, for example, only sends aggregate reports as long as the MX record for the Microsoft 365 domain points directly to Microsoft 365. More on gaps in Why DMARC reports do not arrive.
- They don't show inbox or spam placement. Adding that information is discouraged. See Authentication vs inbox placement.
You get one report per policy domain per receiver per period. A subdomain without its own DMARC record shows up as records inside the parent domain's report. A subdomain with its own record gets its own report, sent to its own rua.
Failure (forensic) reports
A failure report is about one failed message, or a group of similar failures. They're normally generated and sent almost immediately after the receiver detects a DMARC failure. The format is based on the ARF auth-failure format, with an Identity-Alignment field that names the mechanisms that failed to produce an aligned identity.
The trade-off is privacy. They can contain the header fields or sometimes the entire content of a failed message, which may contain personally identifiable information. They can also expose mailing-list membership and forwarding destinations, and they can carry the spam, phishing, or malware that failed in the first place.
That's why few receivers send them. Many large-scale providers limit or entirely disable the generation of failure reports. Two big ones say so directly:
- Google: "(Not supported) Gmail doesn't support the ruf tag."
- Microsoft: "Microsoft 365 doesn't send DMARC Forensic reports (also known as DMARC Failure reports), even if a valid ruf=mailto: address exists."
The fo tag controls when failure reports are generated and is ignored without ruf. It's covered in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.
Side by side
Aggregate (rua) |
Failure / forensic (ruf) |
|
|---|---|---|
| Defined in | Current aggregate reports | Current failure reports |
| Covers | All mail from each source IP over a period | One failed message, or a group of similar failures |
| Timing | Daily or more often (SHOULD, at least every 24 hours) | Almost immediately after a failure |
| Content | Counts, published policy, SPF and DKIM results, alignment, disposition. No message content | Headers, sometimes the full message. May include PII |
| Who sends them | Many receivers, not all | Few. Gmail and Microsoft 365 don't |
| What it's for | Finding your sources, tracking pass rates, deciding on enforcement | Targeted diagnosis and abuse investigation, after a privacy review |
Microsoft describes failure reports as one report per failure, which can be high volume. Generators are required to rate-limit, so read that as a simplification.
Which one should you use?
Start with rua only. That's also Microsoft 365's advice: start with rua only, then add ruf later if needed. Aggregate reports remain the recommended mechanism for gaining visibility.
Aggregate reports are what you use to find every service sending as your domain (How to inventory sending sources) and to decide when you're ready to move past p=none. Since raw XML gets unmanageable fast, most teams read them through a parser or a visual view (What visual DMARC analysis should show you). The provider rules behind all this are in Google, Yahoo, and Microsoft sender requirements.
Add ruf only when you have a specific diagnostic need, and only after a privacy review. If you do, limit the scope and duration, control where the reports go, redact, and use secure channels. Send them to a mailbox with restricted access, and treat what arrives as potentially malicious.
Mistakes worth avoiding
- Pointing
ruaat a personal inbox. Google warns you can get "hundreds or even thousands of reports daily" at scale. Google and Microsoft both recommend a dedicated mailbox or group. - Deleting the DMARC record to stop the report emails. Remove or redirect
ruainstead. Deleting the record removes your policy too. - Adding
rufand expecting data from Gmail or Microsoft 365. You won't get any. - Sending
rufto a mailbox lots of people can read. Failure reports can hold personal data and malicious content. - Reading "no failure reports" as "nothing is failing." Many receivers don't send them, so silence tells you nothing.
- Pointing
ruaorrufat another domain without its authorization record. Receivers ignore unauthorized external addresses (Why DMARC reports do not arrive). - Mixing up DMARC reports and TLS-RPT reports. TLS-RPT uses a different record and reports on TLS for mail in transit (MTA-STS, TLS-RPT, and SMTP TLS).
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Why am I getting DMARC reports?
Because your DMARC record has a rua tag asking receivers to send them. They're summaries of mail that used your domain, sent by receivers that support reporting, such as Google and Microsoft.
How do I stop the report emails?
Remove the rua tag or point it somewhere else, such as a dedicated mailbox or a reporting service. Keep the record itself. Without the reports, though, you lose the data that shows who sends as your domain.
Do I need both rua and ruf?
No. Start with rua. Add ruf only for a specific diagnostic need, after a privacy review.
Why don't I get any forensic reports?
Many large receivers don't send them, including Gmail and Microsoft 365. An empty ruf mailbox is normal.
Do aggregate reports contain my customers' emails?
No. They hold counts, sending-server IPs, domains, and authentication results, not message content or individual addresses.
Are DMARC reports the same as TLS-RPT reports?
No. They're separate report types with separate records. See MTA-STS, TLS-RPT, and SMTP TLS.