DMARC policy is monitoring-only
ShipReady found one valid DMARC record with p=none.
Why it matters
A monitoring policy can help validate legitimate senders before enforcement, but it asks receivers to monitor rather than quarantine or reject failures.
How ShipReady detects it
What it inspects
ShipReady queries the discovered DMARC record, parses its tags, and checks the p value after rejecting duplicate or unusable records.
What triggers a finding
The rule triggers when one usable DMARC record has p=none.
What the evidence shows
The observed usable DMARC record declares p=none.
Limits of this check
ShipReady does not send mail, examine alignment results, receive aggregate reports, or determine how any receiver treats a message. p=none is not missing DMARC and can be an intentional rollout stage.
How to fix it
Review legitimate sender alignment
Use monitoring data to confirm authorised senders pass before choosing an enforcement policy.
Choose enforcement deliberately
Move to quarantine or reject only when the organisation has validated its sending paths.
How to verify the change
Recheck the published policy
Query the DMARC TXT record and confirm the intended p value after rollout.
Expected: The record expresses the organisation's deliberate monitoring or enforcement policy.