Email senders
Salesforce Marketing Cloud DMARC: SPF and DKIM alignment
Salesforce Marketing Cloud signs DKIM on your domain with a Private Domain or SAP. See how SPF aligns and what its basic DMARC record leaves out.
SPF include for Salesforce Marketing Cloud
Salesforce Marketing Cloud does not need an SPF include on your domain.
DKIM for Salesforce Marketing Cloud
- Selectors
- Salesforce Marketing Cloud does not document this.
- How to enable it
- Applies to a domain authenticated as a Private Domain or SAP. The DKIM key is a TXT record under _domainkey on that domain, and the selector comes from your own zone. Salesforce maintains it on a delegated domain. On a self-hosted domain, publish the entries from the zone file you download.
Salesforce Marketing Cloud signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Salesforce Marketing Cloud’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- bounce.[SAP domain]. With multi-bounce domain on: bounce.[Private Domain]
Sending ranges of Salesforce Marketing Cloud
Use these to recognize Salesforce Marketing Cloud in your reports. They change over time, so do not copy them into your SPF record.
Salesforce Marketing Cloud does not document this.
Does your domain authorize Salesforce Marketing Cloud?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Salesforce Marketing Cloud documentation
- Salesforce Help: Configure a Sender Authentication Package or Private Domain
- checked 2026-11-09
- Salesforce Help: DNS Record Maintenance for Your Marketing Cloud Engagement Custom Domain and Email Sending
- checked 2026-11-09
- Salesforce Help: Private Domain: DKIM, SPF, and DMARC Authentication FAQ
- checked 2026-11-09
- Salesforce Help: Working with the Email Sender Authentication Package
- checked 2026-11-09
- Salesforce Help: Requirements for a DMARC policy to pass for sends through Marketing Cloud Engagement
- checked 2026-11-09
- Salesforce Help: Request simple DMARC policy for a Marketing Cloud Engagement sending domain
- checked 2026-11-09
- Salesforce Help: Email Deliverability Issues (Bounces & Spam) FAQ
- checked 2026-11-09
- Salesforce Help: Deliverability Products Overview
- checked 2026-11-09
- Salesforce Help: Sender Policy Framework and Salesforce SPF Records
- checked 2026-11-09
Salesforce Marketing Cloud DMARC starts with a From domain you authenticate in Marketing Cloud Engagement. Salesforce sells that as a paid Private Domain or as a Sender Authentication Package (SAP), which adds a dedicated IP and branded links.
How it authenticates
You add the domain in Setup, under Domain SSL Certificates, and choose how to manage DNS. You can delegate the domain or a subdomain to Salesforce with four NS records. You can also self-host, download the zone file and publish every entry.
The zone carries SPF, the DNS list of servers allowed to send for a domain, on the sending domain and its bounce and reply hosts. It also carries the DKIM key, the public half of a signature that receivers check. The selector comes from your own zone.
Salesforce documents no include: for this product. Its _spf.salesforce.com article covers mail from the Salesforce application and sends Marketing Cloud customers to product-specific content.
DMARC passes with one aligned result, from SPF or DKIM. Salesforce applies a basic record during setup and suggests v=DMARC1; p=reject; adkim=r; aspf=r; pct=100;, though yours may differ.
What to watch for
Check that record before anything else. It has no rua tag, so nobody receives aggregate reports. Its p=reject can also block legitimate mail if another platform sends from the same domain. In that case, ask for p=none and a rua address until your reports show every platform passing.
A Private Domain with a different base domain from your SAP domain breaks SPF alignment. The bounce address stays on bounce.[SAP domain]. DKIM can still pass DMARC, and Salesforce warns that some providers want both. Multi-bounce domain fixes it through a support case.
Addresses added with Add Email Address or Register Domain stay unauthenticated. Only those marked SAP or Private Domain count.
On self-hosted DNS, merge the zone's SPF into any record already on that name, since two SPF records cause a permerror. Salesforce sometimes changes sending IPs, so keep those entries current. Confirm signing with the DKIM checker.