Enter your domain to see your SPF record, whether it’s valid, and how many of the 10 allowed DNS lookups it uses.
Free, no sign-up. Checks SPF, DKIM, DMARC, mail servers and blacklists in one go.
What SPF does
SPF (Sender Policy Framework) is a list of the servers allowed to send email for your domain. When a message arrives claiming to be from you, the receiving mail system looks up that list and checks whether the message came from one of them.
An SPF record is a TXT record on your main domain. A typical one for a business on Google Workspace looks like this:
v=spf1 include:_spf.google.com ~all
Reading your result
| What you see | What it means |
|---|---|
| Valid, under 10 lookups | Your record works. Check that every service that sends as you is listed. |
| No SPF record | Mail systems can’t tell which servers are yours. Real email is more likely to land in spam, and forgeries are easier. |
| Multiple SPF records | Your domain has two or more records starting with v=spf1. That’s an error, and mail systems treat SPF as failed. See how to fix multiple SPF records. |
| Too many DNS lookups | The record needs more than 10 lookups to evaluate, so SPF fails for every message. |
Ends in +all or ?all | The record allows any server, or takes no position, so it protects nothing. |
The parts of an SPF record
v=spf1starts every SPF record.include:adds another company’s list of servers, such as your email provider or newsletter tool. Each include costs at least one DNS lookup.aandmxallow the servers your domain’s web address and mail records point to. Each costs a lookup.ip4:andip6:list specific server addresses. These cost no lookups.- The ending sets the rule for everything else:
-all(fail),~all(soft fail, the most common),?all(neutral) or+all(pass everything, which you should never use).
The 10-lookup limit
The SPF standard caps a record at 10 DNS lookups, counting every include, a, mx, exists and redirect, including the ones nested inside each include. Go over and SPF returns an error for every message. It’s a common problem for businesses that have added a CRM, a newsletter, an invoicing tool and a help desk over the years. The checker counts lookups for you.
To get back under the limit, remove includes for services you no longer use first. If you still need them all, an IT provider can flatten some includes into fixed ip4: entries, though those need upkeep when the provider’s addresses change.
Common SPF records by provider
| Email provider | Include to add |
|---|---|
| Google Workspace | include:_spf.google.com |
| Microsoft 365 | include:spf.protection.outlook.com |
| Zoho Mail (US) | include:zohomail.com |
| GoDaddy email | include:secureserver.net |
Each newsletter, CRM or invoicing tool that sends as your domain publishes its own include in its setup instructions. Combine them all into one record, before the ending. Our guides walk through it for Google Workspace, Microsoft 365, Zoho Mail and GoDaddy.
Common questions
Should my SPF record end in ~all or -all?
Either works with DMARC. -all is stricter and is what Microsoft recommends. ~all is a reasonable choice while you’re still confirming every service that sends as you. What protects you from spoofing is DMARC; check yours with our DMARC checker.
Does SPF alone stop people from spoofing my domain?
No. SPF checks a technical sender address that recipients never see, not the “From” address in their inbox. DMARC is what connects the two and tells mail systems to block forgeries.
Can I have one SPF record for my domain and another for a subdomain?
Yes. Each domain and subdomain gets its own single record. The one-record rule applies per name.
Records break without anyone noticing
A website move, a new email tool or a DNS change can quietly undo this setup. MailWatchman checks your domain every day and emails you the moment something changes, with the fix. Plans start at $6 a month.