SPF, DKIM and DMARC explained in plain English
Three standards work together to prove an email really came from you. Here is what each does, without the jargon.
SPF: who is allowed to send
SPF is a published list of the mail servers authorised to send for your domain. The receiver checks whether the sending server is on that list. It answers: is this server allowed?
DKIM: a tamper-proof signature
DKIM adds a cryptographic signature to every email, verified against a public key in your DNS. It answers: was this message really signed by the domain, and unaltered in transit?
DMARC: the policy that ties them together
DMARC does two things. It tells receivers what to do when an email fails both SPF and DKIM alignment (none, quarantine, or reject). It also asks them to report back on everything sent in your name.
DMARC only passes if SPF or DKIM passes AND the verified domain matches your visible From address. That alignment requirement is what actually stops spoofing.
How they fit together
- SPF authorises your servers.
- DKIM signs your mail.
- DMARC enforces the policy and gives you visibility.
The ClearAuth suite manages all three as one system: ClearSPF, ClearDKIM and ClearDMARC.