Type a domain to see its SPF record, check that it is valid, count its DNS lookups against the limit of 10, and see what to fix.
Free, no account needed.
How to use it
SPF (Sender Policy Framework) is a TXT record on your domain that starts with v=spf1 and lists the servers allowed to send mail for it. A receiving server compares the server a message came from with that list.
SPF checks the hidden return address (the envelope sender), not the From line people see. That is why it protects your brand only together with DMARC, which ties the result to the From domain.
A record such as v=spf1 include:_spf.google.com ip4:203.0.113.5 ~all is read from left to right:
Each include, a, mx, ptr, exists and redirect makes the receiver run a DNS lookup, and includes inside includes count too. SPF allows 10 in total. A record that needs more fails with a permanent error, and receivers treat the domain as having no valid SPF at all. The checker follows every include and counts them for you.
To get under the limit, remove services you no longer use, drop a and mx when those servers do not send mail, or replace an include with the ip4 ranges it lists, and keep those up to date.
Most broken SPF records come down to a few slips:
Both protect you once DMARC is enforced. -all asks receivers to refuse unlisted senders and ~all asks them to accept but mark the mail. Many domains use ~all while they confirm every sender, then move to -all.
No. More than one v=spf1 record is a permanent error, and SPF fails. Put every include and address into a single record.
SPF returns a permanent error, so mail from your domain can fail SPF everywhere. Remove includes you do not need, or replace some with the addresses they stand for.
No. SPF checks the hidden return address, not the From line people see. Pair it with DKIM and a DMARC policy of quarantine or reject.
Yes. The email authentication check API returns the SPF, DMARC, DKIM and MX results, the grade and the fixes as JSON for any domain.
Get a key and make your first call in minutes.