Skip to content
All field notes

DMARC Reports to Another Domain: The _report Record

Point rua= at a mailbox on another domain and receivers drop the reports unless that domain publishes a _report._dmarc record. How to check it and fix it.

PlatOps Security TeamDeliverability6 min read
The short version
When rua= or ruf= points at a mailbox whose Organizational Domain differs from the domain that published the policy, receivers must find a TXT record at <policy-domain>._report._dmarc.<mailbox-host> before they send any report.
Without that record the receiver ignores the address. Nothing bounces and nothing tells you: the reports simply never arrive.
The record belongs to whoever owns the mailbox domain. A reporting service publishes it for you. When the mailbox is on your own second domain, or on an MSP's domain, the owner of that domain publishes it.
A per-domain record authorizes only the domains you list. A wildcard, *._report._dmarc, accepts reports for any domain that names your mailbox.

You publish a DMARC record, point rua= at the mailbox your team reads, and wait. Reports arrive for the main domain. For the second brand, the country domain or the client domain you manage, nothing comes. The record parses, the DMARC checker shows it, and receivers are skipping the address on purpose.

The cause is one missing TXT record on the domain that receives the reports. This post covers when the record is required, what it looks like, how to test it, and how reporting services and MSPs handle it.

If aggregate reports are new to you, start with what a DMARC aggregate report contains.

Why receivers ask for permission

A DMARC record is published by the domain owner, but the rua= address can name any mailbox on the internet. Without a check, anyone could publish a record for a domain they control, point it at a stranger's mailbox, and have every large receiver send that stranger daily reports. The specification closes this with a consent step: the domain that receives the reports has to say it wants them.

The procedure was section 7.1 of RFC 7489. Under DMARCbis it is section 4 of RFC 9990 for aggregate reports, and RFC 9991 applies the same procedure to ruf= failure reports. The core specification, RFC 9989, is covered in our post on what changed in DMARCbis.

When the check applies

The receiver compares two Organizational Domains: the one where it found the DMARC record, and the one in the host part of the rua= or ruf= address. If they match, it sends the report. If they differ, it runs the check first.

DMARC record on Report address Check needed?
example.com dmarc@example.com No
mail.example.com dmarc@example.com No, same Organizational Domain
example.co.uk dmarc@example.com Yes
client.example reports@msp.example Yes
example.com token@rua.reporting-service.example Yes

The third row is the one that catches in-house teams. One company, one mailbox, two registered domains. To a receiver they are unrelated.

Under DMARCbis, receivers find the Organizational Domain with a DNS tree walk instead of the Public Suffix List (RFC 9989, section 4.10). For ordinary registered domains the answer is the same.

What the receiver looks up

RFC 9990 builds the query name from three parts: the domain that published the policy, the label _report._dmarc, and the host of the report address. For a policy on example.co.uk with rua=mailto:dmarc@example.com:

example.co.uk._report._dmarc.example.com.  TXT  "v=DMARC1"

The record must parse as DMARC tags, with v=DMARC1 first. Anything else is discarded. If no valid record is found, the address "MUST be ignored by the Mail Receiver generating the report." Other addresses in the same rua= list are checked on their own, so a record that names your own mailbox and a reporting service can lose one destination and keep the other.

The receiver does not bounce anything, and no error report reaches you. The only symptom is missing data.

Testing it

Look up the DMARC record, take each rua= and ruf= host, and query the authorization name for each host that sits on a different Organizational Domain:

dig +short TXT _dmarc.example.co.uk
"v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

dig +short TXT example.co.uk._report._dmarc.example.com

An empty answer is the problem. The fix goes in the DNS of example.com, not example.co.uk:

example.co.uk._report._dmarc.example.com.  3600  IN  TXT  "v=DMARC1"

The DMARC lookup tool shows the record and its report addresses. It does not run the authorization query, so do that step by hand. Allow a day after publishing: most receivers send aggregate reports once every 24 hours.

Per-domain records or a wildcard

The RFC allows both forms. A wildcard accepts reports for every domain:

*._report._dmarc.example.com.  TXT  "v=DMARC1"

A per-domain record accepts reports for one domain only. Both styles are in use. On 3 November 2026, dmarc-reports.cloudflare.net, the host in one of the rua= addresses of cloudflare.com, answered v=DMARC1; for any domain name we tried, including one that does not exist. The same company owns both names, but they are two Organizational Domains, so the record is required.

The trade-off is control. A wildcard means that anyone can point rua= at your mailbox, and every receiver that sees their mail will send you their reports. That costs storage, and on a shared mailbox it buries the reports you care about under reports you never asked for. Per-domain records avoid that, at the price of one more DNS change each time a domain is added.

Reporting services

When rua= points at a reporting service, the authorization record lives in the service's DNS, not yours. You cannot publish it, and you do not need to.

DDMARC publishes per-domain records. On 3 November 2026, platops.com._report._dmarc.rua.ddmarc.com returned v=DMARC1 and the same query for example.com returned nothing. If you move a domain to a new reporting service, check its authorization record before you remove the old address from rua=, and keep both addresses for a few days so there is no gap in the data.

MSPs collecting client reports

An MSP that asks clients to send reports to dmarc@msp.example is in the fourth row of the table above for every client. Two ways to handle it:

  • One record per client domain, added to the onboarding checklist next to the DMARC record itself. When a client leaves, delete it, and the reports stop.
  • A wildcard on a mailbox used only for DMARC reports, accepting that unrelated reports may arrive.

The per-client record is the one that scales cleanly, because it doubles as an inventory of the domains you are collecting for. The MSP playbook covers the rest of a multi-client rollout.

Two details that trip people up

Overrides stay on the same host. The authorization record can carry its own rua= tag to redirect reports to a different mailbox, but RFC 9990 requires the new address to use the same host as the original. If it points elsewhere, the receiver sends the report to neither address.

Size suffixes are obsolete. RFC 7489 let you append a size limit to an address, such as mailto:reports@example.com!50m. RFC 9989 keeps that syntax only as obsolete grammar and tells receivers to ignore the suffix (section 4.8). It does no harm, but it no longer limits anything, so drop it when you next edit the record.

Where this matters most

Domains that send no mail are the clearest case. A parked domain has a null MX, so it cannot receive its own reports, and its rua= always points somewhere else. If the authorization record is missing, the forgeries that its p=reject policy blocks never show up in your data. The policy still works. You just cannot see what it is stopping.

The same is true for a domain that you are about to move from p=none to p=reject. The decision rests on the reports. Before you trust a quiet month, confirm that the reports were allowed to arrive.

Questions we get asked

If its rua= address is on a different Organizational Domain, check the authorization record first. For example.co.uk sending reports to dmarc@example.com, query TXT at example.co.uk._report._dmarc.example.com. If it returns nothing that starts with v=DMARC1, receivers ignore the address, as RFC 9990 section 4 requires.

Field notes, twice a month.

When a mailbox provider changes the rules, you hear it here with the record you need to change. No digest, no roundup, no product news.

Field Notes, our DMARC newsletter, twice a month, from PlatOps Security, LLC (Gaithersburg, MD). We use your address only to send it. Unsubscribe with one click in any issue. Privacy policy.