SPF, DKIM, and DMARC
SPF, DKIM, and DMARC are key tools in email authentication. They work together to help prevent email spoofing, phishing, and spam, making sure emails really come from who they claim to come from.
Let’s break them down in simple terms:
✅ SPF – Sender Policy Framework
What it does:
Verifies whether an email is sent from an authorized server for a domain.
How it works:
Your domain publishes a list of IPs/servers allowed to send email (in a DNS TXT record).
When an email arrives, the receiving mail server checks:
➜ “Is this server allowed to send mail for this domain?”
Example:
Your domain is example.com
. You allow Microsoft 365 to send emails on your behalf. You publish an SPF record like:
✉️ DKIM – DomainKeys Identified Mail
What it does:
Adds a digital signature to the email to prove it hasn’t been tampered with and really comes from your domain.
How it works:
Your mail server signs outgoing emails with a private key.
Receivers use your public key (published in your domain’s DNS) to verify the signature.
This proves:
✔ The email content wasn’t altered
✔ It really came from your domain
DKIM does not encrypt the email concepts.
DKIM is added as CNAME record.
🛡️ DMARC – Domain-based Message Authentication, Reporting & Conformance
What it does:
Builds on SPF and DKIM to tell receiving servers what to do if an email fails those checks.
How it works:
You publish a DMARC policy in DNS:
none
(monitor only)quarantine
(send to spam)reject
(block the message)
You can also get reports about who’s sending email using your domain (including fraudsters!)
Example DMARC record:
🔄 How They Work Together:
SPF checks the sending server.
DKIM verifies the integrity and authenticity.
DMARC ties them together and enforces a policy.
🔐 Why Use Them?
Protects your brand from being spoofed
Reduces phishing attacks
Improves email deliverability
Helps emails avoid the spam folder