Suped

How to set up DMARC/DKIM/SPF for Salesforce Marketing Cloud

Published 7 Jul 2026
Updated 7 Nov 2026
14 min read
Summarize with
SPF, DKIM, and DMARC setup for Salesforce Marketing Cloud Engagement.
Updated on 7 Nov 2026: We clarified Salesforce Marketing Cloud bounce-domain setup and corrected the SPF, DKIM, and DMARC validation steps.
Salesforce Marketing Cloud Engagement needs a verified sending domain and correctly configured SPF and DKIM. DMARC requires at least one passing authentication method with identifier alignment to the domain in the visible From address. Start by choosing the exact From domain, usually a dedicated subdomain such as marketing.example.com. Publish the tenant-specific DNS records, review the DMARC policy for the From domain, and test a real campaign send.
The Salesforce private domain FAQ explains authenticated sending with Private Domain and how it differs from Sender Authentication Package (SAP). Email sent directly by Salesforce Platform uses a different DKIM Keys workflow and can use include:_spf.salesforce.com. Marketing Cloud Next also has a separate Authenticated Domains workflow. Use the records generated for the Salesforce product that sends your email.

Configure SAP or a Private Domain

In Salesforce Marketing Cloud Engagement, the authenticated sending domain is the setup unit. Sender Authentication Package covers authenticated sending plus branded click, image, and view-as-webpage URLs. Private Domain provides authenticated sending without branded link or image domains, including for accounts using shared IPs. Confirm an available SAP or Private Domain license and access to the relevant DNS zone before starting.
Salesforce Marketing Cloud Engagement sending domain authentication setup.
Salesforce Marketing Cloud Engagement sending domain authentication setup.
  1. Access: Open Marketing Cloud Engagement with an admin user, select the sending business unit, then go to Setup > Security > Domain SSL Certificates and click New Domain. A disabled New Domain button indicates that no SAP or Private Domain license is available.
  2. Domain: Choose the exact From domain, for example marketing.example.com. A dedicated subdomain keeps Marketing Cloud Engagement DNS separate.
  3. Package: Choose SAP for email authentication and URL branding, or Private Domain for email authentication only. Authenticated sending is on by default with SAP and must be selected during Private Domain setup. Complete the IP address and Reply Mail Management choices offered for the package before submitting the configuration.
  4. Records: Use the DNS delegation instructions or download the self-hosted zone file. Do not invent SPF, DKIM, MX, or CNAME values.
  5. Status: Wait for the domain to move through Pending DNS validation and In progress to Active. Salesforce says the In progress stage can take up to five business days.
Illustrative Marketing Cloud Engagement DNS patterndns
; Illustrative only. Copy actual values from your Salesforce zone file. ; Replace PRIORITY_FROM_SALESFORCE with the supplied MX priority. $ORIGIN marketing.example.com. bounce MX PRIORITY_FROM_SALESFORCE bounce.s50.exacttarget.com. reply MX PRIORITY_FROM_SALESFORCE reply.s50.exacttarget.com. click CNAME click.virt.s50.exacttarget.com. view CNAME view.virt.s50.exacttarget.com. 50dkim1._domainkey TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY_FROM_SALESFORCE" @ TXT "v=spf1 include:cust-spf.exacttarget.com -all" bounce TXT "v=spf1 include:cust-spf.exacttarget.com -all" reply TXT "v=spf1 include:cust-spf.exacttarget.com -all"
Use Salesforce values
Marketing Cloud Engagement stacks vary. A zone file can include stack-specific hosts, selectors, and IP addresses. Copy the exact values Salesforce provides for the tenant and domain, then check public DNS resolution before changing the DMARC policy.

Choice

Use

Tradeoff

SAP
Authentication and URL branding
One branding domain per business unit
Private Domain
Additional From domains
Does not brand links or images
Delegated DNS
Dedicated subdomain
Salesforce manages the zone
Self-hosted DNS
Existing or shared domain
Your team maintains every record
Choose the Marketing Cloud Engagement domain option before adding DNS.

Verify the sending domain and From addresses

Domain verification and email authentication are separate controls in Marketing Cloud Engagement. SAP, Private Domain, or Domain Registration can establish a Verified Domain. Only SAP and Private Domain configure SPF and DKIM for authenticated sending.
  1. Domain: Open Setup > From Address Management and confirm the sending domain appears as SAP, Private, or Registered with a verified status.
  2. Addresses: Verify and save From addresses in Account Settings, Users, and Sender Profiles. This check still applies when the domain already has SAP or Private Domain authentication.
  3. Business units: Check every business unit that sends. Registered domains can be copied to existing business units and must be copied again after a new business unit is created.
  4. Dynamic From: Import the planned From addresses into From Address Management when AMPscript or sender profiles generate addresses dynamically.
  5. Send path: Retest each production sender profile after verification. A verified domain does not prove that SPF, DKIM, or DMARC passes.
