DMARC rua Reports Not Arriving: External Destination Verification
The short answer (what's causing it)
If rua= points to a mailbox on a different domain, RFC 7489 requires that domain to publish an authorisation record. Without it, many receivers silently drop the reports.
Step-by-step fix
- Check whether the rua domain differs from your domain.
- On the receiving domain, publish
example.co.uk._report._dmarc.receiver-domainTXTv=DMARC1. - Or route reports to a mailbox on your own domain.
- Wait for the next daily report cycle.
Record examples (replace example.co.uk with your domain)
example.co.uk._report._dmarc.reports.example.net. TXT "v=DMARC1"
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: DMARC.
Scan my domain free (20-check SuperTool) → £24 Sovereign DMARC (T0 RUA), SPF, MTA-STS & PHP2Shell Remediation Pack → £19 NIS2, DORA & ISO 27001 Supplier Posture Bulk Auditor Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
Why route reports in-house?
It keeps report data under your control; third-party routing is an observation to review against your own data-transfer assessments, not automatically a breach.
How often do reports arrive?
Typically daily per reporting receiver.
Related FaultyPacket guides & tools
- Free 20-check SuperTool
- DMARC RUA first-party reporting vs external SaaS
- DMARC SaaS dashboard vs enforcement scorecard
- Internet Mail Security Observatory
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.