Fix the invalid DMARC record

Why it matters

Receivers ignore a DMARC record they cannot parse, so no policy applies even though a record exists. The scan shows what did not parse.

The fix

1. The record must begin with v=DMARC1 and must contain a p= tag with the value none, quarantine or reject. Tags are separated by semicolons.
2. Report addresses in rua must be URIs written as mailto:name@example.com (comma-separated for several), not bare email addresses.
3. Retype the record by hand if it was pasted from a document, because curly quotes and non-breaking spaces break parsing. Edit the record at _dmarc in place; do not add a second one.
4. Fixing it makes DMARC start applying, so if the record says p=quarantine or p=reject, first check that your legitimate mail passes SPF or DKIM; use p=none if you are not sure.

_dmarc.example.com.  IN TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

The examples use example.com. Replace it with your own domain.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the DMARC policy check
• Publish a DMARC record, starting in monitoring mode
• Keep only one DMARC record
• Move DMARC from monitoring to quarantine, then reject
• Move DMARC from quarantine to reject
• Remove the pct tag from the DMARC record
• Remove the t=y test flag from the DMARC record
• Make the DMARC subdomain policy match the main policy
• Add a report address to the DMARC record
• Remove or fix the invalid tags in the DMARC record