Receivers ignore your DMARC record
The record is there, but receivers discard it whole because of one mistake in it. Until it's fixed, your domain has no DMARC policy and you get no reports.
Fixing the mistake puts the record's policy into force at once. If it says quarantine or reject, first check that your own mail passes: read the reports from before the mistake, or confirm each service you send through. When you aren't sure, fix the record with every policy at none (p=none, and sp=none and np=none if those tags are there) and tighten it once reports arrive.
The third line of the result names the mistake:
Receivers ignore your DMARC record
Something in the record stops receivers from reading it, so your domain has no DMARC protection.
Receivers ignore this DMARC record: duplicate tag p.
A tag written twice
duplicate tag p means the record says p= twice, as in v=DMARC1; p=reject; p=none. DMARC records use the DKIM tag syntax, where a repeated tag makes the whole record invalid (RFC 6376 section 3.2). Any tag counts, not only p.
At your DNS provider, edit the TXT record at _dmarc. in front of the domain you checked (many want only the part before your main domain: _dmarc for example.com, _dmarc.mail for mail.example.com), and keep one copy of the tag. For a repeated p, keep p=none unless you've checked your mail passes, as above.
A policy value receivers don't know
invalid p= value rejct means p=, sp= or np= holds something other than none, quarantine or reject. The check reads these values in lower case only, so it also reports p=Reject. The standard's grammar ignores case here, so a receiver that follows it reads Reject as reject; writing lower case keeps every reader, this check included, in agreement.
An unknown policy value alone doesn't sink the record. It does here because the record also has no valid report address. RFC 9989 section 4.10.1 says a receiver then "applies no DMARC processing". With a valid rua=mailto: address, receivers fall back to p=none instead: see DMARC only watches because of a mistake.
Correct the value, or set the policies to none as above until you've checked your mail passes. Give the record a report address too: fix the existing rua= if it has one, for example by adding mailto: in front, or add rua=mailto:dmarc-reports@example.com if it has none.
Check your fix
With your domain in place of example.com:
dig +short TXT _dmarc.example.com
Details → on your result shows the same record.
Split the line containing v=DMARC1 at each semicolon. No tag name should appear twice, and p=, sp= and np= should each hold exactly none, quarantine or reject. Then run the check again.
For bulk senders, Gmail treats a record it can't use like no record (Gmail SMTP errors, updated 10 Nov 2026):
550 5.7.40 Your message was blocked because the sending domain doesn't have a DMARC record or the DMARC record doesn't specify a DMARC policy.Last updated .