Salesforce Marketing Cloud Engagement signs with a selector that depends on the stack your account is on: 200608 on S1, S4, S6 and S7, and 10dkim1, 11dkim1, 12dkim1, 13dkim1, 50dkim1 or 51dkim1 on the others.
| Whose | Salesforce Marketing Cloud — marketing email |
| Selector | 200608, or 10dkim1 … 51dkim1 |
| Published as | A TXT with the key under your Sender Authentication Package or private domain — often hosted by Salesforce through NS delegation |
| Rotation | By Salesforce; selector names may change, so check s= in a recent message |
| Where to find it | Setup → From Address Management; only a Sender Authentication Package or private domain is authenticated |
| Can it go? | Once Marketing Cloud no longer sends from the domain. |
Is Salesforce Marketing Cloud’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Salesforce Marketing Cloud’s key under 200608 and 10dkim1 and 11dkim1 and 12dkim1 and 13dkim1 and 50dkim1 and 51dkim1, check it, and name every other key the domain publishes.
The records
What Salesforce Marketing Cloud asks you to publish, with its own values in place of the placeholders:
200608._domainkey.<SAP domain> TXT v=DKIM1; k=rsa; p=<public key>
How it works
When the sending subdomain is delegated to ns1–ns4.exacttarget.com, Salesforce publishes the key itself; self-hosted DNS gets a zone file to copy.
Sources
Checked on 27 September 2026 against these official sources:
- Salesforce Help article 005228402 — help.salesforce.com
- Salesforce Help article 000383527 — help.salesforce.com
- Salesforce Help: Marketing Cloud: dns record maintenance — help.salesforce.com