Opens in a new tab

include:_spf.salesforce.com — Salesforce’s SPF include, and the two settings that decide whether it counts

include:_spf.salesforce.com authorises the mail servers of the Salesforce application — Sales and Service Cloud — to send as your domain. Whether SPF actually checks it depends on two settings: with Email Security Compliance or Bounce Management on, Salesforce puts its own bounce address in the envelope (…bnc.salesforce.com), and SPF checks that instead. Salesforce’s preferred fix for DMARC is a DKIM key.

v=spf1 mx include:_spf.salesforce.com ~all
Belongs toEmail sent from the Salesforce application (Sales and Service Cloud)
Needed on your domain?It depends on how you use it — see below

What it costs, and is it in your record?

We measure include:_spf.salesforce.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Salesforce’s is there and what it costs.

What it covers

Mail sent from the Salesforce application itself. Account Engagement (Pardot) and Marketing Cloud have their own SPF instructions.

Do you need it?

It depends on Setup → Deliverability. With “Enable compliance with standard email security mechanisms” or “Activate bounce management” on, the envelope sender becomes a Salesforce bounce address such as …@abc123.bnc.salesforce.com: the mail passes SPF on Salesforce’s domain, the include on yours is never checked, and SPF cannot align for DMARC.

With both off, Salesforce sends with your own address in the envelope, and then “If you don’t enable Email Security Compliance”, it recommends adding include:_spf.salesforce.com to your record. Its preferred route to DMARC either way is DKIM.

Common mistakes

  • Using another salesforce.com SPF name — only _spf.salesforce.com covers mail from the application.
  • Listing Salesforce’s addresses by hand: its include uses a macro that covers every Salesforce mail server, and Salesforce does not recommend copying ranges.
  • Leaving Bounce Management on and expecting SPF to align with your domain.

Setting up Salesforce: SPF, DKIM and DMARC together →

Questions

Why does the record use exists: instead of addresses?

It checks the sending address against a list Salesforce keeps in DNS, so it never goes out of date — and costs one lookup in your record, plus the include itself.

Sources

Checked on 26 September 2026 against these official sources:

Stay under 10 lookups without dropping a sender

Let us host your SPF record: you publish one include line, we flatten every service in it to their addresses and refresh it hourly, so however many there are they fit in a few lookups — and we tell you when a service changes its addresses. On the Personal plan and up.

Create a free account