Skip to content
All terms

Glossary

SPF (Sender Policy Framework)

What Is SPF (Sender Policy Framework)? Definition and Setup Guide

SPF (Sender Policy Framework) is an email authentication standard. A domain owner publishes a list of the mail servers allowed to send email for that domain in a DNS record, and receiving mail servers check each incoming message against that list. Messages from servers not on the list can be flagged, quarantined or rejected.

For brands, SPF is a first line of defence against criminals who send phishing emails that appear to come from the brand's own domain.

What Is SPF?

SPF is defined in RFC 7208 and works through the DNS (Domain Name System). The domain owner adds a TXT record that starts with v=spf1 and lists every source that is allowed to send mail for the domain: the company's own mail servers, a marketing platform, a ticketing tool, a payment provider and so on.

When a message arrives, the receiving server looks at the domain used in the technical "envelope sender" (the Return-Path address), fetches that domain's SPF record and checks whether the connecting server's IP address is authorised. The result is usually pass, fail, softfail, neutral or none.

SPF has an important limitation. It checks the envelope sender, not the "From" address that people see in their inbox. A criminal can pass SPF on a domain they own while showing your brand name in the visible "From" line. That gap is why SPF is meant to be used together with DKIM and DMARC, which ties the visible address to the authentication results.

How an SPF Record Works

A simple SPF record looks like this:

v=spf1 ip4:203.0.113.10 include:_spf.mailprovider.example ~all

Each part has a job:

  • ip4 / ip6: authorises a specific IP address or range.
  • include: authorises the servers of a third-party sender, such as an email service provider.
  • a / mx: authorises the servers behind the domain's own address or mail records.
  • all with a qualifier: says what to do with everything else. -all means fail, ~all means softfail (treat as suspicious), ?all means neutral.

Common SPF Problems

  • The 10 lookup limit. An SPF check may trigger no more than 10 DNS lookups. Many "include" entries from different vendors push a record over the limit, and the result becomes an error instead of a pass.
  • Forwarding. When a message is forwarded, it comes from the forwarder's server, which is not in your record, so SPF can fail even for legitimate mail.
  • Forgotten senders. A tool added by another team that sends email in your name but is missing from the record.
  • Multiple SPF records. A domain must publish only one SPF record. Two records cause a permanent error.
  • Unused domains. Domains that never send email, including defensive registrations and parked domains, are still abused by spoofers unless they publish v=spf1 -all.

Why It Matters for Brands

Without SPF, anyone can send a message that uses your domain in the technical sender fields, and many receivers have no way to tell it apart from the real thing. The consequences are familiar:

  • Phishing and fraud. Customers receive fake order confirmations, refund requests or invoices that appear to come from your domain. See Email Spoofing and Phishing.
  • Lost trust. Customers who are deceived once often blame the brand, not the criminal.
  • Deliverability. Major mailbox providers increasingly expect authentication from senders. Missing or broken SPF can send legitimate campaigns to spam.
  • Business email compromise. Spoofed executive or supplier addresses are a tool in Business Email Compromise (BEC).

How to Set Up and Maintain SPF

  1. Inventory every system that sends email for each domain you own: corporate mail, newsletters, CRM, support desk, billing, website forms.
  2. Publish a single SPF record per domain that includes all of them, using the fewest "include" entries possible.
  3. Start with ~all, then move to -all once reports show that all legitimate sources pass.
  4. Stay under 10 lookups. Remove vendors you no longer use and avoid nested includes where you can.
  5. Protect non-sending domains with a record that authorises nothing.
  6. Add DKIM and DMARC. SPF alone does not stop a spoofed visible "From" address.
  7. Review regularly, especially when a new tool or agency starts sending in your name.
  • DKIM: adds a cryptographic signature to messages so receivers can verify they were not altered.
  • DMARC: builds on SPF and DKIM and tells receivers what to do when checks fail.
  • Email Spoofing: forging a sender address to make a message look legitimate.
  • BIMI: shows a verified brand logo in supporting inboxes once authentication is enforced.
  • Domain Monitoring: watching for new domains that imitate yours.

How Remove.tech Helps

SPF protects the domain you own, but it cannot stop criminals from registering a similar domain and sending mail from there. Remove.tech detects lookalike domains, fake websites and phishing pages that impersonate your brand and sends takedown notices to registrars and hosting providers. That covers the part of the problem that email authentication cannot reach. To see what is already out there, get started.

Get started

Join Remove.tech,like other leading brands.

Or contact us by email: hello@remove.tech