Skip to content
// free tool

SPF record checker

Your SPF record is a public list of the servers allowed to send email for your domain. Mail providers check it when a message arrives. If it's missing, duplicated or too relaxed, fake email in your name is more likely to land in your customers' inboxes. This tool reads your SPF record and tells you, in plain English, whether it's doing its job.
// sample result
odesstra ~ $ check yourbusiness.co.za
[email]SPF ok · DMARC p=nonewarn
done in 6.2s · nothing attacked
// what it checks

What we look at

  • Does a record exist? We look for a TXT record on your domain starting with v=spf1.
  • Is there only one? Two SPF records is an error, and mail providers may ignore both.
  • How does it end? -all (reject others) is strongest, ~all (soft fail) is common and acceptable with DMARC, ?all and +all give no protection.
  • How many lookups? Each include:, a, mx, exists and redirect costs a DNS lookup. SPF allows ten; going over breaks the record. We count the ones at the top level.
// reading your results

Good and not-so-good records

A tidy SPF record
example.com  TXT  "v=spf1 include:_spf.google.com include:mailgun.org -all"

// hacker view

[spf] v=spf1 include:_spf.google.com +all fail

// plain english

Your email list says “anyone may send as us”. The +all at the end cancels the rest of the record. Change it to ~all or -all.

If your domain doesn't send email at all, the best SPF record is a short one that says so: v=spf1 -all. Pair it with a DMARC p=reject record and nobody can convincingly send as you.

// limits

What this check does not do

It makes public DNS lookups only. It doesn't follow every include: down the chain, so the lookup count is a minimum, not the final total. It doesn't send test mail and can't tell you whether your real email passes SPF; your DMARC reports show that. And SPF alone can't stop email spoofing of the “From” address your customers see. That's DMARC's job.

// how to fix

Fixing common SPF problems

  • Two records: merge them into one, combining the include: entries.
  • Too many lookups: remove services you no longer use, and replace a or mx with the exact addresses where it's safe to do so. Our guide to fixing SPF "too many DNS lookups" walks through it.
  • `+all` or `?all`: change to ~all while you check, then -all once you're sure every sender is listed.
  • No record: list your mailbox provider and any tool that sends as you, such as your newsletter, shop or invoicing system.

Read what is DMARC, and does my small business need it? to see how SPF fits into the bigger picture.

// questions

Common questions

I use several email services. How do I list them all?

Put them in one SPF record, each as its own include: entry, for example v=spf1 include:_spf.google.com include:sendgrid.net ~all. Each provider publishes the exact include to use in its help pages. Don't create a second SPF record for the new service: two records cancel each other out, and mail servers then treat your domain as if it had no SPF at all. If the list grows long, watch the ten-lookup limit our checker reports.

My website's contact form emails go to spam. Is SPF the reason?

Often, yes. Contact forms usually send through your web host's server, which isn't listed in your SPF record, so the message fails the check. The cleanest fix is to send form emails through your normal email provider or a dedicated sending service, then make sure that service is in your SPF record and signs with DKIM. Your developer or host can set this up, or we can do it for you.

Is SPF enough on its own?

No. SPF checks the hidden envelope sender, not the 'From' address people see, so a scammer can still pass SPF using their own domain while displaying yours. DMARC closes that gap by insisting the visible address matches. Use SPF, DKIM and DMARC together; our DMARC checker looks at all of it.

Should my SPF record end in -all or ~all?

-all is stricter. ~all is fine when you also have a DMARC policy of quarantine or reject, because DMARC makes the final decision. Never use +all.

Can I have two SPF records?

No. Two v=spf1 records on the same domain is an error and can make mail providers ignore SPF entirely. Merge them into one.

How do I fix SPF "too many DNS lookups" (PermError)?

Mail providers stop after ten DNS lookups while checking your record, and each include: can add several of its own. Remove unused services first, then drop redundant a and mx entries. See how to fix SPF PermError.

Do I need SPF if I don't send email?

Yes, a simple v=spf1 -all record tells everyone that no server is allowed to send mail as you. It's a one-line change.

Talk to a human