Skip to main content
MediumEmailOWASP A09:2021CWE-16

How to fix: DMARC reports sent to an external domain that has not authorized them

DMARC reports are addressed to a different domain that has not authorized receiving them. RFC 7489 section 7.1 requires the destination to publish an authorization record before a receiver will send cross-domain reports.

Why it matters

Conforming receivers, which includes the large mailbox providers, will not send reports to a third-party domain that has not opted in. The reports are silently not sent, so the visibility DMARC was deployed for does not exist, and any decision to tighten the policy from none to quarantine or reject is being made without data on who it would affect.

The authorization record lives in the destination's zone rather than yours: the report processor has to publish <your-domain>._report._dmarc.<their-domain> with a v=DMARC1 value. Managed DMARC platforms create it automatically once the domain is added in their console, so the usual cause of this finding is a domain that was put in the DMARC record before it was added to the platform, or one that was later removed from the platform without the DNS record being updated.

How to fix it

  1. 1Add the domain in your report processor's console so it publishes the authorization record.
  2. 2If you run the destination yourself, publish the authorization record there.
  3. 3Keep a mailbox on your own domain in the rua list as well, so reports do not depend entirely on a third party.

Code examples

The record the destination must publish

DNS
example.com._report._dmarc.analyzer.example. IN TXT "v=DMARC1"

Check it

bash
dig +short TXT example.com._report._dmarc.analyzer.example

References

Detected automatically by VulnRadar. The check id is email-dmarc-rua-external-unauthorized, stable across every scan so you can filter or diff on it.

See every email check

Questions

How severe is DMARC reports sent to an external domain that has not authorized them?
VulnRadar rates this medium severity in the email category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id email-dmarc-rua-external-unauthorized, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does DMARC reports sent to an external domain that has not authorized them map to?
It maps to CWE-16. In the OWASP Top 10 it falls under A09:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for dmarc reports sent to an external domain that has not authorized them

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

DMARC reports sent to an external domain that has not authorized them | VulnRadar