DMARC rua to another domain

Quick fix

A DMARC reporting service publishes this record for you. If you send reports to another domain you control, publish it in that domain, one per sending domain or a wildcard.

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

How to fix it

  1. If you use a DMARC reporting service, it publishes the record (often as a wildcard). Check that your domain is added in the service and that the address is the one it gave you.
  2. If you send reports to another domain you control, publish example.com._report._dmarc.example.net TXT "v=DMARC1;" in that domain, one per sending domain or a wildcard.
  3. Use the domain the DMARC record was found at in the name: for a subdomain with its own record that is the subdomain.
  4. Wait a day, then check that aggregate reports arrive from the large receivers.

Learn more: DMARC explained: policy, alignment and reports

How to check

The DMARC check shows the rua addresses of the record that applies to the domain. For each address in another domain, look up the TXT record at <your domain>._report._dmarc.<report domain>, for example with dig TXT example.com._report._dmarc.reports.example.net; our check does not verify it.

The DMARC check opens with your domain filled in; it runs when you press Check.

Tools to check it

What the error means

Also called external destination verification (_report._dmarc).

When the rua address of your DMARC record is in a different organizational domain, for example a DMARC reporting service, receivers first check that the other domain agrees to get your reports. It agrees by publishing a TXT record at example.com._report._dmarc.reports.example.net with at least v=DMARC1. Without it, receivers ignore the address and you get no aggregate reports, with no error message anywhere.

RFC 9990 section 4 explains why: "Without checks, this would allow a bad actor to publish a DMARC Policy Record that requests that reports be sent to a victim address". The receiver builds the name from the domain the policy was found at, the string _report._dmarc and the host in the rua URI, and looks up a TXT record. "Where the above algorithm fails to confirm that the external reporting was authorized by the Report Consumer, the URI MUST be ignored by the Mail Receiver generating the report."

The RFC's example: for blue.example.com with rua=mailto:[email protected], a receiver queries blue.example.com._report._dmarc.red.example.net. A report consumer that accepts reports for any domain can publish *._report._dmarc.red.example.net instead. The record may contain its own rua, which then replaces yours, but only with the same destination host. No verification is needed when the address is in your own organizational domain, for example [email protected] for shop.example.com.

Sources

All findings