Topic · Authentication
Email authentication
Email authentication is the collection of controls that help receivers verify sending infrastructure and domain identity.
How it works
SPF authorizes envelope senders, DKIM signs content and DMARC checks alignment and policy.
What can go wrong
Authentication reduces identity abuse but does not guarantee harmless content.
What to check or do
Deploy SPF, DKIM and DMARC together and continuously validate sending sources.
How to investigate Email authentication
- Signal to investigate
- An ESP dashboard reports SPF and DKIM success while receiver headers still report DMARC fail.
- Evidence to collect
- Collect an original message and its Authentication-Results, RFC5322.From, MAIL FROM, DKIM d= and s= values.
- Common wrong conclusion
- Authentication success is not the same as author-domain alignment or proof that the sender is trustworthy.
How to interpret the evidence
SPF authenticates an envelope identity; DKIM authenticates a signing identity; DMARC requires a passing and aligned identity. A lookalike domain can authenticate its own messages and still be malicious.
What to change and how to verify it
Inventory every outbound platform, align at least one identifier for each stream, then retest from real receiving mailboxes.
Put this into practice
Run a focused check, then explore protection if your domain needs it.