How to read the Authentication-Results header

See for yourself whether a message passed SPF, DKIM and DMARC, and which domain each check was about.

Every major mailbox provider adds an Authentication-Results header to incoming mail, recording what it found. It's the quickest way to see why a message went to spam or failed DMARC. In Gmail, open the message, choose the three-dot menu and Show original. In Outlook, open the message's properties or "View message source".

Authentication-Results: mx.google.com;
       dkim=pass header.i=@example.com header.s=google header.b=Xk2P1a9e;
       spf=pass (google.com: domain of jan@example.com designates 209.85.220.41
           as permitted sender) smtp.mailfrom=jan@example.com;
       dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=example.com

Reading it line by line

PartWhat it tells you
dkim=pass header.i=@example.comA DKIM signature for example.com was valid. header.s is the selector. There can be several dkim= results, one per signature.
spf=pass … smtp.mailfrom=SPF result for the envelope sender's domain, which is not necessarily the From domain.
dmarc=pass … header.from=The DMARC verdict for the From domain. p= is the published policy; dis= is what was actually done (NONE, QUARANTINE, REJECT).

What to look for

  • dmarc=fail with SPF or DKIM passing: compare the domains. If smtp.mailfrom and header.i/header.d belong to your email provider instead of your domain, it's an alignment problem.
  • dkim=fail (body hash did not verify): the message was changed after signing.
  • dkim=neutral (no key) or permerror: the key isn't published.
  • spf=softfail or fail: the sending server isn't in your SPF record.
  • spf=permerror: your SPF record can't be evaluated at all.
  • arc=pass: the message was forwarded, and an intermediary vouched for its original authentication.

Only trust the Authentication-Results header added by the receiving provider, the one at the top. Headers further down were added by other servers, and a sender can fake them.