DMARC record has no supported policy value
ShipReady found one qualifying DMARC record, but its parsed p tag was absent, empty, or not a supported policy value.
Why it matters
The p tag expresses the policy value in a DMARC record. Its value should be chosen after the organisation has separately validated its intended sending paths.
How ShipReady detects it
What it inspects
ShipReady finds a qualifying DMARC TXT record and parses its semicolon-separated key=value tags. This rule applies only when exactly one qualifying record is found at the selected DMARC name.
What triggers a finding
The rule triggers when the parsed p tag is absent, empty, or not one of none, quarantine, or reject. Multiple qualifying records are handled by the separate duplicate-DMARC-record rule.
What the evidence shows
The selected DMARC record did not contain a supported p policy value under ShipReady's tag parsing.
Limits of this check
ShipReady performs bounded DNS and text parsing, not complete RFC DMARC validation. It does not send email, test alignment, reporting, receiver behavior, message rejection, inbox placement, or deliverability.
How to fix it
Review intended mail senders
Confirm which services legitimately send mail for the domain and validate their authentication behavior separately.
Set one supported policy value
Correct the DMARC record so its p tag is deliberately set to none, quarantine, or reject. Choose the value as part of an intentional rollout rather than from the scanner result alone.
Check for duplicate records
Ensure the selected DMARC name returns one intended qualifying DMARC record; resolve duplicate records through the separate duplicate-record issue when present.
How to verify the change
Inspect the published DMARC TXT value
After DNS propagation, query the exact DMARC name and confirm the single intended record contains the chosen p value.
Expected: One qualifying DMARC record is returned and its parsed p value is none, quarantine, or reject.