What an SPF record does
SPF is a single TXT record at the root of your domain that lists the servers allowed
to send email as your domain. A receiving mail server reads it when a message arrives, checks whether the
sending server is on the list, and passes the result on to DMARC. The record starts
with v=spf1, lists senders as include:, ip4:, ip6:, a or mx terms, and ends by saying what to
do with everyone else, usually ~all or -all.
This page runs the full email check and shows the SPF section first, with its own verdict, so you can see the record, its lookup count and its include tree at a glance. The rest of the email setup follows below it, because SPF on its own decides little: DMARC decides what happens to mail that fails.
The three ways SPF breaks
Most SPF problems come down to three mistakes, and each one makes receivers stop with an error, which counts as a fail for all your mail.
Too many lookups. Receivers allow 10 DNS lookups per check. Every include, a, mx, ptr, exists
and redirect costs one, and so do the terms inside the records you include. Adding a newsletter tool or a
help desk is often what pushes a record over the edge. We count exactly as receivers do, show a meter
against the limit and list every include in a tree, so you can see which service costs the most.
More than one record. A domain may publish only one v=spf1 record. A second one, often added by a
service's setup guide, makes receivers give up on both.
A broken include. An include that points at a name with no SPF record, a typo, or a provider's old include name breaks the whole record. We follow every include, and void lookups (names that turn out to have nothing there) are counted too, since more than two of those is also an error.
Endings and what they mean
-allrejects mail from servers that aren't listed. It is the strongest setting once your list is complete.~allmarks such mail as suspicious. It is the safe place to start, and with an enforcing DMARC policy it is all you need.?allsays nothing either way and protects nothing.+all, or a bareall, lets every server on the internet send as your domain. It is worse than having no record.
What else we check
We flag the ptr mechanism, which the standard says not to use, IP ranges so wide they include other
people's servers, and macros that make a record hard to check. Each problem comes with a step-by-step
guide for the common DNS hosts.
Reading the result
The SPF section opens with a one-line verdict in plain words, then shows the record with a copy button, the lookup count on a meter against the limit of 10, and the include tree, folded away until you open it. Each term in the tree says whether it cost a lookup and how it ended: found, nothing there, failed to answer, or not looked up because it depends on the sender. Problems are listed under the whole result as findings, worst first, each with a short fix and a link to a step-by-step guide.
When a lookup fails, the result is marked partial and says which part couldn't be read. We never report a record as missing just because a server was slow to answer.
Changing your record
Use Check and edit this record in the SPF builder under the result. It opens the SPF builder with your current record filled in, so you can try a change and see the new lookup count before you touch your DNS. The builder also writes a new record from a list of your mail services if you'd rather start fresh.
After you publish a change, run this check again once the old record's TTL has passed, usually within an hour.