Verification is not authentication
Domain Registration proves control of a From domain so Marketing Cloud Engagement can allow it. It does not add branded SPF or DKIM. Use SAP or Private Domain when the same domain must also pass DMARC through Marketing Cloud Engagement.

Set up SPF

SPF helps Salesforce Marketing Cloud Engagement pass DMARC only when the SPF-authenticated return-path domain has identifier alignment with the visible From domain. Publish the Salesforce SPF value on the return-path host in the zone file, then test the envelope sender used by a real campaign.
Salesforce Marketing Cloud Engagement SPF record for bounce.marketing.example.com.
Salesforce Marketing Cloud Engagement SPF record for bounce.marketing.example.com.
  1. Existing: Keep one SPF TXT record per DNS host. Merge Salesforce into the current record instead of publishing a second SPF record.
  2. Include: Use the value in the Marketing Cloud Engagement zone file. A common value is include:cust-spf.exacttarget.com. Do not substitute include:_spf.salesforce.com from Salesforce Platform instructions.
  3. Return-path: Publish SPF on the bounce or custom Mail From host Salesforce provides so SPF can authenticate the envelope sender.
  4. Root: Do not add Salesforce to the root SPF record unless that host is the Mail From domain or the tenant-specific zone file requires it.
  5. Limit: Keep SPF within the 10-term DNS lookup limit, including nested include and redirect evaluations. An include does not always cost just one lookup.
SPF examplesdns
Host: bounce.marketing.example.com TXT: v=spf1 include:cust-spf.exacttarget.com -all Host: marketing.example.com TXT: v=spf1 include:cust-spf.exacttarget.com -all

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
After the record resolves in public DNS, run the SPF check against the exact host Salesforce uses for bounces or SMTP MAIL FROM. SPF records do not inherit: a TXT record at marketing.example.com does not cover bounce.marketing.example.com. Publish each SPF host required by the Salesforce zone file.
SPF checks that matter
  1. Pass: SPF returns pass for the Salesforce envelope domain used by the actual campaign.
  2. Domain: Under relaxed DMARC alignment, the envelope domain and visible From domain share the same organizational domain.
  3. Errors: Investigate temporary DNS errors and correct permanent SPF errors, including excessive lookups, before policy enforcement.
  4. Scope: The Salesforce include belongs only on hosts Salesforce uses, not every domain in the company.

Fix SPF alignment for Private Domains

A Private Domain can retain the SAP bounce domain as its SMTP MAIL FROM. If the two domains belong to different organizational domains, SPF can pass without DMARC identifier alignment. Adding an SPF include to the visible From domain does not change the envelope sender.
  1. Check a production message's Return-Path against its visible From domain to confirm the mismatch.
  2. Before requesting multi-bounce domains, verify that the Private Domain's bounce host has working MX and SPF records from Salesforce.
  3. Ask Salesforce Support to enable Multi-Bounce Domains. Supply the target Member ID (MID) and a Private Domain for verification. The setting applies to the MID.
  4. After activation, test every Private Domain. Expect a return path such as bounce.brand.example for a From domain of brand.example. This meets relaxed SPF alignment; aspf=s requires an exact domain match.
A passing DKIM result with identifier alignment is sufficient for DMARC even when SPF lacks identifier alignment.

Set up DKIM

DKIM is usually the more stable DMARC path for Salesforce Marketing Cloud Engagement because forwarding can break SPF. DMARC passes when a valid DKIM signature has identifier alignment with the visible From domain. The selector and public key for Marketing Cloud Engagement come from Salesforce, not a local key generator.
Salesforce Marketing Cloud Engagement DKIM selector and public key for marketing.example.com.
Salesforce Marketing Cloud Engagement DKIM selector and public key for marketing.example.com.
  1. Selector: Copy the stack-specific selector under _domainkey from the Salesforce zone file.
  2. Type: Publish the Salesforce-provided DKIM public key as the TXT record in the Engagement zone file. Do not substitute Salesforce Platform's two-CNAME DKIM setup.
  3. Host: Use the full host Salesforce provides. Shorten it only when the DNS provider automatically appends the zone.
  4. Provisioning: Wait for the selector to resolve publicly and the sending domain to become Active, then send a message to confirm Salesforce adds the DKIM signature.
  5. Business units: Check every business unit and sender profile that uses the domain. A parent business unit result does not validate every production send path.
