Email was designed in the eighties with no way to check who was sending what. Anyone could write whatever sender they liked, the same way anyone can write whatever return address they like on an envelope. The three records in this article are the patches the industry bolted on afterwards to fix that.
They live in your domain's DNS, the public directory where your company declares how its presence on the internet works. When Gmail receives an email claiming to be from you, it consults that directory to decide whether to believe it.
SPF — who is allowed to send
SPF is a list of servers authorised to send email on behalf of your domain. It looks like this:
v=spf1 include:_spf.google.com include:sendgrid.net -all
Translated: "Google's and SendGrid's servers may send on my behalf; reject anyone else." That -all at the end is the part people leave out, and it is precisely the part that does the work. Without it you are publishing a guest list and leaving the door open.
The most common SPF failure is not the absence of one: it is an SPF that breaks from piling up providers. There is a limit of ten lookups, and once you pass it the record stops counting, with no warning. We cover it in detail in the article on the 10-lookup limit, with measurements of Mexican brands.
DKIM — the signature proving nothing was altered
DKIM puts a cryptographic signature on every message. The receiving server takes the public key from your DNS and checks two things: that the message came from who it claims, and that nobody modified it along the way.
If SPF is the guest list, DKIM is the hologram on the ticket. SPF authorises the server; DKIM protects the contents.
DKIM has one practical quirk: the key is published under an arbitrary name chosen by your provider, called a selector. Google uses one, Microsoft another, and a company can use whatever it likes. That is why no external tool can state with certainty that you don't have DKIM — only that it didn't find it where it usually lives. Any checker that flatly tells you "you have no DKIM" is claiming more than it can know.
DMARC — the instruction for what to do when something fails
SPF and DKIM check things, but neither says what to do if the check fails. That is DMARC:
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
p=reject means "if a message claims to be from me and doesn't pass the checks, reject it". And rua is the address where you want to receive reports on who has been trying to send in your name.
Here is the costliest misunderstanding of the three: publishing DMARC is not the same as switching it on. The p=none policy reports but does not protect — the forged email gets through all the same. And that is where a great many companies stop, large ones included: we went through it in a separate article.
What almost nobody explains: alignment
You can have a valid SPF, DKIM signing and DMARC published, and still fail. DMARC does not merely require that SPF or DKIM pass: it requires that the domain which passed the check match the one the recipient sees in the "From:".
The typical case: you hire an invoicing platform that sends to your customers from notificaciones@[the-platform].com but puts your name in the visible sender. SPF passes — for the platform's domain — and DMARC fails anyway, because it doesn't align with yours. This is invisible if you only inspect records; it shows up in DMARC reports after days of collection.
Check how yours are doing
Your domain's SPF, DKIM and DMARC, in seconds and from your browser. No sign-up, and without giving us any access.
Where to start
- SPF first, ending in
-all, with every one of your sending services listed and none to spare. - DKIM on every platform that sends email as you: your mailbox provider, your invoicing system, your campaign tool.
- DMARC on
p=noneto begin with, with reporting switched on, so you can see who sends in your name without breaking anything. - Move up to
quarantineand thenrejectonce the reports show all your legitimate email aligns. This is the step most companies never take.
Order matters. Setting p=reject before you know who sends on your behalf is the fastest way to stop your own invoices from arriving.
Keep reading
- The 10-lookup SPF limit that breaks your email without warning We measured ten Mexican brands: two are at the exact limit.
- Your DMARC on p=none is not protecting you Publishing it is not enabling it, and the difference is paid in impersonation.