Opens in a new tab

cm._domainkey: Campaign Monitor’s DKIM key

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.

WhoseCampaign Monitor — marketing email
Selectorcm
Published asA TXT with the key Campaign Monitor generates — or one you bring
Key1024-bit generated; your own up to 2048. 768-bit keys must be regenerated.
RotationBy hand: remove and add the sending domain again
Where to find itAccount 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:

Know when a DKIM key disappears

Point your DMARC reports at us and we monitor the keys your mail is signed with — and email you when one stops answering, before receivers start failing your mail. Free for your first domain.

Create a free account