Free tool
SPF record checker
Fetch a domain's SPF record, resolve every include, and count DNS lookups against the limit of 10. Free, no signup.
Results for
shipmail.to
Looks good
SPF record looks good
4 of 10 DNS lookups are used.
OK
SPF record
v=spf1 mx include:amazonses.com include:spf.shipmail.to -all
DNS lookups used: 4 of 10 allowed.
Adding a sender or starting over? Build a new record with the free SPF record generator
SPF checks who can send. To check where incoming email goes, use the free MX record check
What SPF does
SPF (Sender Policy Framework) is a TXT record on your domain that lists the servers allowed to send email as you. When a mail server receives a message claiming to come from your domain, it checks the sending server against that list. Mail from a server that is not on the list fails SPF, which hurts deliverability and, combined with DMARC, gets spoofed mail rejected outright.
A domain without SPF is easy to impersonate, and legitimate mail from it is more likely to land in spam. Every domain that sends email should have exactly one SPF record.
The 10 lookup limit
SPF allows at most 10 DNS lookups per check. Every include, a, mx, exists, ptr, and redirect in your record costs one lookup, and includes pull in the lookups of the records they reference. Add a few providers (Google, a marketing platform, a helpdesk, a CRM) and you can pass 10 without noticing.
Past the limit, receivers return a permanent error and may treat your mail as if SPF did not exist. This checker resolves your includes recursively and counts the total.
How to fix a failing record
One record only. If you have two SPF records, merge them into a single v=spf1 string, since receivers treat multiple records as a permanent error.
Over the lookup limit, remove includes for services you no longer use, or replace rarely-used includes with their ip4 and ip6 ranges, which cost no lookups.
End the record with ~all (softfail) or -all (fail). A record ending in +all allows anyone to send as your domain and ?all gives receivers no signal at all.
SPF record examples
Google Workspace only: v=spf1 include:_spf.google.com ~all
Microsoft 365 only: v=spf1 include:spf.protection.outlook.com -all
Two services during a move from Google Workspace to Microsoft 365: v=spf1 include:_spf.google.com include:spf.protection.outlook.com -all
A domain that sends no mail at all, such as a parked domain: v=spf1 -all
What does a valid SPF record look like?
A single TXT record on the domain root starting with v=spf1, followed by the mechanisms that allow your senders, ending with ~all or -all. For example: v=spf1 include:spf.shipmail.to ~all.
Why can I only have one SPF record?
The SPF specification (RFC 7208) requires receivers to treat multiple v=spf1 records as a permanent error, so a second record does not add senders, it breaks SPF entirely. Merge all mechanisms into one record.
Should I use ~all or -all?
-all tells receivers to fail mail from unlisted servers, ~all marks it suspicious but deliverable. Start with ~all while you confirm every legitimate sender is listed, then consider -all. Never use +all.
Does SPF stop spoofing on its own?
No. SPF checks the envelope sender, not the From header people see, and forwarding can break it. You need DKIM and a DMARC policy on top of SPF for real spoofing protection.
Email, newsletters and booking pages on your own domain, in one plan.
Get started for free