Multiple DMARC Records Found
A domain must publish exactly one DMARC record. If multiple DMARC TXT records exist under the _dmarc subdomain, receiving servers cannot determine which policy should apply, and DMARC validation becomes ambiguous or invalid.
One-Minute Fix
Remove duplicate DMARC records and keep only one valid DMARC policy under the _dmarc hostname.
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.comA domain must publish one DMARC policy, not several competing ones.
Re-checkWrong vs correct setup
Wrong setup
v=DMARC1; p=none; rua=mailto:dmarc@example.com
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.comThis is broken because the domain publishes two separate DMARC policies at the same hostname. Receivers cannot reliably determine which policy should apply.
Correct setup
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.comThis is the correct pattern. The domain publishes one clear DMARC policy, so receivers can evaluate and enforce it correctly.
Why this happens
Multiple DMARC records often appear when DNS providers migrate records, when different teams add policies independently, or when an old DMARC policy is not removed before a new one is added.
Why this is a problem
- DMARC validation fails or becomes ambiguous.
- Receivers cannot determine which policy to apply.
- Anti-spoofing enforcement becomes unreliable.
- Troubleshooting becomes harder because the record exists but is still broken.
How this affects deliverability
Multiple DMARC records create policy ambiguity. That weakens trust in the domain and prevents receivers from enforcing authentication policies consistently.
Common causes
- DNS migrations duplicated records.
- Two administrators published separate policies.
- Automated tools added a new DMARC entry without removing the old one.
- Legacy TXT records were preserved accidentally.
What we checked
We searched for multiple TXT records beginning with v=DMARC1 under the _dmarc hostname. If more than one exists, DMARC evaluation becomes invalid or ambiguous.
Live DNS lookup. No login. No saved domains. No tracking.
FAQ
Can I have two DMARC records during migration?
No. Even during migration, the domain should publish one final DMARC policy under _dmarc.
What if the two records are similar?
That still creates ambiguity. DMARC expects a single authoritative policy record.
How do I fix this safely?
Identify the record you actually want to keep, merge any needed tags into one final policy, and remove the duplicate.
Next steps
- Check all TXT records under _dmarc.
- Identify which DMARC policy should remain active.
- Merge required tags into one final record if needed.
- Delete the duplicate DMARC record.
- Re-run the check after DNS propagation.
- Review the full troubleshooting guidance in the DMARC Hub.
- Explore sender authorization issues in the SPF Hub.
- Check signing and selector issues in the DKIM Hub.