Free tool

Check your domain's SPF record

Enter your domain: our SPF checker reads your SPF record, counts its DNS lookups and makes sure the domains it relies on actually exist. Results explained, and a corrected SPF record to copy when it needs to change.

No sign-up. Your domain is neither stored nor published.

What this SPF check looks at

SPF is a TXT record published on your domain that starts with v=spf1. It lists the servers allowed to send email on your behalf, often with include: entries pointing to your mailbox provider or your sending tools. The check confirms there is only one SPF record, that it ends with a clear rule (-all or ~all, never +all), and that it doesn't need more than 10 DNS lookups, the limit set by the standard: beyond that, mail providers treat it as broken. Using the domain registry, it also confirms that the domains named in your SPF record and your mail servers are actually registered: an included domain that has expired can be bought by anyone, who could then send "authorized" email in your name.

How to read the result

"In order": your SPF record is unique, readable and ends with a strict rule. An SPF record that is missing, ends with +all or ?all, or goes over the lookup limit protects nothing: if DMARC is missing too, the result flags that your domain can be spoofed. An included domain that is available to buy is reported separately, with the number of domains involved. "Could not be checked" means a temporary DNS or registry outage, never a problem on your side.

The most common SPF mistakes

  • Two SPF records published after switching email providers: there must be only one, covering every service.
  • Too many include: entries added tool after tool, until the DNS lookup limit is exceeded.
  • A record ending in +all, which allows the whole world to send email in your name.
  • An include: pointing to a former provider whose domain no longer exists.

The fix, step by step

List the services that send email with your address: mailbox, website, invoicing, newsletter, support desk. Combine them into a single SPF record, remove the services you no longer use, and end it with ~all while you check, then with -all. If you go over the lookup limit, replace an include: with the service's IP addresses when it publishes them, or move your newsletters to a subdomain. The result above suggests the merged SPF record when we can write it, ready to paste.

Frequently asked questions

Is SPF enough to stop people from spoofing my address?

No. SPF checks the technical sender address, which your customers never see. DMARC is what ties SPF to the visible address, so check it too.

~all or -all?

Both are recognized strict endings. ~all marks unauthorized messages as suspicious, -all asks providers to reject them. With DMARC in place the difference matters little; without DMARC, -all protects more.

Why is my provider telling me to add an include?

Because its servers send email on your behalf. Add it to your existing SPF record instead of creating a second one.