DMARC reports not arriving: external destination not authorized

Receivers only send reports to another domain if that domain agrees to receive them. How the _report._dmarc record works.

You pointed rua= at an address on another domain, and reports never arrive, or only from some providers. Checkers may report "external destination not verified" or "rua domain not authorized".

Why receivers need permission

Without a safeguard, anyone could publish a DMARC record that points rua= at a victim's address and flood it with reports. So when the report address is on a different organizational domain than the domain being reported on, receivers first check that the report domain agrees. They look up this TXT record:

<your domain>._report._dmarc.<report domain>

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

If it doesn't exist, Google, Microsoft, Yahoo and most others silently drop the reports.

How to fix it

  • You use a DMARC reporting service: the service must publish this record, usually as a wildcard (*._report._dmarc.…) covering every customer. If reports don't arrive, check that the address you used is exactly the one they gave you, then ask them.
  • You send reports to another domain you own (for example from brand.com to company.com): publish brand.com._report._dmarc.company.com TXT "v=DMARC1" in the DNS of company.com.
  • Same organizational domain: reports for shop.example.com sent to dmarc@example.com need no authorization.

You can check the record yourself: dig TXT example.com._report._dmarc.reports.example.net +short should return "v=DMARC1".