Salesforce DKIM Setup
Marketing Cloud and core Salesforce use different selectors. Publish the TXT Salesforce gives you, not a blog post example from 2019.

Two Salesforce Worlds, Two DKIM Stories
Salesforce Marketing Cloud (SFMC) sends bulk and journey mail through SFMC infrastructure. DKIM keys and selectors come from Email Studio admin or setup wizards SFMC provides. DNS is usually CNAME or TXT on a hostname SFMC specifies for your sending domain.
Salesforce core (CRM) email from the platform uses a different configuration path (Email Deliverability settings in Setup). Selectors and DNS names differ from SFMC. Treat them as separate projects even when the brand domain matches.
Warning
“Marketing Cloud DKIM and CRM DKIM share a logo, not the same DNS row.”
Marketing Cloud DKIM Publish Steps
SFMC will not guess your DNS host; copy what the wizard shows. Match prod versus sandbox hostnames when SFMC splits them.
In SFMC, open the admin area for sender authentication or domain keys (wording varies by tenant version). Add the sending domain you use in From: addresses.
Copy the exact DNS records SFMC displays (CNAME targets or TXT values). Do not substitute examples from old documentation.
In Cloudflare, GoDaddy, or Route 53, create records at the hostnames SFMC lists. Match prod vs sandbox if SFMC separates them.
Return to SFMC and run Verify or the equivalent until status shows authenticated.
Send a test journey or proof send. In Gmail Show original, confirm `dkim=pass` with the expected selector and domain.
Add or update SPF includes SFMC requires on the bounce or envelope domain SFMC specifies, merged into your single apex SPF if that is where authorization lives.
Core Salesforce org mail
In Setup, search Email Deliverability or DKIM keys (labels change between releases). Generate a key pair, publish the TXT record at the selector hostname Salesforce shows, activate the key, then send a test from a workflow or Apex email path you actually use.
Pro tip
Warning
Frequently Asked Questions
Key takeaways
Five checks we run before a client turns DMARC to quarantine on a domain that also sends from SFMC.
SFMC and core Salesforce need separate DKIM DNS publishes and tests.
Copy live wizard values; stale blog selectors fail silently in journeys.
Verify with Gmail Show original on real journey mail, not only SFMC's green status.
Merge SFMC SPF includes without creating a second `v=spf1` TXT row.
Plan key rotation with TTL and dual-key windows like any other ESP.
Share this analysis
Help others discover this content
