Sender Policy Framework SPF
A DNS record for your domain listing the servers and tools allowed to send email in your name.
In Arabic إطار سياسة المرسل SPF
What is Sender Policy Framework?
Sender Policy Framework (SPF) is a text record in your domain's DNS settings listing the servers and tools allowed to send email for that domain. When an email arrives, the recipient's mailbox provider checks this record to see whether it came from an authorized source. It is one of the first email authentication steps, set once and updated when you add a sending tool.
SPF checks only the sending source. It does not protect content or prove an email is safe, so it is used with DKIM and DMARC. A domain has only one SPF record, which you edit by adding tools to it, not by creating a second record, since two records invalidate each other. The record also has a technical lookup limit that many tools can exceed.
Why does Sender Policy Framework matter in business?
An email from a tool not listed in your record may be treated as spoofed, landing in spam or getting rejected.
- 01
Before enabling any new sending tool
A new newsletter tool or support system must be added to the record before its first email, or its messages suffer from day one.
- 02
Diagnosing emails landing in spam
When emails from one source only land in spam, checking SPF often shows that source is not listed.
- 03
Reducing spoofing of your domain
Together with DMARC, SPF helps mailbox providers reject emails that fraudsters send in your domain's name.
Worked example
- 1Situation
A shoe store in Dammam sends email from three sources: its store system, a newsletter tool and a customer service system.
- 2Data
The store opens its domain's SPF record and finds only two sources listed, while emails from the third source land in spam.
- 3Calculation
Sending sources are 3 and listed sources are 2, so 3 - 2 = 1is missing: the customer service system.
- 4Decision
The store adds the third source to its existing SPF record without creating a second one, then sends a test email and checks the result.
Common mistakes
Creating a second SPF record
Adding a new record for each tool makes the check fail. Merge all sources into one record with an include for each tool.
Forgetting an existing sending tool
Your store or invoicing system sends email too. List every tool that sends in your domain's name before writing the record.
Relying on SPF alone
SPF alone does not meet major mailbox provider requirements or stop all spoofing. Add DKIM and DMARC alongside it.
Frequently asked questions
How do I check my domain's SPF record?
Use free tools like MXToolbox by entering your domain, or open your DNS settings at your domain provider and look for a TXT record starting with v=spf1. Then send a test email and check its headers for the SPF result.
What is the difference between SPF, DKIM and DMARC?
SPF sets who may send in your domain's name. DKIM adds a digital signature proving the email was not altered and came from your domain. DMARC tells mailbox providers what to do with emails that fail those checks, and sends you reports.
What do ~all and -all mean at the end of the record?
They set how emails from unlisted sources are treated. ~all means soft fail, usually accepted but flagged. -all means hard fail and rejection. Start with soft fail until you confirm every tool is listed, then decide alongside your DMARC setup.
Takteek services that help here
When setting up marketing email, we list every sending tool with the client, merge them into one SPF record and test before the first campaign.
Talk to Takteek
Want to put this to work for your business?
Tell us about your business in four steps and we will come back with a clear plan that starts from your current numbers. The consultation is free.
- A plan built on your numbers
- One team for ads, content and store
- Free consultation, no commitment


