Learn
DMARC RUA vs RUF: Aggregate and Forensic Reports Explained
DMARC rua names where receivers send aggregate XML reports. ruf requests per-message failure reports, which most receivers refuse to send.
What it is
DMARC rua is the tag in your DMARC record that tells mail receivers where to send aggregate reports. The ruf tag names where they send reports about individual failed messages. A mail receiver is the service that accepts mail for the recipient, such as Gmail or Microsoft 365.
Both tags are optional. Each holds one or more addresses written as mailto: URIs. If rua is missing, receivers must not generate aggregate reports for your domain. If ruf is missing, they must not generate failure reports.
DMARC rua vs ruf
rua |
ruf |
|
|---|---|---|
| Report type | Aggregate | Failure, also called forensic |
| Covers | Message counts per sending IP address, passing and failing | One failed message, or similar failures grouped |
| Format | XML file attached to an email, preferably gzip-compressed | Email in Abuse Reporting Format |
| Timing | At least every 24 hours, per RFC 9989 | Normally almost immediately after the failure |
| Contents | No message content or individual email addresses | Header fields, sometimes the whole message |
What aggregate reports tell you
Each aggregate report lists the IP addresses that sent mail using your domain, the message count for each, and the SPF and DKIM results. That shows you who sends as your domain while you stay at p=none. The format is built for software, so learn how to read DMARC aggregate reports.
Google recommends always including rua. Microsoft 365 sends aggregate reports only when the recipient organization's MX record points directly to Microsoft 365.
DMARC ruf and the forensic report
A DMARC forensic report is the same thing as a failure report, the term RFC 9991 uses. Each one describes a failed message and can include its header fields or its whole content, so it may carry personal data.
Most receivers refuse to send these reports for that reason. Gmail does not support the ruf tag. Microsoft 365 does not send failure reports, even when the address is valid. The fo tag sets which failures you ask about, and receivers may choose whether to follow it.
Example
Publish this TXT record at _dmarc.example.com to request aggregate reports:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
p=none asks receivers not to change how they treat failing mail because of this record. If you already publish a DMARC record, edit it and keep the tags already there, such as p= and sp=. The DMARC Generator builds the line for you.
To ask for failure reports too, add ruf and fo. Use a mailbox with restricted access, because these reports can carry message content.
v=DMARC1; p=none; rua=mailto:dmarc@example.com; ruf=mailto:dmarc-failures@example.com; fo=1
fo=1 requests a report when SPF or DKIM fails to give an aligned pass, meaning a pass for a domain that matches the From address. The default, fo=0, requests one only when both fail.
To send reports to two places, separate the addresses with a comma and write mailto: on each:
v=DMARC1; p=none; rua=mailto:dmarc@example.com,mailto:client@reports.example.net
Reports sent to another domain
The second address above sits outside example.com, so receivers check that reports.example.net agreed to take the reports. That domain's operator publishes this TXT record at example.com._report._dmarc.reports.example.net:
v=DMARC1;
Without it, receivers must ignore that address. The same check applies to ruf. An address at a subdomain of your own registered domain does not need this record.
Common mistakes
- Leaving out
mailto:.rua=dmarc@example.comis not a URI. RFC 9990 says receivers should ignore malformed URIs, so you get no reports. Google also requires the prefix. - Publishing a second DMARC record. Add
ruaandrufto the one record you have. When a name returns several DMARC records, receivers discard all of them, which can leave your domain with no DMARC policy. - Reading an empty
rufmailbox as good news. Silence is normal, because most receivers send nothing. For one specific message, open its headers in the Email Header Analyzer. - Setting
fowithoutruf. Receivers must ignorefowhenrufis absent, sofo=1alone requests nothing. - Using a personal mailbox. Google advises against it and says large organizations can get hundreds or thousands of reports a day. Microsoft recommends a dedicated mailbox or group.
- Leaving
rufopen to everyone. RFC 9991 encourages limiting failure reporting to targeted diagnostic work and restricting who can read the reports. - Relying on removed syntax. RFC 7489, the earlier specification, defined
ri(report interval),rf(failure report format) and size limits such as!10m. RFC 9989 replaced it in May 2026 and removed all three.