Email Marketing

SPF

Also called Sender Policy Framework

A DNS record naming the mail servers allowed to send for your domain, checked by receivers as messages arrive.

Quick facts: SPF

Category
Email Marketing
Also called
Sender Policy Framework
Level
Intermediate
Affects
Deliverability, spoofing protection, bulk sender compliance
Where to see it
Your DNS panel, public SPF lookup and validation checkers
In this article4
  1. How SPF works
  2. Why SPF matters
  3. Common mistakes with SPF
  4. How to act on it

How SPF works

Sender Policy Framework is a single TXT record published in your domain’s DNS. It names the mail servers and services permitted to send on your behalf, usually by referencing each provider’s own published list rather than by writing out addresses. When a message arrives, the receiving server looks up that record and asks a simple question: did this connection come from somewhere the domain owner allowed?

The record ends with an instruction covering everything not listed. A soft fail asks receivers to accept the message but mark it as suspect; a hard fail asks them to treat it as unauthorised. Receivers are free to interpret both, which is one reason SPF alone is not enough.

Two details catch people out. SPF checks the hidden return-path domain, not the from address your recipient reads, so a forger can pass SPF while still displaying your name — closing that gap is what DMARC exists for. And the specification caps the record at ten DNS lookups; exceed it and the check fails outright, which happens easily once several tools are added over the years.

Why SPF matters

It is the oldest and simplest of the three authentication checks, and the one most receivers look at first. Bulk mail from a domain with no SPF record has an obvious mark against it before anything else is considered, and major providers now expect bulk senders to publish one.

It is also the record most likely to be quietly broken. Because it is a single line that everything shares, adding a new invoicing tool or moving to a new email host can push it past the lookup limit and break authentication for every system at once, including mail that had worked for years.

Common mistakes with SPF

Publishing more than one SPF record for the same domain is the classic error. The specification allows only one, and a second causes a permanent error, so the correct approach when adding a sender is to extend the existing record rather than add another.

Listing everything you can think of is the next. Broad inclusions and old vendors pile up lookups and authorise services you no longer use. Prune the record when you drop a tool, not just when something breaks.

Finally, SPF does not survive most forwarding. When a recipient auto-forwards your message, the forwarding server becomes the sender and the check fails, through no fault of yours. That is expected behaviour and the reason DKIM is needed alongside it, since a DKIM signature travels with the message.

How to act on it

Write down every service that sends mail using your domain — marketing platform, website contact forms, invoicing, helpdesk, booking system, your own mail host — then build one record that covers all of them and nothing else. Publish it, then verify with a public SPF checker that it resolves cleanly and stays within the lookup limit.

Treat it as a living record. Re-check after any migration, and whenever a colleague signs up for a new tool that sends on your behalf. Pair it with DKIM and a DMARC policy, because SPF on its own protects the envelope rather than the name your customer actually sees, and a domain with only SPF still lets a convincing forgery through.

Do and do not

Do

  • Keep exactly one SPF record and edit it when adding senders
  • Check the record stays inside the ten lookup limit
  • Remove vendors from the record when you stop using them

Do not

  • Publish a second SPF record for the same domain
  • Expect SPF alone to stop spoofing of your visible name
  • Treat forwarding failures as a fault in your setup

Questions people ask about this

Can I have more than one SPF record?

No. The specification permits exactly one SPF record per domain, and publishing a second causes a permanent error that fails the check for every sender at once. When you add a new tool, edit the existing record to include it rather than creating another line. This is one of the most common authentication faults.

Why does SPF fail when someone forwards my email?

Because the forwarding server, not yours, is the one connecting to the final recipient, and that server is not on your list. It is normal and it is not something you can fix from your side. A DKIM signature survives forwarding, which is why the two records are used together rather than as alternatives.

Does SPF stop someone spoofing my company name?

Not on its own. SPF validates the hidden return-path domain rather than the from address a recipient reads, so a forger using their own authenticated domain can still display your business name. Stopping that requires DMARC, which insists the visible domain lines up with what was actually checked.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.