Some DMARC values are invalid
Your policy applies, but receivers skip some of the record's other values. For each one they use a default, which may not be what you meant.
Some DMARC values are invalid
Receivers ignore those values and use their defaults, which may not be what you meant.
Receivers use the default for each invalid value: invalid rua= address.
A frequent cause is a report address without mailto:, as in rua=reports@example.com. Receivers send nothing to it, so you get no reports and the record looks fine.
RFC 9989 section 4.8 sets the rule: "Syntax errors in the remainder of the record MUST be discarded in favor of default values (if any) or ignored outright." What the check looks at, and what a receiver does with a bad value:
| What the result names | Valid values | A receiver uses |
|---|---|---|
adkim, aspf | r or s | relaxed alignment, r |
rua | addresses such as mailto:reports@example.com, separated by commas | no reports to that address |
ruf | the same | no failure reports to that address |
fo | 0, 1, d and s, separated by colons, each once; not 0 and 1 together | 0 |
psd | y, n or u | u |
t | y or n | n |
malformed tag | a part with no = | nothing: it is skipped |
The check reads adkim, aspf and the policy values in lower case only, so it also names adkim=S. A receiver that follows the standard accepts either case; lower case keeps every reader in agreement.
A malformed tag is usually a stray word or a missing =, as in v=DMARC1; p=none; rua mailto:reports@example.com. Write it as tag=value or delete it.
Correct the values
- Read the record: open Details → on your result, or run
dig +short TXT _dmarc.example.comwith your domain in place ofexample.com. - At your DNS provider, edit the TXT record at
_dmarc.in front of the domain you checked. Many DNS providers want only the part before your main domain:_dmarcforexample.com,_dmarc.mailformail.example.com. Correct each value the result names, using the table. - Run the check again.
Last updated .