What is the difference between DMARC aggregate reports and DMARC failure reports, and which one does a domain owner rely on?
answer
- statistics versus samples
- one periodic, one near-immediate
- XML summary against an ARF message
- privacy decides who sends which
basics
~20 sAggregate reports (RFC 9990, requested with rua) are daily XML summaries of SPF, DKIM and alignment results per sending IP, with no message content; failure reports (RFC 9991, requested with ruf) are per-message ARF samples, and most receivers send none.
solid answer
~50 sAn **aggregate report** is an XML document, normally gzip-compressed, that a receiver mails to each `rua` address for a reporting period; RFC 9989 says receivers SHOULD send them at least once every 24 hours. It counts messages per source IP and gives the disposition, the DKIM and SPF alignment verdicts and the raw results, for passing and failing mail alike. A **failure report** goes to a `ruf` address soon after a DMARC failure, in the Abuse Reporting Format (RFC 5965 with RFC 6591, updated by RFC 9991), and carries the failed message's header block or the whole message. Because that can include personal data, RFC 9989 notes that most receivers refuse to send them, and those that do often redact. So a domain owner builds monitoring on aggregate reports and treats failure reports as an occasional diagnostic extra. Both formats left RFC 7489 for their own documents in May 2026.
go deeper
Recall the two report types, the tag that requests each, and the one-line difference: aggregate reports count, failure reports sample. Knowing which one can carry message content is the core of the answer.
Explain format and timing: gzip-compressed XML per reporting period against an ARF message per failure, and why aggregate reports cover passing mail as well as failures.
Show that you know failure reports are scarce in practice and that monitoring is built on aggregate data; mention that RFC 9989 removed the ri and rf tags in May 2026.
Frame the trade-off: aggregate data is enough for a sender inventory at little privacy cost, while failure reports buy per-message detail at a legal and handling cost the organisation has to own.
## Two kinds of DMARC feedback DMARC lets the owner of a domain publish a policy for mail whose visible `From` domain (the RFC 5322 From, called the **Author Domain**) does not pass. The same DMARC record can ask receivers for feedback, and the specification defines two kinds. Since May 2026 they live in separate documents: **RFC 9990** for aggregate reports and **RFC 9991** for failure reports, which together with RFC 9989 obsolete the single 2015 text, RFC 7489. A record asks for aggregate reports with the `rua` tag and for failure reports with the `ruf` tag; if a tag is absent, receivers MUST NOT generate that kind of report. ## Aggregate reports: the statistics An aggregate report answers one question for one reporting period: *which systems sent mail using my domain, and how did that mail authenticate?* - **Format:** an XML document defined by the XML Schema in RFC 9990, with the root element `feedback`. - **Packaging:** attached to an email message; the XML SHOULD be gzip-compressed (`application/gzip`, file extension `.xml.gz`), otherwise it is sent as `text/xml`. - **Cadence:** RFC 9989 says receivers SHOULD send aggregate reports at least once every 24 hours; the period typically covers one UTC day. - **Content:** report metadata, the policy the receiver found, and one or more `record` elements, each with a `source_ip`, a message `count`, the applied disposition, the DKIM and SPF alignment verdicts and the raw DKIM and SPF results. - **Scope:** messages that passed as well as messages that failed, so the owner sees every stream, not only the problems. RFC 9990 states that this data contains no individual mail addresses, no IP addresses of individuals and no message content. ## Failure reports: the samples A failure report answers a different question: *what did this particular failing message look like?* It is generated soon after a receiver sees a DMARC failure rather than on a schedule, and it uses the **Abuse Reporting Format** (ARF, RFC 5965) with the authentication-failure extensions of RFC 6591, as updated by RFC 9991. An ARF report is a `multipart/report` message with three parts: 1. a human-readable description; 2. a machine-readable `message/feedback-report` part with fields such as `Feedback-Type: auth-failure`, `Auth-Failure: dmarc`, `Identity-Alignment`, `Source-IP` and `Reported-Domain`; 3. the original message in full (`message/rfc822`) or a copy of its entire header block (`text/rfc822-headers`). That third part is both the value and the problem: it can hold recipients, subjects, bodies and attachments. RFC 9989 records that most receivers refuse to send failure reports because of privacy concerns, and RFC 9991 notes that many large-scale providers limit or disable them; those that do send often redact. The record's `fo` tag tells receivers which failures the owner would like reported, but report generators "may choose to adhere" to it - it is a request, not a switch. ## Side by side | | Aggregate report | Failure report | |---|---|---| | Defined in | RFC 9990 | RFC 9991, format from RFC 5965 and RFC 6591 | | Requested with | `rua` | `ruf`, shaped by `fo` | | Timing | periodic, at least daily (SHOULD) | soon after a failure, under a rate limit | | Unit | counts per source IP and result | one message, or a group of similar ones | | Content | domains, results, counts | header block or the whole message | | Availability | sent by receivers that implement reporting | sent by few receivers, often redacted | ## Why aggregate reports carry the programme A domain owner preparing for enforcement needs to know every system that sends with its name. The aggregate report is built for that: each source IP appears with its volume and with whether it passed aligned, so a forgotten application server or an outside sending service shows up as a row. Among the things RFC 9989 says a domain owner MUST do to fully participate in DMARC is set up a mailbox to receive aggregate reports and analyse them. Failure reports can explain one failure quickly, but because few receivers send them, a plan that depends on them sees only a small, unrepresentative slice of the traffic. ## What changed in May 2026 - The reporting text moved out of RFC 7489 (Informational) into RFC 9990 and RFC 9991, both on the Standards Track. - The `ri` tag (a requested aggregate interval, default 86400 seconds in RFC 7489) and the `rf` tag (a requested failure-report format) were removed by RFC 9989; a receiver that follows it ignores them as unknown tags. - Aggregate reports gained elements such as `np`, `testing` and `discovery_method`, and a reported DKIM result must now name its selector.
- Does a receiver send DMARC aggregate reports for a domain whose DMARC record has no rua tag?No. RFC 9989 says that if the `rua` tag is not provided, Mail Receivers MUST NOT generate aggregate feedback reports for the domain, and the same rule applies to `ruf` and failure reports. A record without `rua` still carries a policy, but the owner gets no feedback at all, which defeats the purpose of starting in monitoring mode.
- Can a domain owner still ask for a different reporting interval or failure-report format in its DMARC record?Not under RFC 9989 (May 2026). The `ri` tag, a requested interval that defaulted to 86400 seconds in RFC 7489, and the `rf` tag, a requested failure-report format, were removed. A receiver following RFC 9989 ignores them as unknown tags; aggregate reports SHOULD come at least every 24 hours, and failure reports use ARF as updated by RFC 9991.
An aggregate report is a bank statement: it lists each payee with totals, enough to spot a charge you do not recognise, but no receipts. A failure report is a photocopy of one disputed receipt - far more detail, including whatever personal information is written on it, so it is handed out sparingly.
- Aggregate reports include copies of the messages that failed DMARC.
- Failure reports arrive once a day as a summary of every failure.
- Any receiver that sends aggregate reports will also send failure reports when asked.
- Publishing ruf guarantees a sample of every forged message.
- The ri tag still sets how often receivers send aggregate reports.