Selected DMARC record has no aggregate reporting address
ShipReady found a selected valid DMARC record whose parsed rua tag was absent or empty.
Why it matters
Aggregate reports can help an owner review how a DMARC deployment is behaving. A reporting destination should be chosen and monitored deliberately as part of that deployment.
How ShipReady detects it
What it inspects
ShipReady performs bounded DNS TXT lookups for DMARC records, selects one qualifying record, and parses its semicolon-separated key=value tags.
What triggers a finding
The rule triggers when that selected valid record has no non-empty parsed rua tag. It can apply to a monitoring policy as well as an enforcing policy.
What the evidence shows
The selected DMARC record did not contain a non-empty aggregate reporting address under ShipReady's tag parsing.
Limits of this check
ShipReady does not validate a reporting mailbox or URI, determine whether receivers support reporting, receive reports, send email, or evaluate real message authentication, receiver behavior, inbox placement, or deliverability.
How to fix it
Choose an intended reporting destination
Decide whether aggregate reporting is useful for this DMARC deployment and identify a mailbox or reporting service the team can operate.
Publish the intended rua value
Add a correctly formatted aggregate-reporting address to the selected DMARC record, following the reporting destination's setup requirements.
How to verify the change
Inspect the published DMARC TXT value
After DNS propagation, query the selected DMARC name and confirm its intended record contains a non-empty rua value.
Expected: The selected DMARC record has the intended aggregate-reporting address.