Knowledge Base

What SPF, DKIM and DMARC Actually Do

Email logo

This article explains what SPF, DKIM and DMARC actually do, and why mail fails without them.


The Problem They Solve

Email was designed without any way to prove who sent a message. Anyone can claim to be sending from your domain, and nothing in the protocol stops them. These three records are the patch, and they answer three separate questions.

Record Question it answers
SPF Is this server allowed to send for this domain?
DKIM Has this message been altered since it was sent?
DMARC What should happen when the answer to either is no?

SPF

SPF is a TXT record listing the servers permitted to send mail for your domain. A receiving server compares the sending server against that list.

The common mistake is having two SPF records. Only one is permitted per domain, and a second invalidates both. If you add a new mail provider, extend the existing record rather than creating another.

SPF also breaks on forwarding. A forwarded message arrives from the forwarding server rather than yours, which is why DKIM matters as well.

DKIM

DKIM adds a cryptographic signature to every message. The receiving server fetches your public key from DNS and checks the signature matches, which proves the message came from your domain and has not been altered in transit.

Unlike SPF, DKIM survives forwarding, because the signature travels with the message.

DMARC

DMARC ties the other two together. It tells receiving servers what to do with mail that fails, and where to send reports about it.

Policy What receivers do
p=none Deliver as normal, but send reports
p=quarantine Put failures in the spam folder
p=reject Refuse failures outright

Start at none and read the reports for a few weeks before tightening. Going straight to reject on a domain you have not checked will block legitimate mail from services sending on your behalf, such as a newsletter tool or a booking system.

What Happens Without Them

A domain with no authentication is not rejected outright, but it scores badly, so mail lands in spam more often. It can also be spoofed freely, which means someone can send convincing invoices in your name, and the bounces come back to you.

Why Mail Still Fails With Them

Authentication passing is necessary, not sufficient. Reputation, content and sending history all still count. A correctly authenticated message from a server with a poor reputation will still be filtered.


Next: How to Configure SPF, DKIM and DMARC Records covers setting them up.

Please rate this article to help us improve our Knowledge Base.

0 0