MediumPolicy · usually medium
DMARC record requests no aggregate reports
There is no rua address, so you receive no data about who sends as your domain.
Check your own domain
What causes this
The rua tag is the address receivers send daily aggregate reports to. Those reports are the only broad view you get of which systems send mail using your domain and whether they authenticate. Without rua, a p=none policy accomplishes nothing at all — it neither enforces nor informs.
What it breaks
You cannot tell whether raising the policy would break legitimate mail, which is exactly the information needed to move beyond p=none safely.
How to fix it
Add an rua address to the record.
- Choose a mailbox or DMARC reporting service to receive the reports.
- Add rua=mailto:that-address to the DMARC record.
- If the address is at a different domain, that domain must publish an authorisation record — see the external reporting finding.
Example record
TXT · _dmarc
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
Specification: RFC 7489 — DMARC
Related problems
- BIMI record published without DMARC enforcementBIMI requires a DMARC policy of quarantine or reject. The record will be ignored.
- External reporting address is not authorisedReports are directed to another domain that has not published the required authorisation record.
- DMARC policy is set to noneThe policy monitors but does not act — failing mail is still delivered.
- Subdomain policy is weaker than the domain policysp= is set to a laxer value than p=, leaving subdomains less protected.
- Non-sending domain is not protected against forgeryThis domain appears not to send mail, but publishes no policy preventing others from doing so.