Skip to content
Email basics November 4, 2026 · 3 min read · By Smailor Team

Also in FrançaisEspañolDeutsch

What is SPF? The email record explained

SPF (Sender Policy Framework) is a DNS record listing the servers allowed to send mail for your domain. When a message arrives, the receiving server looks at the connecting IP address, fetches your SPF record, and checks whether that IP is on the list.

Nothing in email stops a stranger from claiming to be you. SPF is one of three checks, with DKIM and DMARC, that make such a claim verifiable.

Reading a record

SPF is a TXT record on the domain itself:

v=spf1 ip4:203.0.113.10 include:_spf.mailprovider.com ~all
  • v=spf1 says this is an SPF record.
  • ip4:203.0.113.10 allows that address.
  • include:_spf.mailprovider.com allows everything that provider's own SPF allows.
  • ~all says what to do with everything else.

What the ending means

Ending Name Meaning
-all Fail Nothing else may send. Refuse or mark it.
~all Softfail Probably not us, accept with suspicion.
?all Neutral No opinion, which protects nothing.
+all Pass Anyone may send. Never use this.

~all is the safe default for most domains. With DMARC in place, the difference between ~all and -all matters less, because DMARC decides what happens on failure.

The limits that catch people out

One record per domain. Two records beginning with v=spf1 make SPF fail with a permanent error. When you add a new sending service, merge its include into the existing record. Do not create a second one.

Ten DNS lookups at most. Each include, a, mx, exists and redirect costs a lookup, including the ones nested inside the includes. Past ten, SPF returns permerror and stops protecting you. Every tool you connect (newsletter, invoices, CRM) tends to add one, so the limit arrives faster than expected. Remove the services you stopped using first.

SPF checks the envelope, not the visible From. It validates the Return-Path, the bounce address used between servers. A message can pass SPF for another domain while displaying your name, and only DMARC closes that gap.

Forwarding breaks it. A forwarded message arrives from the forwarder's IP, which is not on your list. This is normal, and it is why DKIM exists alongside SPF.

Frequently asked questions

Is SPF required?

In practice yes. Gmail and Yahoo require SPF or DKIM from every sender, and both from anyone sending more than 5,000 messages a day to their users. Without it, expect spam folders or refusals.

How do I check my SPF record?

Run dig example.com TXT, or the SPF record check, which also counts your lookups. No account is needed.

Do I need SPF if my domain never sends mail?

Publishing v=spf1 -all is a good idea. It tells every receiver that any mail claiming to come from that domain is fake.

Does SPF stop phishing?

Only partly. Without DMARC, it does not protect the From address that people actually read. See how spoofing works.

When you add your domain, Smailor shows the SPF value to publish and, if you already have a record, the include to add inside it instead of creating a second one.