Skip to content
BENIBIX Learn

SPF vs DKIM

People think SPF and DKIM do the same check, and they do not. SPF asks if the server that sent the email is on the domain's list of allowed senders. DKIM checks a hidden signature on the email itself. It proves the email came from the domain and was not changed. Forwarding often breaks SPF but leaves DKIM whole.

Infrastructure🔒 Security

Sender Policy Framework (SPF)

A public list of who may send email for a domain.

SPF is a list of the mail servers allowed to send email for a domain. The list is kept in the domain's DNS records, where anyone can read it. A mail server that gets an email checks the list. Mail from any other server looks fake. It stops people faking your domain on an email.

Example
A shop sends newsletters through an email service and receipts through its web shop. Its SPF record names both, so mail from either one passes.
Why it matters
Without it, anyone can send mail that claims to come from your domain. Big mail services now expect it from every bulk sender.
Full entry
Infrastructure🔒 Security

DomainKeys Identified Mail (DKIM)

A hidden mark on each email. It proves who sent it and that nobody changed it.

DKIM adds a hidden signature to each email a domain sends. The sending server signs the email with a secret key. The matching public key sits in the domain's DNS records. The server that gets the email uses it to check two things. The email really came from that domain, and nobody changed it on the way.

Example
A bank signs every email with DKIM. A fake email that copies its logo has no real signature. So the server that gets it flags it.
Why it matters
It proves an email is real even after it has been forwarded. Mail services trust signed mail more.
Full entry

In one line

Sender Policy Framework (SPF)
A public list of who may send email for a domain.
DomainKeys Identified Mail (DKIM)
A hidden mark on each email. It proves who sent it and that nobody changed it.