Skip to content
DocumentationAPI reference Build something worth sending.

Guides

DMARC rua and aggregate reports

What the DMARC rua tag does, how to write it, why reports to another domain need an authorization record, and how to read the XML reports that arrive.

The rua tag in a DMARC record tells mailbox providers where to send aggregate reports. Those reports list the IP addresses that sent mail using your domain, and whether each one passed SPF and DKIM. Without them you are guessing which senders will break when you move to p=quarantine or p=reject.

The rua format

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

The value is a mailto: address. For more than one address, separate them with commas:

rua=mailto:dmarc@example.com,mailto:reports@dmarc-vendor.example

Leave out mailto: and receivers will not send reports. A record with no rua still works as a policy. You just will not hear anything back.

Reports to an address on another domain

If the address is on a different domain from the policy, such as a reporting service, that domain has to agree to receive them. It publishes a TXT record that names your domain:

example.com._report._dmarc.dmarc-vendor.example  TXT  "v=DMARC1"

Reporting services publish this for their customers. If you point rua at a mailbox on a second domain you own, publish it yourself. Without it, many receivers skip the report. The DMARC checker warns about an address on another domain. It does not look the authorization record up.

What arrives

Large mailbox providers send one report a day per domain, as a zipped or gzipped XML attachment. Each row is a source IP, a message count, the SPF and DKIM results, whether each one aligned with the From domain, and what the receiver did. Expect a report from each provider that received your mail that day, so a busy domain gets many.

Raw XML is hard to read at volume. A free parser, a DMARC reporting service, or a short script that groups rows by source IP is enough to see the senders. Use a mailbox set aside for reports, not a person's inbox.

Reading a report

  • Your own providers should show DKIM pass and aligned. If one fails, fix its DKIM setup before you tighten the policy.
  • A source you recognize that fails both checks is a sender you forgot, like an old CRM or a billing system. Add it to SPF or set up DKIM for it, or stop it sending as your domain.
  • Sources you do not recognize, failing both, are usually forwarding or spoofing. Those are what p=reject is for.

rua and ruf

ruf asks for failure reports about single messages. Most large providers do not send them, because they can contain message content. rua is the tag that matters.

No reports arriving

Wait at least a day after publishing. Then check that the record is on _dmarc and starts with v=DMARC1, that the address is spelled right and accepts mail, and that an address on another domain has the authorization record. A domain that sent no mail that day gets no report. If the checker cannot find the record at all, see DMARC record not found.

Next steps

↑↓ to navigate↵ to openesc to close