Delegated DNS
Salesforce manages the hosted zone after delegation. Verify the live DKIM selector because the displayed setup status and public DNS can update at different times.
  1. Control: Salesforce publishes the required DKIM values.
  2. Risk: DNS troubleshooting depends on Salesforce visibility.
  3. Check: Query the selector after Salesforce marks the domain active.
  4. Fit: Use delegation when the entire subdomain is dedicated to Marketing Cloud Engagement.
Self-hosted DNS
Your DNS team publishes every Salesforce value. Compare the downloaded zone file with public DNS because host suffix and record-type mistakes are common.
  1. Control: Your team owns every TXT, CNAME, MX, and A record.
  2. Risk: Hostname suffix mistakes can publish DKIM under the wrong name.
  3. Check: Query the exact selector host shown by Salesforce.
  4. Fit: Use self-hosting when central DNS controls domain changes or the domain already has records for another use.
Illustrative DKIM TXT recorddns
Host: 50dkim1._domainkey.marketing.example.com Type: TXT Value: v=DKIM1; k=rsa; p=PUBLIC_KEY_FROM_SALESFORCE
Common DKIM failure
If Salesforce signs only with an exacttarget.com or stack domain instead of your authenticated sending domain, DKIM can pass without DMARC identifier alignment. DMARC fails if SPF also lacks a passing result with identifier alignment. Check the domain configuration or sender profile. The SFMC DKIM failures page covers that symptom.

Set up DMARC

DMARC belongs on the domain in the visible From address. RFC 9989 defines the current DMARC protocol, RFC 9990 defines aggregate reporting, and RFC 9991 defines failure reporting. Start a new Salesforce Marketing Cloud rollout at p=none to collect aggregate reports without asking receivers to block mail. If the domain already uses quarantine or reject, keep that policy and repair Salesforce authentication before sending.
  1. Host: Check the existing DMARC record and any inherited parent policy first. Use one DMARC TXT record at _dmarc.marketing.example.com for that From subdomain, or _dmarc.example.com when the From domain is example.com.
  2. Policy: For a domain without an enforcement policy, use p=none while identifying and repairing legitimate traffic. Preserve an existing quarantine or reject policy when adding Salesforce.
  3. Reports: Send rua reports to an address that can receive and process aggregate XML files. For an external reporting domain, confirm that the destination has authorized reports for your domain.
  4. Subdomains: On the organizational domain, sp sets the policy for existing subdomains without an overriding record. Use p on a sending subdomain's own record. RFC 9989 also defines np for non-existent subdomains.
  5. Generator: Use the DMARC record generator to build the final record without hand-typing optional tags.
Starter DMARC recorddns
v=DMARC1; p=none; rua=mailto:dmarc@example.com

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Run the DMARC check against the same domain that appears after the @ in the Marketing Cloud Engagement From address. Checking only the parent can miss a DMARC record published directly on the sending subdomain.
Publish in the right DNS zone
For self-hosted DNS, publish the DMARC record in your own zone. Newly provisioned SAP domains already have a basic DMARC policy, so check the live record before adding another. For a subdomain delegated to Salesforce, open a Salesforce Support case with the target domain and full replacement DMARC TXT value.
Passing condition
A Marketing Cloud Engagement message passes DMARC when at least one authentication path both passes and has identifier alignment: DKIM through the d= signing domain, or SPF through the return-path domain.

Test email authentication and troubleshoot failures

Do not judge the setup only by DNS lookups or the Salesforce status. Send a real message from Marketing Cloud Engagement because its headers show the DKIM signing domain, SPF return path, and DMARC result.
  1. Send: Send from the production business unit and sender profile, not a generic test route that uses another profile.
  2. Headers: Read the receiving server's Authentication-Results for spf=pass, dkim=pass, and dmarc=pass. Confirm which passing method provides DMARC identifier alignment.
  3. DKIM: Read d= and s= in DKIM-Signature. Query s._domainkey.d using those values and confirm that d= meets the DMARC record's DKIM alignment mode.
  4. SPF: Compare the smtp.mailfrom domain in Authentication-Results with the visible From domain under the DMARC record's SPF alignment mode.
  5. Retest: Wait for the corrected DNS response to appear publicly, then send again before changing the DMARC policy.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
If a receiver rejects the test, save the SMTP bounce reason and JobID. Give Salesforce Support those details and the sending MID; include full message headers when a received copy is available.

Signal

Cause

Fix

