Reading the Authentication-Results header
Quick fix
Read dmarc= and header.from= first, then the spf= and dkim= results for the same domain; for dkim=neutral or temperror, check the selector's key record.
How to fix it
- Find the header added by your own receiving server: the first
Authentication-Resultsfrom the top, with your provider's host name. - Read
dmarc=andheader.from=first, then thespf=anddkim=results whose domain matches the From domain. - For
dkim=neutralorpermerror, check the key record of the selector for syntax errors and a completep=value. - For
dkim=temperror, check that the selector record exists and that the domain's name servers answer; send again to see whether it was transient. - For
dmarc=failwith a passing SPF or DKIM result for another domain, set up DKIM with your own domain at that sending service.
Learn more: DKIM explained: selectors, keys and rotation
How to check
For a dkim=neutral, temperror or permerror result, take the d= and s= tags from the message's DKIM-Signature header and check that selector with the DKIM check. It reports a missing record, a record with syntax errors and a key that does not decode. The DKIM selector finder tries common selectors when you have no message at hand.
The DKIM record check opens with your domain filled in; it runs when you press Check.
Tools to check it
What the error means
dkim=neutral, dkim=temperror (no key for signature), dmarc=pass (p=NONE sp=NONE dis=NONE)
Authentication-Results is the header a receiving server adds to say what its SPF, DKIM and DMARC checks found. It is defined in RFC 8601. A short one, from RFC 7208 section 9.2, reads "Authentication-Results: myhost.example.org; spf=pass smtp.mailfrom=example.net": first the name of the server that checked, then one result per method with the domain it was checked for.
Each method has its own field for the domain. smtp.mailfrom= is the domain SPF checked (the envelope sender), header.d= or header.i= the DKIM signing domain, and header.from= the domain DMARC checked; RFC 9989 registers it as "The domain portion of the RFC5322.From header field". DMARC passes when SPF or DKIM passes for a domain aligned with header.from.
The DKIM results are defined in RFC 8601 section 2.7.1. Two that confuse people:
dkim=neutral: "The message was signed, but the signature or signatures contained syntax errors or were not otherwise able to be processed. This result is also used for other failures not covered elsewhere in this list."dkim=temperror: "The message could not be verified due to some error that is likely transient in nature, such as a temporary inability to retrieve a public key. A later attempt may produce a final result."
Microsoft documents its DMARC field as "dmarc=<pass|fail|bestguesspass|none> action=<permerror|temperror|oreject|pct.quarantine|pct.reject> header.from=<domain>", where action is what it did with the message. Headers from Gmail can carry extra fields in parentheses, for example (p=REJECT sp=REJECT dis=NONE), a frequent question on Server Fault. Google does not document these fields, and dis is not one of the properties RFC 9989 registers for DMARC (header.from and policy.dmarc). Read the result (dmarc=pass or dmarc=fail), not the comment.
Trust only the header your own receiving server added: any other copy can be written by the sender. RFC 8601 section 5 says a server "MUST delete any discovered instance of this header field that claims, by virtue of its authentication service identifier, to have been added within its trust boundary but that did not come directly from another trusted MTA."
Sources
- RFC 8601: Authentication-Results header field, sections 2.7.1 and 5 (checked 2026-11-16)
- RFC 7208: Sender Policy Framework (SPF), sections 2.3, 2.6, 9.1 and 10.1.2 (checked 2026-11-16)
- RFC 9989: DMARC (Authentication-Results method dmarc) (checked 2026-11-16)
- Microsoft Learn: Anti-spam message headers in Microsoft 365 (checked 2026-11-16)
- Server Fault: What does dis=NONE mean in an email's Authentication-Results header? (checked 2026-11-16)