Docs Security

SPF record (email spoofing)

Checks your domain's SPF record, which lists the servers allowed to send email as you, so forged email is easier for inboxes to spot.

SecurityWeight 3In reports as email-spf

What it checks

We look up the TXT records on your main registered domain, for example example.com even when you scan www.example.com or shop.example.com, using public DNS over HTTPS. We pick out the records that start with v=spf1.

The check does not follow include: entries or count DNS lookups. It looks at how many SPF records there are and how the record ends.

Why it matters

Without SPF, receiving mail servers cannot tell your real email from email forged to look like it comes from your domain. That helps scammers send fake invoices or password resets in your name, and can hurt the delivery of your real mail.

Gmail and Yahoo ask every sender to authenticate their mail, and ask bulk senders to have SPF, DKIM and DMARC in place.

How to fix it

List every service that sends email as your domain: your mailbox provider, newsletter tool, CRM, help desk, shop notifications. Put them all in one SPF record, and end it with ~all or -all so everything else is marked as not allowed.

If the domain sends no email at all, publish a record that allows nothing. Keep the record within SPF's limit of 10 DNS lookups, which long lists of include: entries can go past.

Platform notes

Any site

SPF lives in DNS, so you edit it wherever your domain's DNS is managed: your registrar, Cloudflare, or the website platform if it manages DNS for you. Your mail providers' help pages give the include: value to add.

Shopify, Wix and Squarespace

If the platform manages your domain's DNS, add or edit the TXT record in its domain settings.

Cloudflare

Edit the TXT record under DNS, Records. Cloudflare's email security tools can also show which services send as you.

Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.

Want to test just this? Use the free SPF and DMARC checker.

Questions

Should I end SPF with ~all or -all?

Both pass this check. ~all asks receiving servers to treat other senders with suspicion, and -all asks them to reject. Many domains start with ~all and move to -all once they are sure every sender is listed.

What if I have two SPF records?

Merge them into one. Mail servers treat two SPF records on the same name as an error, so neither of them works.

See what this check finds on your site

Free, about 30 seconds, with every other check included.