cm is Campaign Monitor’s DKIM selector: a TXT record with a 1024-bit key it generates, or one of up to 2048 bits you bring. Older 768-bit keys are flagged as at risk and must be regenerated.
| Whose | Campaign Monitor — marketing email |
| Selector | cm |
| Published as | A TXT with the key Campaign Monitor generates — or one you bring |
| Key | 1024-bit generated; your own up to 2048. 768-bit keys must be regenerated. |
| Rotation | By hand: remove and add the sending domain again |
| Where to find it | Account settings → Sending domains |
| Can it go? | Remove any earlier Campaign Monitor DKIM record when you authenticate again — two records at cm fail as “Multiple records found”. |
Is Campaign Monitor’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Campaign Monitor’s key under cm, check it, and name every other key the domain publishes.
The records
What Campaign Monitor asks you to publish, with its own values in place of the placeholders:
cm._domainkey.example.com TXT k=rsa; p=<public key>
Common mistakes
- The full name at a host that appends the domain.
- Hosts that will not take an underscore or four-level names: create _domainkey, then cm under it.
Sources
Checked on 27 September 2026 against these official sources:
- Manage your own authentication — help.campaignmonitor.com
- Email authentication troubleshooting — help.campaignmonitor.com