Opens in a new tab

k2._domainkey and k3._domainkey: Mailchimp’s DKIM keys

k2 and k3 are Mailchimp’s DKIM selectors: two CNAMEs to dkim2.mcsv.net and dkim3.mcsv.net, the same for every account. They are what “authenticate your domain” in Mailchimp adds, so your campaigns are signed with your own domain rather than mcsv.net.

WhoseMailchimp — marketing email
Selectork2, k3
Published asTwo CNAMEs, to dkim2.mcsv.net and dkim3.mcsv.net — the same targets for every customer; Mailchimp keeps the keys
KeyNot documented; the keys at dkim2 and dkim3.mcsv.net are 2048-bit RSA
Before you set it upMail shows “via mailchimpapp.net” or “on behalf of mcsv.net”
Where to find itProfile → Account & billing → Domains → Start authentication (the domain must be verified first)
Can it go?Once you no longer send campaigns from the domain through Mailchimp. Mailchimp asks you to turn authentication off in Mailchimp before changing the records.

Is Mailchimp’s key on your domain?

Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Mailchimp’s key under k2 and k3, check it, and name every other key the domain publishes.

The records

What Mailchimp asks you to publish, with its own values in place of the placeholders:

k2._domainkey.example.com  CNAME  dkim2.mcsv.net
k3._domainkey.example.com  CNAME  dkim3.mcsv.net

How it works

Mailchimp shows the values only inside the account; every account we have seen points at the same two hosts, so the records are the same for everyone.

An older k1 CNAME to dkim.mcsv.net is from Mailchimp’s earlier setup; it can stay while it answers, but k2 and k3 are what it checks now.

Common mistakes

  • A DNS host that appends the domain turns k2._domainkey.example.com into k2._domainkey.example.com.example.com — enter only k2._domainkey.
  • Changing the CNAMEs after authenticating without switching authentication off first.

Setting up Mailchimp from scratch? Its SPF, DKIM and DMARC records, and a check of all three.

Questions

Do I still need k1?

Not for Mailchimp’s current authentication, which checks k2 and k3. An old k1 CNAME to dkim.mcsv.net does no harm; remove it once k2 and k3 verify.

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