This free SPF checker reads your record and shows how to fix it.
We count your DNS lookups against the limit of 10, explain every part of the record in plain English and hand you the corrected record to paste. Free, with no signup.
Works with a domain or a full email address. We read DNS fresh on every run.
3 of 5 checks pass. Fix SPF first: until SPF passes, this domain falls short of the rules Gmail, Yahoo and Outlook set for bulk senders.
Receivers read exactly one SPF record. When they find more, they stop and return a permanent error (RFC 7208), which counts as no SPF at all.
v=spf1 include:_spf.google.com ~all v=spf1 include:secureserver.net -all
Delete both records and publish this one in their place. Your mail is handled by Google Workspace, so include:secureserver.net, GoDaddy's email service, is left out. Add it back only if you also send mail that way.
v=spf1 include:_spf.google.com ~all
Add it as a TXT record with host @ in your DNS, in place of any SPF record already there. This record uses 1 of the 10 DNS lookups SPF allows.
| include:_spf.google.com | Google Workspace may send for this domain. Costs 1 lookup. |
| ~all | Mail from any other server is marked as suspicious (soft fail). Use -all to have it fail outright. |
Once your records pass, warm up the mailbox and start sending with Emailchaser.
Emailchaser warms up each mailbox on its own, then sends your campaign and its follow-ups from the domain you just checked.
The check runs on our server against live DNS and 16 public blocklists (3 for domains, 13 for mail server IPs). A list that does not answer is never counted as clean. Nothing you type is stored.
Each SPF result means one thing, and each has one fix.
The checker gives one line for your record. Find that line below to see what receivers do with it and what to change. When you run a check, the row that matches your result is marked.
| What the checker shows | What it means | What to do |
|---|---|---|
| One valid SPF record, using a few of the 10 DNS lookups | Receivers can read the record, and mail from the servers it lists passes SPF. | Nothing to fix. Run the check again each time you add a sending service. |
| Needs more than 10 DNS lookups | Receivers stop at 10 and return a permanent error, so SPF fails for every message from the domain. | Remove includes for services you no longer use. Flatten the rest only if you must. |
| More than one SPF recordYour result in the example | Receivers return a permanent error when they find two, which counts as no SPF at all. | Delete the extra record and publish the single merged record the report writes for you. |
| No SPF record found | Receivers have nothing to check, and Gmail, Yahoo and Outlook expect SPF from bulk senders. | Publish one TXT record at the root of the domain. Copy the one in the report. |
| Ends in +all, ?all or has no all term | Receivers either let every server pass, or reach no verdict on servers you did not list. | End the record with ~all, or -all once you are sure every sender is listed. |
| A term or include that does not work | One part receivers cannot read or follow breaks the whole record. | Correct or remove the part the report names. It is usually a typo or a service you stopped using. |
| Your mailbox provider is not listed | Mail you send from your own mailboxes fails SPF at the provider. | Add the include the report shows for your provider. |
See where your SPF record sits among 13,511 listed companies.
We read the SPF record of 13,511 listed companies on 18 October 2026. 47.3% end in -all, 40.6% end in ~all, and 3.1% of the 12,231 SPF records need more than 10 DNS lookups, so receivers cannot evaluate them.
How the example domain compares, so you can see what your own result will show.
SPF record
More than one
0.6% of the 13,511 companies publish two or more, which receivers treat as none.
SPF ending on your provider
Google Workspace
21.4% of them end SPF in -all. Across all 13,511 companies it is 47.3%.
- -all, hard fail6,391 domains47.3%
- ~all, soft fail5,487 domains40.6%
- ?all, +all, a redirect or no all term353 domains2.6%
- More than one SPF recordYour domain75 domains0.6%
- No SPF record1,205 domains8.9%
- 0 or 1 lookupsYour domain3,296 records26.9%
- 2 or 3 lookups2,849 records23.3%
- 4 or 5 lookups1,917 records15.7%
- 6 or 7 lookups1,646 records13.5%
- 8 or 9 lookups1,489 records12.2%
- Exactly 10, the limit658 records5.4%
- 11 or more, so SPF fails376 records3.1%
Companies on Microsoft 365 and on Google Workspace set these records differently.
| Where the mail is handled | Domains | End in -all | Over 10 lookups | No SPF record |
|---|---|---|---|---|
| Microsoft 365 | 4,421 | 66.5% | 3.1% | 0.5% |
| Google Workspace | 1,302 | 21.4% | 3.5% | 5.5% |
| A security gateway in front of the mailbox | 2,526 | 46.5% | 4.0% | 0.8% |
| Another host or their own server | 4,108 | 42.2% | 2.5% | 7.5% |
Companies on Microsoft 365 end SPF in -all 66.5% of the time, against 21.4% on Google Workspace, where the setup guide uses ~all. Both endings pass. These are large listed companies, not cold email domains, so read the numbers as the standard the people you email already meet, not as a target for your own setup.
Source: Emailchaser DMARC adoption study, 13,511 company domains with a stock exchange listing, read from public DNS on 18 October 2026. See the full study and its data.
A receiver reads your SPF record in four steps.
SPF is checked on the receiving side, for every message, in well under a second.
The message arrives
The receiver notes the server that delivered it and the domain in the return-path address.
It fetches one TXT record
It looks up the record that starts with v=spf1 at that domain. Two records, and it stops with an error.
It counts lookups
Every include, a, mx, ptr and exists term costs one lookup. Past 10, SPF fails.
It matches the server
If the delivering server is listed, SPF passes. If not, the all term decides.
Publish the record as one TXT record at the root of your domain.
Your DNS provider is wherever your nameservers point: your registrar, Cloudflare or your host.
- Open the DNS settings for the domain.
- Look for a TXT record whose value starts with
v=spf1. If there is one, edit it. Never add a second. - Set the host to
@. Some panels want the domain name itself, or an empty host. For a subdomain such asmail.yourdomain.comthe host ismail. - Paste the record and save. Run the check above again once the old record's TTL has passed, usually between 5 minutes and an hour.
Start from the example that matches how you send.
v=spf1 include:_spf.google.com ~all
v=spf1 include:spf.protection.outlook.com -all
v=spf1 include:_spf.google.com include:amazonses.com ~all
Two includes, two of the 10 lookups. Add one include per service, and keep it all in the same record.
v=spf1 -all
It tells receivers to fail any message that claims to come from the domain.
Gmail, Yahoo and Outlook all list SPF among their requirements for bulk senders. Read the rules from Google, Yahoo and Microsoft.
An SPF record breaks at 11 DNS lookups, even when every line in it is correct.
Each include, a, mx, ptr and exists term makes the receiving server do another DNS lookup, and so do the includes inside those includes. RFC 7208 caps the total at 10. One lookup over, and the whole record returns a permanent error, which Gmail treats as no SPF at all. The tree in the report above counts every lookup for you, nested ones included, and shows which include costs the most.
That is why an SPF record grows until it breaks. Each new tool someone in the company signs up for asks you to add its include: a help desk, a CRM, a newsletter tool, a billing system. Each one looks harmless on its own. The fifth or sixth one pushes the count past 10, and from that moment every message from the domain fails SPF, including the ones from Google Workspace that worked yesterday.
ip4 and ip6 terms cost nothing, because the address is already in the record. That is what "flattening" an SPF record means: replacing includes with the addresses they resolve to. It works until the provider changes its addresses, which is why we suggest removing includes you no longer use before you flatten anything.
Every part of an SPF record has one job.
| Term | What it means | DNS lookups |
|---|---|---|
| v=spf1 | Marks the TXT record as SPF. It must come first. | 0 |
| include:_spf.google.com | Every server the other domain's SPF record allows may send for you. | 1, plus the lookups inside it |
| a | The server at your domain's own address (its A record) may send. | 1 |
| mx | Your own mail servers (your MX records) may send. | 1 |
| ip4:203.0.113.0/24 | Servers in this address range may send. | 0 |
| ip6:2001:db8::/32 | The same for IPv6 addresses. | 0 |
| exists:%{i}.spf.example | Passes when a name built from the message resolves. Rare outside large providers. | 1 |
| ptr | Matches on reverse DNS. RFC 7208 says not to use it. | 1 |
| redirect=_spf.example.com | Use another domain's record in place of this one. Only read when there is no all term. | 1 |
| ~all / -all | What happens to every server not listed: soft fail or fail. | 0 |
A sign in front of a term changes what a match means: + pass (the default), - fail, ~ soft fail and ? neutral. In practice only the all term at the end carries one. A record that ends in +all or plain all passes every server on the internet, and our check fails it.
Some providers' includes cost one lookup, and some cost seven.
We ran each provider's documented include through the checker on its own. The number is the include plus every lookup nested inside it, which is what it costs you out of 10.
| Provider | Include | Lookups it costs |
|---|---|---|
| Google Workspace | include:_spf.google.com | 1 |
| Microsoft 365 | include:spf.protection.outlook.com | 1 |
| Amazon SES | include:amazonses.com | 1 |
| Postmark | include:spf.mtasv.net | 1 |
| Brevo | include:spf.brevo.com | 1 |
| Zendesk | include:mail.zendesk.com | 1 |
| Fastmail | include:spf.messagingengine.com | 1 |
| Mailchimp | include:servers.mcsv.net | 1 |
| SendGrid | include:sendgrid.net | 2 |
| Zoho Mail | include:zohomail.com | 2 |
| Salesforce | include:_spf.salesforce.com | 2 |
| Proton Mail | include:_spf.protonmail.ch | 2 |
| GoDaddy email | include:secureserver.net | 3 |
| Mailgun | include:mailgun.org | 5 |
| Freshdesk | include:email.freshdesk.com | 7 |
Measured on live DNS on 6 October 2026. Providers change their records without notice, so check your own record above rather than adding these up.
Google Workspace and Microsoft 365 cost one lookup each, so a domain that only sends through one of them has nine to spare. The expensive ones are the services that nest includes for several mail systems of their own.
Two SPF records on one domain is the most common way to break SPF.
It usually happens when a domain changes hands between services. The registrar publishes a default record for its own email service, then someone adds Google Workspace's record next to it instead of replacing it. Both look valid on their own, and together they fail: receivers read exactly one SPF record, and when they find two they return a permanent error for every message.
When our check finds more than one, it writes the merged record for you: one v=spf1, every include and address from the old records once, and one all term. If your mail runs on a provider we recognise and one of the old records is a registrar's default include (GoDaddy's secureserver.net, for example), the merged record leaves it out and says so. The report also counts the merged record's lookups before you publish it.
Most broken SPF records fail for one of five reasons.
Every one of these returns a permanent error or lets the wrong servers through, and every one is easy to miss by reading the record by eye, because each term on its own looks fine.
| What we find | What receivers do | The fix |
|---|---|---|
| Two or more SPF records | Return a permanent error, so SPF fails for every message | Merge them into one record; the report writes it for you |
| More than 10 DNS lookups | Return a permanent error once the count passes 10 | Remove includes you no longer use, then flatten the rest if you must |
| An include with no SPF record behind it | Return a permanent error when they reach it | Fix the spelling or remove the include |
| +all | Pass mail from every server on the internet | End the record with ~all or -all |
| No all term at the end | Treat unlisted servers as neutral, neither pass nor fail | Add ~all or -all as the last term |
A sixth problem is quieter: a record longer than 255 characters pasted as one string. DNS stores TXT values in chunks of up to 255 characters, and most DNS panels split a long record for you. If yours does not, it may cut the record off, and the check above will show the record exactly as receivers read it.
SPF passing is not the same as DMARC passing.
SPF checks the domain in the return-path address, the one bounces go to, not the one your recipient sees in From. When you send through a service that uses its own return-path, SPF can pass for that service's domain while doing nothing for yours. DMARC only counts SPF when the two domains match, which is called alignment.
That is why the other four checks run with this one. DKIM signs with your own domain and survives forwarding, so it is the record DMARC leans on most. See your DKIM key on the DKIM checker and your policy on the DMARC checker, or build a new SPF record from scratch with the SPF record generator.
Common questions about SPF records
What is an SPF record?
A TXT record at the root of your domain that lists the servers allowed to send email as your domain. A receiving server looks it up for every message and checks whether the server that delivered it is on the list.
How many SPF records can a domain have?
Exactly one. With two or more, receivers stop and return a permanent error (RFC 7208), which counts as no SPF at all. Merge them into one record that keeps every include you still use.
What is the SPF 10 lookup limit?
Every include, a, mx, ptr and exists term makes the receiving server do a DNS lookup, and so do the terms inside each include. RFC 7208 caps the total at 10. One more and the whole record returns a permanent error. Our checker counts every nested lookup and shows the tree.
Should I use ~all or -all?
Either is fine for cold email. ~all (soft fail) marks mail from unlisted servers as suspicious, -all (hard fail) says it should fail. Gmail, Yahoo and Outlook ask for SPF to pass, not for one ending over the other. Never use +all, which lets anyone send as you.
Does SPF alone stop my emails going to spam?
No. Gmail, Yahoo and Outlook also want DKIM and a DMARC record from anyone sending in bulk, and DMARC needs SPF or DKIM to pass for the same domain as your From address. The check above runs all five.
What is an SPF PermError?
A permanent error: the receiver could not evaluate your record at all, so SPF counts as failed for every message. The usual causes are two SPF records, more than 10 DNS lookups, an include that points at a name with no SPF record, or a typo in a term. Our check names which one it found.
Does a subdomain need its own SPF record?
Yes, if it sends mail. SPF is not inherited: mail.yourdomain.com is checked against its own TXT record, not the root domain's. A subdomain that never sends can publish v=spf1 -all.
How long does an SPF change take to show up?
As long as the TTL on the old record, often between 5 minutes and an hour. Our check reads DNS fresh on every run, so run it again after the change.
How do I check my SPF record?
Type your domain in the checker above and press Check domain. It reads the TXT record that starts with v=spf1, counts the DNS lookups and explains each term. From a terminal, run nslookup -type=txt yourdomain.com on Windows, or dig TXT yourdomain.com +short on Mac and Linux.
What is a good SPF record?
One TXT record at the root of the domain, starting with v=spf1, listing every service that sends as you, using fewer than 10 DNS lookups and ending in ~all or -all. For a domain that sends only through Google Workspace, that is v=spf1 include:_spf.google.com ~all.
Can this tool flatten my SPF record?
It does not flatten. It shows the lookup tree, marks the include that costs the most and, when two records need merging, writes the merged one. Flattening swaps includes for the IP addresses behind them, and providers change those addresses without notice, so remove includes you no longer use first.
How many companies have a broken SPF record?
In our study of 13,511 listed companies, 3.1% of SPF records needed more than 10 DNS lookups, 0.6% of domains published more than one SPF record and 8.9% published none.
Check the rest of your setup with these free tools.
Send cold email from domains that pass all five checks.
Every plan includes warm-up, follow-ups and unlimited email accounts.
Start my free trial7-day free trial, $0 today