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
| Part | What it tells you |
|---|---|
dkim=pass header.i=@example.com | A 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=failwith SPF or DKIM passing: compare the domains. Ifsmtp.mailfromandheader.i/header.dbelong 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)orpermerror: the key isn't published.spf=softfailorfail: 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.