Salesforce lets you name the selector and an alternate when you create a DKIM key. Both are CNAMEs to custdkim.salesforce.com, and Salesforce switches between them every 30 days. Since Spring ’26 it will not send from an unverified domain.
| Whose | Salesforce — CRM (Sales and Service Cloud) |
| Selector | a selector you choose, and its alternate |
| Published as | Two CNAMEs, to <selector>.<random>.custdkim.salesforce.com; Salesforce keeps the keys |
| Key | RSA, size of your choosing — Salesforce recommends 2048 |
| Rotation | Automatic, every 30 days: the alternate is published on day 25 and takes over on day 30 |
| Where to find it | Setup → DKIM Keys → Create New Key; Activate once both CNAMEs resolve |
| Can it go? | Once the org no longer sends from the domain. Keys cannot move between orgs: a refreshed sandbox needs new keys and CNAMEs. |
Is Salesforce’s key on your domain?
Salesforce makes a selector for each account. Enter a domain and the selector it gave you — or paste the DKIM-Signature header of a message it sent — and we check the key, and name every other key the domain publishes.
The records
Salesforce’s own example:
example-sf-a._domainkey.example.com CNAME example-sf-a.k4tyd2.custdkim.salesforce.com
example-sf-b._domainkey.example.com CNAME example-sf-b.k4tyd2.custdkim.salesforce.com
Common mistakes
- A proxied CNAME at Cloudflare.
- Another record at the same name as the CNAME.
- Using the My Domain name instead of the email domain.
What changed
- Spring ’26 — Email from an unverified domain fails with “550 5.7.1 Delivery not authorized”; domains already in use were enforced between 29 June and 27 July 2026.
Setting up Salesforce from scratch? Its SPF, DKIM and DMARC records, and a check of all three.
Sources
Checked on 27 September 2026 against these official sources:
- Salesforce Help: Create secure dkim — help.salesforce.com
- Salesforce Help: Considerations dkim — help.salesforce.com
- Salesforce Help article 005316090 — help.salesforce.com