DKIM fail
Missing key or changed signed content
Check the signature's selector and changes after signing
DKIM mismatch
d= lacks identifier alignment
Fix the authenticated domain or sender profile
SPF fail
Wrong host or missing include
Repair return-path SPF
DMARC fail
Neither method passes with identifier alignment
Fix DKIM or SPF alignment
SPF permerror
Syntax, duplicates, or lookups
Repair the SPF record
Use message headers to map each failure to the right fix.
Do not test the wrong path
A Salesforce system notification, a CRM email, and a Marketing Cloud Engagement campaign can use different mail paths. Accept a pass result only when the message came from the same business unit, sender profile, and domain used for production sends.

Monitor Salesforce authentication

Salesforce Marketing Cloud authentication can break after a business unit change, sender profile change, DNS cleanup, or Private Domain migration. Suped, our DMARC reporting and email authentication platform, processes aggregate reports into source-level results and alerts so teams can identify which Salesforce mail stream is failing. Reports describe an earlier reporting window, so use fresh message headers to verify an immediate fix.
  1. Sources: Suped groups Salesforce Marketing Cloud separately from other senders so the affected source stays clear.
  2. Alerts: Suped notifies the team when Salesforce SPF, DKIM, or DMARC failures cross a configured threshold.
  3. Diagnosis: Suped shows the failing domain and authentication results needed to trace the DNS or sender-profile problem.
  4. After a fix, compare subsequent reporting windows for the affected domain before increasing enforcement.
Where Suped fits
Suped's DMARC monitoring lets teams review Salesforce results beside other approved senders, identify the failing domain, and give the DNS or Salesforce administrator the authentication evidence needed to investigate.

Secure your domain with p=reject

Move a Salesforce Marketing Cloud domain to p=reject only after real campaign traffic shows that every legitimate source passes DMARC consistently. The policy asks receivers to reject messages that fail DMARC, so validate journeys and infrequent automated sends before enforcement.
  1. Baseline: For a domain starting at p=none, monitor long enough to capture normal campaigns, journeys, regional sends, and infrequent seasonal traffic. Keep an existing enforcement policy in place when adding Salesforce.
  2. Fix: Account for all legitimate sending sources and repair their authentication failures before enforcement.
  3. Stage: After legitimate sources pass consistently, move a dedicated sending subdomain to quarantine and review subsequent aggregate reports before reject.
  4. Testing: RFC 9989 made pct historic. The t=y flag requests test treatment one policy level lower, rather than percentage enforcement. Receivers that do not support t can ignore it and apply the full published policy.
  5. Reject: Set p=reject only when Salesforce DKIM passes consistently and every other legitimate sender is accounted for.
Policy readiness
Use source ownership and authentication results before enforcing Salesforce Marketing Cloud domains.
Monitor
Sources unknown
Keep p=none while the report data contains unidentified sources.
Repair
Failures remain
Fix SPF, DKIM, and sender-profile problems before changing policy.
Stage
Review quarantine results
Review quarantine results after legitimate sources pass, before requesting reject.
Reject
Legitimate mail passes
Enforce after all legitimate production mail passes DMARC consistently.
Reject policy exampledns
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Where Suped helps
Suped's hosted DMARC lets teams stage policy changes without repeated DNS edits. Combined with report processing and alerts, it gives teams a controlled workflow for taking a Marketing Cloud Engagement domain to reject.

FAQ

SAP is not required to authenticate a custom From domain. SAP provides authentication and branded URLs. Private Domain provides authentication without branded link or image domains and works with shared IPs. Domain Registration verifies ownership but does not configure SPF or DKIM.

Publish SPF on every host required by the tenant-specific Salesforce zone file, including the bounce host used as SMTP MAIL FROM. Root-domain SPF does not cover subdomains. Add Salesforce at the root only if that host sends through Salesforce or the zone file requires it.

Check the DKIM d= domain in the message headers. DKIM can pass cryptographically while using a domain that lacks DMARC identifier alignment with the visible From address. Fix the authenticated domain or sender profile, then send another production-path test. With adkim=s, d= must exactly match the visible From domain; relaxed alignment uses a shared organizational domain.

Salesforce Marketing Cloud commonly sends through ExactTarget infrastructure, so rDNS ending in exacttarget.com often indicates Marketing Cloud Engagement. Confirm the source with message headers, DMARC aggregate reports, and the sending business unit before authorizing it.

The include cust-spf.exacttarget.com is associated with Salesforce Marketing Cloud Engagement SAP and Private Domain configurations. Use the exact include in the tenant-specific zone file. The include _spf.salesforce.com belongs to a different Salesforce Platform mail path.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing