What is an SPF record?
An SPF record is a single TXT record on your domain that lists the servers allowed to send email for it, such as v=spf1 include:_spf.google.com ~all for Google Workspace. Receivers compare the server that sent a message with that list. A domain must have only one SPF record, and checking it must take no more than 10 DNS lookups.
How to check and fix your SPF record
Check the record
Enter your domain above. The checker reads your SPF TXT record, says how it ends, and counts the DNS lookups it can see in it.
Make sure there is only one
If the check shows more than one SPF record, merge them. RFC 7208 says a domain must not have multiple SPF records, and receivers treat that as a permanent error.
List every sender
Mailbox provider, newsletter platform, CRM, invoicing tool, website forms and any office server. Each one that sends as your domain needs an
include:orip4:entry.Start from the right example
Take the record below that matches your mail provider, then add your other senders before the
allat the end.Choose how it ends
Google's record ends in
~all. Microsoft recommends-allfor Microsoft 365 domains that also have DKIM and DMARC. Never end in+all.Count the lookups
include, a, mx, ptr, exists and redirect each count; ip4, ip6 and all do not. Nested includes count too. Stay at 10 or fewer.
Publish, then wait
Replace the old TXT record with the new one at your DNS host. Google says SPF can take up to 48 hours to start working.
Check again
Run the next check on the full email checker page, and confirm DKIM and DMARC there at the same time.
SPF record examples
Copy the line that matches your setup, then add any other sender before the ending.
| Setup | Record | Notes |
|---|---|---|
| Google Workspace only | v=spf1 include:_spf.google.com ~all | Google's own record |
| Google Workspace and Amazon SES | v=spf1 include:_spf.google.com include:amazonses.com ~all | Google's example of a second sender |
| Microsoft 365 only | v=spf1 include:spf.protection.outlook.com -all | Microsoft's record for its commercial cloud |
| Microsoft 365 and an office mail server | v=spf1 ip4:192.168.0.10 include:spf.protection.outlook.com -all | Microsoft's example; use your server's public IP address |
| A marketing subdomain | v=spf1 include:sender.example include:spf.protection.outlook.com -all | Published on marketing.yourdomain; each sending subdomain needs its own record |
| A domain that sends no mail | v=spf1 -all | Microsoft's record for parked domains |
Records from Google Workspace Admin Help and Microsoft Learn. sender.example stands for the include value your sending service gives you.
How the ending changes the result
| Ending | Result for servers not listed | When to use it |
|---|---|---|
| -all | Fail | Microsoft recommends it for Microsoft 365 domains with DKIM and DMARC in place |
| ~all | Softfail | Used in Google's record; a common choice while you confirm every sender |
| ?all | Neutral | Testing only; Microsoft does not recommend it in production |
| +all | Pass, for any server at all | Never: it lets anyone send as you |
Microsoft notes that DMARC treats both -all and ~all as SPF failures.
The SPF checklist
- Exactly one TXT record on the domain starts with v=spf1
- Every service that sends as your domain is listed
- Services you no longer use have been removed
- The record ends in ~all or -all, never +all
- No ptr mechanism, which RFC 7208 says should not be published
- 10 DNS lookups or fewer, with nested includes counted
- Each subdomain that sends mail has its own SPF record
- Parked domains carry v=spf1 -all
- The record is published as TXT, the only type RFC 7208 allows
- Long records are split into strings of 255 characters or fewer
- DKIM and DMARC are set up too; SPF is one record of three, not the whole job
Who uses this guide
IT leads
Audit SPF on every domain and subdomain the business owns, and remove senders nobody uses any more.
Developers
Add the include for a new transactional email service before the first password reset or receipt goes out.
Office managers
Check SPF after changing mail provider, when an old record is easy to leave behind.
Marketing teams
Before connecting a new newsletter or CRM tool, check how many lookups the record has left.
Freelancers on their own domain
Get the single Google or Microsoft record right on the first day.
Managed IT providers
Spot duplicate SPF records on client domains in seconds and send the merged record.
Worked examples
Two records after a migration
Suppose the check shows v=spf1 include:_spf.google.com ~all and a second record left by your old host. Both are now invalid. Delete the old one, or fold any sender you still use into the Google record as one more include.
Twelve lookups
Suppose your record has eight includes, an a and an mx, and two of those includes hold includes of their own. That is twelve lookups, over the limit, so SPF fails with a permanent error. The checker counts the ten it can see in your own record, which puts you at the limit; the two nested ones push you over. Remove senders you no longer use, and replace a and mx with ip4 entries where the addresses are stable.
Microsoft 365 ending in ~all with no DKIM
Suppose your Microsoft 365 domain ends in ~all and has no DKIM. Microsoft notes that the DMARC policy is effectively ignored for ~all failures when the message carries no DKIM signature. Turn on DKIM, then move to -all as Microsoft recommends.
What changes in 2027 for SPF
Now
- RFC 7208 (2014) is still the SPF standard: one record per domain, published as TXT, with at most 10 terms that trigger DNS lookups.
- Google's record for Workspace still ends in ~all, while Microsoft recommends -all for Microsoft 365 domains with DKIM and DMARC.
- Microsoft counts include, a, mx, exists and redirect towards the limit, and notes that ip4, ip6 and all do not count.
Next
- AdEngage UAE expects growing businesses to add more sending tools in 2027, from CRMs to booking systems, so the 10 lookup limit will bite more often. Decide which senders really need SPF.
- Move bulk senders to their own subdomain, as Microsoft's example does with a marketing subdomain, so the main record stays short.
- Review SPF every quarter and after every new tool, because a record that was right last year may still list senders you have dropped.