SPF Record Checker
Check a domain’s SPF record. Every include is followed and every DNS lookup counted, and each problem comes with the fix.
- Live DNS lookup
- Results in seconds
- No sign-up
- Free
What the SPF check looks at
Syntax and duplicates
One record only, valid mechanisms, and no stray quote marks.
Every include, followed
The whole tree of included records, with each one’s own lookups.
The 10-lookup limit
A running count, with a warning before you reach the limit.
Advertisement
How SPF works
When a server receives an email, it looks at the domain in the message’s return path (the “envelope from”, which is usually your domain or your email service’s) and fetches that domain’s SPF record. If the sending server’s IP address is on the list, SPF passes. If not, the “all” at the end of the record says what to report: fail, soft fail or neutral.
SPF alone doesn’t decide what happens to a message. DMARC does that, using the SPF and DKIM results. That’s why SPF needs to be right and line up with the domain people see in the From address. See SPF, DKIM and DMARC explained.
The parts of a record
| Term | Means | Lookups |
|---|---|---|
include:domain | Also allow the servers in that domain’s SPF record | 1, plus its own |
ip4: / ip6: | Allow an address or range | 0 |
a / mx | Allow the domain’s own web or mail server addresses | 1 each |
exists, ptr | Rarely used; ptr is deprecated | 1 each |
redirect=domain | Use another domain’s record instead | 1 |
~all / -all | Everything else soft fails / fails | 0 |
Includes for common email services
Add one include for every service that sends email with your domain in the return path. A
typical record for Google Workspace plus a newsletter service looks like v=spf1 include:_spf.google.com include:sendgrid.net ~all. Check your provider’s
own setup page too; some services send through their own domain and need no include at all.
| Service | Include |
|---|---|
| Google Workspace | include:_spf.google.com |
| Microsoft 365 | include:spf.protection.outlook.com |
| Zoho Mail | include:zohomail.com |
| Proton Mail | include:_spf.protonmail.ch |
| Fastmail | include:spf.messagingengine.com |
| SendGrid | include:sendgrid.net |
| Mailgun | include:mailgun.org |
| Brevo | include:spf.brevo.com |
| Zendesk | include:mail.zendesk.com |
Fixing the common problems
- Over 10 lookups: remove services you no longer use, replace
aandmxwith theip4ranges they stand for, or move bulk mail to a subdomain with its own record. Full walk-through: fixing too many DNS lookups. - Two SPF records: merge them into one: a single
v=spf1, every include from both, and one~allat the end. - Malformed record: DNS panels sometimes store quote marks or spaces as part
of the value. The record must start exactly with
v=spf1.
Frequently asked questions
What is an SPF record?
A TXT record at your domain that lists the servers allowed to send email for it. Receiving mail servers check the sending server against the list. It starts with v=spf1, lists mechanisms such as include:, ip4: and a, and ends with an “all” that says what to do with everything else.
What does “too many DNS lookups” mean?
SPF limits a full check to 10 DNS lookups. Every include, a, mx, ptr, exists and redirect costs one, and so does every one inside the records you include. Past 10, SPF fails for every message, even from servers you listed. This checker follows every include and counts them for you.
Should I use ~all or -all?
Either is fine once DMARC is in place, because DMARC decides what happens to failing mail. ~all (soft fail) is the more common choice and is what Google and Microsoft suggest. -all (fail) is stricter. Never use +all, which lets any server send as you.
Can I have two SPF records?
No. A domain may publish exactly one TXT record starting with v=spf1. Two or more make SPF fail with a permanent error. When you add a new email service, add its include to your existing record instead of creating another.
Do subdomains need their own SPF record?
Yes, if they send mail. SPF isn’t inherited: mail from news.example.com is checked against news.example.com’s own record. A subdomain that never sends mail can publish v=spf1 -all to stop it being spoofed.
How long until a change shows up?
The checker asks public resolvers, which may keep the old record until its TTL runs out, often an hour. Our own cache lasts 30 seconds. If you just changed it, check the DNS propagation checker for TXT records.
Did this tool do what you needed?
Related tools
All toolsDMARC Record Checker
Read a domain’s DMARC policy in plain words and see what to change before tightening it.
DKIM Record Checker
Find DKIM keys under common selectors, or check your own, with key size and problems.
Email Domain Health Check
SPF, DKIM, DMARC and MX checked together, with a score and a list of fixes.