More than one DMARC TXT record is published
ShipReady found multiple TXT records beginning with v=DMARC1 at the discovered DMARC name.
Why it matters
DMARC receivers need one usable policy record at a name; duplicate records should be reconciled before relying on the policy.
How ShipReady detects it
What it inspects
ShipReady queries the discovered DMARC DNS name and counts TXT records that begin with v=DMARC1.
What triggers a finding
The rule triggers when more than one qualifying DMARC record is observed at that name.
What the evidence shows
Multiple qualifying DMARC TXT records were returned by the DNS lookup.
Limits of this check
ShipReady does not send mail, query receiving providers, or test DNS propagation. It does not establish delivery failure for a particular message.
How to fix it
Publish one intended DMARC record
Merge the required tags into one valid DMARC TXT record and remove duplicate records.
How to verify the change
Requery the deployed record
Inspect TXT answers at the exact DMARC name after DNS propagation.
Expected: Exactly one intended v=DMARC1 record is returned.