Skip to content
  • There are no suggestions because the search field is empty.

rua, ruf, and report authorization

rua and ruf are tags in your DMARC record that tell receivers where to send reports. rua asks for aggregate reports: daily summaries of who sent mail as your domain and how it did on SPF, DKIM, and alignment. That's the data you actually run DMARC on. ruf asks for failure reports about individual messages, and most large receivers send few or none. If a report address is on a different domain from the one publishing the policy, that other domain has to publish a small authorization record, or receivers ignore the address.

dmarc rua vs ruf: what each tag asks for

rua ruf
Requests Aggregate reports Failure (forensic) reports
What you get XML summaries per receiver, usually daily Reports about individual failing messages
If the tag is missing Receivers must not send aggregate reports Receivers must not send failure reports
How often they arrive Most large receivers send them Many receivers don't send them at all
Privacy Counts, IPs, domains, results Can include message headers or the whole message

Both take a comma-separated list of URIs, and receivers that send reports must support mailto::

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

What's inside each report type is covered in Aggregate (RUA) vs forensic (RUF) reports. The other tags in the record are in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.

What the rua tag does

rua is the list of addresses to which aggregate feedback reports are to be sent. Leave it out, and receivers must not send you aggregate reports. A p=none record with no rua collects nothing.

Each report is XML, normally gzip-compressed. It covers the policy the receiver found, sending IP addresses, message counts, SPF and DKIM results and domains, whether each was aligned, and what the receiver did with the mail. Receivers should send them at least once every 24 hours. In practice, Google and Microsoft typically send them once a day.

Not every receiver sends them. Sending is recommended, not required, and receivers can opt out. A claim you'll sometimes see, that every mail server you send email to will send you a daily report, overstates it, so don't plan around it.

Where to point rua:

  • Not a personal inbox. To use a specific mailbox or Microsoft 365 Group and not to deliver reports to a user's mailbox. Google suggests a dedicated group or mailbox.
  • A reporting service is the practical option for most domains. Many third-party services exist that will process DMARC aggregate reports. The reports are meant for software to parse, not for people to read in a mail client. What a visual report view should show you is in What visual DMARC analysis should show you.
  • Keep the list short. Receivers send to each listed address only up to their own limits on how many they support.

Reading an aggregate report field by field is in A field-by-field walk-through of a DMARC aggregate report.

What ruf does, and why it's often empty

ruf is the list of addresses to which message-specific failure information is to be reported. The current term is failure reports. Many tools and providers still say "forensic reports." Same thing.

Don't expect much from it:

  • Receivers may choose to send them, and receivers concerned about privacy have either chosen to heavily redact the information in such reports or not send them at all.
  • It also says "most Mail Receivers refuse to send them out of privacy concerns."
  • Many large-scale providers limit or entirely disable them.
  • Gmail doesn't support ruf.
  • Microsoft 365 "doesn't send DMARC Forensic reports... even if a valid ruf=mailto: address exists."

So an empty ruf mailbox doesn't mean nothing is failing. Look at your aggregate reports for that.

The reports a receiver does send can contain header fields or the entire message, which can include personal data. Anyone requesting them should have controls for handling that data. If you need ruf for a specific diagnosis, limit its scope and duration, control and validate the addresses, redact, and use secure transport. Get a privacy review first.

The fo tag controls when failure reports are generated. The default, fo=0, asks for a report only when every mechanism fails to produce an aligned pass. fo=1 asks for one when any mechanism fails. fo does nothing without ruf. Details are in DMARC tags explained: p, sp, np, adkim, aspf, rua, ruf, fo, and t.

Sending reports to another domain: report authorization

This is the part that catches people. Say example.com publishes:

_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:reports@reports.example.net"

example.net is a different organizational domain. Without a check, anyone could publish a DMARC record that sends floods of reports to a mailbox they don't own. So the receiver must confirm that the destination domain agreed to accept reports for example.com.

The receiver looks for a TXT record at:

<policy-domain>._report._dmarc.<destination-host>

Here, that's example.com._report._dmarc.reports.example.net. If at least one TXT record there parses and starts with v=DMARC1, the destination is authorized:

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

If not, the receiver must ignore that address. The same check applies to ruf addresses.

Points to get right:

  • The destination domain publishes this record, not you. A report consumer publishes such a record in its DNS if it wishes to receive reports for other domains. A reporting service normally handles this on its own domain. If you send reports to a second domain you own, you publish it there.
  • A wildcard is allowed. A destination willing to take reports for any domain can publish *._report._dmarc.reports.example.net with v=DMARC1.
  • The destination can redirect. The authorization record may carry its own rua, but only to the same destination host.
  • Same organizational domain, no record needed. rua=mailto:dmarc@example.com on example.com's own policy doesn't need authorization.

A typical example uses shop.example._report._dmarc.personal.example with the value v=DMARC1;.

If you've seen a reference that points to the wrong place for this authorization check, the procedure is the one above: the destination domain publishes the TXT record, or that address is ignored.

Mistakes worth avoiding

  • Pointing rua at another domain that hasn't published authorization. Reports never arrive. Troubleshooting is in Why DMARC reports do not arrive and The rua mailbox is empty.
  • Forgetting mailto:. rua=dmarc@example.com isn't a valid URI.
  • Using a personal inbox that fills up with XML.
  • Turning on ruf and fo=1 without a plan for the personal data in the reports that do arrive.
  • Adding ri= or rf=. Both are historic. Remove them from old records. The !10m-style size suffix on report addresses is obsolete too.
  • Treating missing reports from one receiver as a problem with your record. For example, Microsoft 365 as a receiver sends aggregate reports only when the receiving domain's MX points directly to Microsoft 365. Provider specifics are in DMARC for Microsoft 365 and DMARC for Google Workspace.

How reports fit into DMARC overall is in What is DMARC and how it works.

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

Create a free DMARC accountTalk to an expert

FAQ

Which do I need, rua or ruf?

Start with rua. Add ruf only for a specific diagnostic need, after a privacy review, and expect most large receivers not to send them.

Why am I getting no ruf reports?

Most large receivers don't send them. Gmail doesn't support ruf, and Microsoft 365 doesn't send them.

My rua address is at my reporting provider's domain. Do I need to do anything?

The provider's domain must publish <yourdomain>._report._dmarc.<provider-host>, or a wildcard, with v=DMARC1. Reporting providers normally do this for you. Otherwise receivers ignore the address.

Can I list more than one rua address?

Yes, comma-separated, each with mailto:. Receivers may cap how many they'll send to.