Free migration and setup with every plan. We move your old email for you. Learn more

SPF Lookup

Check your domain's email settings for free.

Shows which servers may send email on behalf of your domain.

Lookups are coming soon. The guide below explains what the record should look like.

What is an SPF record?

SPF (Sender Policy Framework) is the list of servers you allow to send email on behalf of your domain. It is published as a TXT record in your domain's DNS, where anyone can read it.

When someone sends a message from your address, the receiving server looks at the IP address it came from and checks whether that address is on your SPF list. If it is not, the message is treated as suspicious; most of the time it goes to spam, and sometimes it is refused outright.

SPF is not a set-and-forget record. The contact form on your website, your newsletter tool, the invoices your accounting software sends: all of them send mail in your name, and each one has to be on the list.

How to read the result

  • v=spf1: Marks the record as SPF. It always comes first.
  • include: Adds another service's SPF list to yours. Your email provider or newsletter tool usually gives you this value.
  • ip4: / ip6: Allows a single address or a range of addresses.
  • a and mx: Allow the servers in your domain's own A and MX records.
  • ~all: Servers not on the list are marked as suspicious (softfail). The safest choice until you are sure every sender is listed.
  • -all: Messages from servers not on the list should be rejected (fail).

The tool splits the record into its rules and counts the DNS lookups. SPF allows at most 10; every include, a or mx rule uses one. Go over the limit and the whole record is treated as invalid, so receivers apply none of your rules.

SPF record example

v=spf1 include:_spf.example.com ip4:203.0.113.10 ~all

This record allows example.com's mail servers and the address 203.0.113.10, and marks every other source as suspicious.

Common SPF mistakes

  • More than one SPF record. A domain can have only one v=spf1 record. If two services gave you two records, merge them into one: v=spf1 include:first include:second ~all
  • Going over the 10-lookup limit. Every new service adds another include, and the limit fills up without anyone noticing. Remove services you no longer use.
  • Using +all. This lets every server in the world send as you and makes SPF pointless.
  • Forgetting a sender. If your website form or invoicing tool is not listed, those emails go to spam. You usually find out when a customer asks where their invoice is.
  • Adding the record to the wrong name. SPF goes on the domain itself (@ or an empty name). A record on a subdomain such as www does not protect your main domain.

How to add an SPF record

  1. List every service that sends mail for you: your email provider, newsletter tool, CRM, website and invoicing software.
  2. Note the include or ip4 value from each one's documentation or settings.
  3. In your DNS panel, create a TXT record named @ (or left empty) and combine everything into a single line.
  4. Save, wait a few minutes and check it with the tool above.

Frequently asked questions

Is SPF enough on its own?

No. SPF only looks at the sending server. It cannot tell whether a message was altered or relayed through another server. Real protection comes from SPF together with DKIM and DMARC.

Should I use ~all or -all?

Start with ~all if you are not sure every sender is listed. Once your DMARC reports show no unexpected sources for a few weeks, you can switch to -all.

How long until a change takes effect?

Usually within minutes. If the old record had a long TTL, some servers may keep seeing the old value for a few hours.

Other tools

Rather not deal with these records?

For companies moving to Perap Mail, we set up the MX, SPF, DKIM and DMARC records ourselves. Migration and setup support is free with every plan.

See free migration