Opens in a new tab

include:cust-spf.exacttarget.com — Salesforce Marketing Cloud’s SPF include

include:cust-spf.exacttarget.com lists the sending servers of Salesforce Marketing Cloud Engagement — ExactTarget before Salesforce bought it — and many company SPF records still carry it. Salesforce has withdrawn the page that asked for it. What SPF checks for Marketing Cloud mail is its bounce domain, which aligns with yours only when your domain is set up as Marketing Cloud’s sending domain (a Sender Authentication Package or a private domain).

v=spf1 include:cust-spf.exacttarget.com -all
Belongs toSalesforce Marketing Cloud — Marketing Cloud Engagement (formerly ExactTarget)
Needed on your domain?Only in some set-ups — by default SPF checks a different domain for its mail

What it costs, and is it in your record?

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

What it covers

Mail sent from Marketing Cloud Engagement. It does not cover mail from the core Salesforce application (_spf.salesforce.com), and Marketing Cloud Next authenticates with CNAME records instead.

Do you need it?

SPF alignment needs the return-path — Marketing Cloud’s “bounce domain” — to match your From domain. When you send from a domain other than the one set up in your Sender Authentication Package, the bounce domain is different and SPF does not align, whatever your root record says.

The records that count are set up with the sending domain itself: Salesforce hosts them for a Sender Authentication Package domain, and you publish them for a private domain. An include on a corporate root domain that is neither does nothing for Marketing Cloud mail.

Common mistakes

  • Expecting the include on your root to make Marketing Cloud mail align — it is the bounce domain that counts.
  • Putting a proxy or firewall in front of Salesforce-hosted custom domains — Salesforce says to exempt them.

Includes it replaced

Salesforce’s Marketing Cloud “Sender Policy Framework and Authentication FAQs” page, which gave the include, now redirects to the core Salesforce SPF article. The include still resolves in DNS.

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