Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

Understanding cm._domainkey: DKIM Selector Example

4 min read
02.04.2025

The record cm._domainkey is a DKIM (DomainKeys Identified Mail) DNS TXT record. It is used to authenticate email messages sent on behalf of your domain and ensure they have not been tampered with during transit. The prefix cm is the DKIM selector, which identifies the specific key to use when validating the DKIM signature.

cm._domainkey DKIM Selector
cm._domainkey — selector "cm" + _domainkey + your domain.

For closely related DKIM and mail-auth topics, see Fixing t_dkim_invalid (DKIM Signature Issue), "DKIM signature, not necessarily valid", DKIM Temperror, and check-auth@verifier.port25.com.

Key Components of cm._domainkey

  1. cm:
    • This is the selector part of the DKIM record.
    • The selector allows you to use multiple DKIM keys for different services or servers (e.g., one for Mailchimp, another for your own mail server).
  2. _domainkey:
    • A fixed subdomain used in the DNS structure to publish DKIM public keys.
  3. Complete DKIM Record:
    • The full DKIM DNS record would look something like this:
    cm._domainkey.example.com IN TXT "v=DKIM1; k=rsa; p=PUBLIC_KEY"
    • Here:
    • v=DKIM1: Specifies the DKIM version.
    • k=rsa: Indicates the key type (RSA in this case).
    • p=PUBLIC_KEY: Contains the public key used to verify the DKIM signature.

When You See cm._domainkey

The selector cm is commonly associated with email marketing platforms such as Campaign Monitor or similar services. These platforms use it as their default DKIM selector to authenticate emails sent on behalf of your domain.

Linux Hosting
Reliable and fast web hosting!
  • Free domain
  • Modern servers
  • NVMe disks
  • 7-day free trial
Linux Hosting

How to Add or Verify the cm._domainkey Record

Locate Your DKIM Record

Log in to your domain registrar or DNS management console (e.g., GoDaddy, Cloudflare, Namecheap).

Search for DNS TXT records.

Look for a record named cm._domainkey.

Publish the Record

If the record does not exist, create one based on the instructions provided by the email service (e.g., Campaign Monitor).

Example DKIM record for cm._domainkey:

Name: cm._domainkey

Type: TXT

Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqh... (your public key here)

Test the DKIM Record

Once added, verify the record using:

Common Issues with cm._domainkey

Issue Solution
Record Not Found
  • Ensure the record has been added to the correct DNS zone.
  • Allow up to 24-48 hours for DNS propagation.
Invalid Public Key Ensure the p value (public key) is copied correctly without any formatting errors (e.g., missing characters, extra spaces).
Service-Specific Selector Some services may require a different selector or format. Refer to the documentation of the email service you are configuring.
DKIM Check Fails If emails fail DKIM checks, confirm:
  • The correct selector (cm) is being used in the DKIM-Signature header.
  • The DNS record matches the private key used to sign outgoing emails.

How cm._domainkey Works in Email Authentication

When you send an email:

  1. The mail server adds a DKIM-Signature header, specifying:
    • The selector (s=cm).
    • The domain (d=example.com).
  2. The recipient server:
    • Queries the DNS for cm._domainkey.example.com to retrieve the public key.
    • Uses the public key to validate the signature in the email header.
  3. If the signature matches:
    • The email passes DKIM verification.

Benefits of DKIM

Prevents Email Spoofing

Verifies that emails claiming to come from your domain are actually sent by you or an authorized service.

Improves Email Deliverability

Authenticated emails are less likely to be marked as spam.

Enhances Domain Reputation

Increases trust with email providers like Gmail, Outlook, and Yahoo.

The cm._domainkey is a DKIM record used for email authentication, typically associated with Campaign Monitor or similar services. By properly setting up and verifying this record, you ensure that your emails are authenticated and have a higher chance of reaching recipients inboxes.

Frequently asked questions
Yes, but only as an identifier. "cm" is just Constant Contact's convention; Mailchimp uses "k1"; Sendgrid uses "s1"; Google Workspace generates random selectors. The selector lets one domain have multiple keys (one per sending service). Receiver gets the selector from the DKIM-Signature header and queries the matching TXT.
Very normal. A typical domain has 3-5 DKIM TXT records: one for the mail provider (e.g., google._domainkey), one for the transactional service (e.g., k1._domainkey), maybe one for marketing (e.g., s1._domainkey), plus one for legacy (often "default" selector). Each service signs with its own selector; receivers verify whichever matches.
DNS TXT "strings" max out at 255 chars; the record itself can be longer but must be split into multiple quoted strings. Some panels split automatically; others fail. For 2048-bit DKIM keys (~390 char base64), the split is required. Format: `"v=DKIM1; k=rsa; " "p=ABC...XYZ"` — two strings on one record. DNS protocol concatenates at query time.
Wait 30+ days before removing the old TXT. In-flight messages signed by the old key need the public key to verify; receivers may take a week to stop holding messages in retry queues. After 30 days the risk of breaking any legitimate delivery is minimal. Don't leave indefinitely — old DKIM keys still publicly available are an information leak.
Related articles
DKIM Temperror: Understanding and Resolving the Issue
"Message has a DKIM or DK signature, not necessarily valid" — Explanation and Fixes
DKIM=Temperror: No Key for Signature