Salesforce Marketing Cloud: SPF, DKIM & DMARC

Set up SPF, DKIM and DMARC in Salesforce Marketing Cloud via the Sender Authentication Package: official SPF include, delegated domain and DMARC rollout.
4 min read
Updated 2026-11-04
Brand Specific
salesforcesfmcspfdkimdmarc

Salesforce Marketing Cloud has an ExactTarget heritage, and it still shows in its authentication model. If you do nothing, your campaigns go out on Salesforce's shared member domains — receivers see "via exacttarget.com"-style senders, SPF passes for a domain you do not own, and DMARC alignment is impossible. Under the Gmail, Yahoo and Microsoft sender requirements, that setup costs inbox placement at any serious volume.

The official fix is the Sender Authentication Package (SAP): a dedicated sending domain, branded Return-Path, DKIM keys and a dedicated IP, provisioned by Salesforce. This guide covers what SAP changes, the records you publish yourself — including the official SPF include value — and how to run DMARC on top.

What you need

  • Marketing Cloud with Admin access — SAP is configured under Setup, in the send management area, by users with administrator rights.
  • An SAP add-on on your contract. SAP is a licensed component requested through your Salesforce account team; Salesforce support provisions the domain, Return-Path, DKIM keys and dedicated IP.
  • A subdomain reserved for sending, for example email.yourdomain.com or mail.yourdomain.com. Salesforce typically asks you to delegate this subdomain to Marketing Cloud's name servers.
  • DNS control over the parent zone, so you can publish the delegation and any remaining records.

How authentication works in SFMC

Three layers decide whether your mail is aligned:

  • Sender Profile. Sets the From address and Return-Path for sends. Without SAP, sender profiles ride on Salesforce's shared domain, so neither SPF nor DKIM aligns with yours.
  • Delegated domain (SAP). Your subdomain is delegated to Marketing Cloud name servers, so Salesforce controls DKIM keys, the Return-Path and bounce handling inside that zone while the visible From domain remains yours.
  • Your own DNS records. The SPF record for the sending domain stays in your zone, and the DMARC record at your root domain ties everything together.

Configuration steps

  1. Request and provision SAP. Work with your Salesforce account team to add the package. During provisioning you choose the delegated subdomain (for example email.yourdomain.com), and Salesforce provides the NS records to publish at your DNS provider. Manage it in Marketing Cloud under Setup > Send Management > Sender Authentication Package.
  2. Publish the SPF record for the sending domain. Salesforce's current official include for Marketing Cloud is cust-spf.exacttarget.com:
email.yourdomain.com.  TXT  "v=spf1 include:cust-spf.exacttarget.com -all"

If the domain also covers other senders, merge them into this record:

v=spf1 ip4:203.0.113.10 include:cust-spf.exacttarget.com -all

Never publish a second v=spf1 record on the same name, and do not copy old tutorials referencing bare exacttarget.com includes — Salesforce's help documentation specifies cust-spf.exacttarget.com.

  1. Confirm DKIM. SAP provisions DKIM for the delegated domain with 2048-bit keys; support supplies the exact records. Because the signing domain is your subdomain, DKIM aligns with the From domain under default relaxed alignment.
  2. Point your Sender Profile at the SAP domain. Make sure the From address and delivery profile use your authenticated subdomain, so every journey and campaign sends aligned.
  3. Publish DMARC at your root domain, starting in monitoring mode:
_dmarc.yourdomain.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; fo=1"

Read the aggregate reports for two to four weeks, confirm every legitimate source passes, then move to quarantine and finally reject. Jumping straight to p=reject loses your own campaigns to spam folders.

Verify

Send a test to Gmail and inspect the headers with the Email Header Analyzer: SPF should pass for your subdomain, DKIM should pass with d=email.yourdomain.com, and DMARC should pass. Check each record with the SPF Checker, DKIM Checker and DMARC Lookup, or run the Email Health Check. For the concepts, see the authentication fundamentals guide.

Common mistakes

  • Expecting DMARC to pass without SAP. On shared member domains, SPF and DKIM pass for Salesforce's domain, not yours. No DNS tweak at your end fixes alignment — the sending domain has to change.
  • Publishing SPF on the wrong name. The SPF record belongs on the domain in the envelope sender — your SAP sending subdomain, not necessarily the root. Match it to what the Sender Profile uses.
  • Running two SPF records. One domain, one v=spf1 TXT record. Duplicates fail every SPF check for the domain.
  • Forcing strict alignment. With a subdomain setup, adkim=s and aspf=s break relaxed alignment and fail otherwise-valid mail. Keep relaxed alignment unless you have a specific reason.
  • Ignoring DMARC reports. SAP fixes Marketing Cloud, but other senders still appear in your reports. Monitor them with the DMARC Report Analyzer before enforcing.

Frequently asked questions

What exactly is the Sender Authentication Package?

SAP is Salesforce's licensed authentication bundle: a custom sending domain delegated to Marketing Cloud name servers, a branded Return-Path, DKIM signing and a dedicated IP. Purchase it through your account team; support provisions it.

Which SPF include should I use for Marketing Cloud?

Use include:cust-spf.exacttarget.com in the sending domain's SPF record — the value in Salesforce's official SPF documentation. Do not copy older blog posts referencing other forms.

Can I pass DMARC without SAP?

Not with the default shared domains — alignment is structurally impossible. Some senders use self-authentication, configuring sender profiles with their own verified domain, DKIM keys and Return-Path, but it is harder than SAP and you own every failure mode.

Does SPF on the SAP domain cover my whole company?

No. SPF is per-domain: your root domain, corporate mail and Marketing Cloud subdomain each need their own record, and together they must respect the ten-lookup limit — check with the SPF Checker.

Was this guide helpful?