External destination verification
The check that a DMARC report address outside the domain's organization agreed to receive its reports, via a TXT record under _report._dmarc.
What it means
Without a safeguard, anyone could publish rua=mailto:victim@example.net and send failing mail to flood that address with reports. So when the rua or ruf address is in a different organizational domain, receivers look for a TXT record that starts with v=DMARC1 at the policy domain, then _report._dmarc, then the report domain: blue.example.com._report._dmarc.red.example.net.
If the record is missing, the receiver ignores that address. A reporting service that accepts reports for any domain publishes a wildcard, *._report._dmarc.reports.example.net. The authorizing record may also carry its own rua to redirect reports, but only to the same host.
When reports stop arriving after a switch to a new provider, this record is the first thing to check.
Example
example.com._report._dmarc.reports.example.net. TXT "v=DMARC1"Related terms
On this site
Sources
What this definition rests on. The wording is ours; the facts are theirs.
- RFC 9990: DMARC Aggregate Reporting, section 4rfc-editor.org
- RFC 9991: DMARC Failure Reporting, section 5rfc-editor.org
- Google Workspace Admin Help: Set up DMARCknowledge.workspace.google.com
All 432 terms in the glossaryThe wiki: blocklists and bounce codes