Back to blog
DKIM

Salesforce DKIM Setup

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

ZeroHook
ZeroHook Team
Security Analysts
Nov 7, 2026~3 min read
Salesforce DKIM Setup
CRM ops enabled DKIM in Marketing Cloud but pasted the core Salesforce org selector into Route 53, and transactional mail passed while every nurture journey failed DMARC alignment for three weeks.

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

DMARC aligns on the domain in the From: header. If SFMC sends as `[email protected]`, publish keys for the domain and selector SFMC documents for that sender profile, not an unrelated subdomain you forgot to delegate.
“Marketing Cloud DKIM and CRM DKIM share a logo, not the same DNS row.”

Marketing Cloud DKIM Publish Steps

1

SFMC will not guess your DNS host; copy what the wizard shows. Match prod versus sandbox hostnames when SFMC splits them.

1

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.

2

Copy the exact DNS records SFMC displays (CNAME targets or TXT values). Do not substitute examples from old documentation.

3

In Cloudflare, GoDaddy, or Route 53, create records at the hostnames SFMC lists. Match prod vs sandbox if SFMC separates them.

4

Return to SFMC and run Verify or the equivalent until status shows authenticated.

5

Send a test journey or proof send. In Gmail Show original, confirm `dkim=pass` with the expected selector and domain.

6

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

Sandboxes need their own keys or you will test against production DNS and think DKIM works when only prod is signed.

Warning

Rotate keys on Salesforce's schedule. Lower DNS TTL before swap, update TXT, verify, then deactivate the old key in the UI.

Frequently Asked Questions

Key takeaways

1

Five checks we run before a client turns DMARC to quarantine on a domain that also sends from SFMC.

1

SFMC and core Salesforce need separate DKIM DNS publishes and tests.

2

Copy live wizard values; stale blog selectors fail silently in journeys.

3

Verify with Gmail Show original on real journey mail, not only SFMC's green status.

4

Merge SFMC SPF includes without creating a second `v=spf1` TXT row.

5

Plan key rotation with TTL and dual-key windows like any other ESP.

After Salesforce keys are live, check selectors next to Workspace and DMARC on zerohook.org/dns-health-check before you enforce quarantine on the same domain.

Share this analysis

Help others discover this content

Fix DNS before the next audit
Provider-specific copy-paste fixes for Cloudflare, Route53, GoDaddy, and more.
Start free scan

More from our blog