k1 is a name two services have used. As a CNAME to dkim.mcsv.net it is Mailchimp’s older DKIM setup, replaced by k2 and k3; as a TXT holding a key it is most often Mailgun’s, which has used k1 among its generated names. Neither service documents it today — what the record points at tells you whose it is.
| Whose | Mailchimp (older setup) or Mailgun — a name two services have used |
| Selector | k1 |
| Published as | A CNAME to dkim.mcsv.net is Mailchimp’s; a TXT with the key is Mailgun’s, or someone else’s |
| Key | dkim.mcsv.net answers with a 1024-bit key |
| Can it go? | A Mailchimp k1 once k2 and k3 verify; a Mailgun k1 only once Mailgun no longer signs with it — Mailgun’s dashboard lists the selectors it uses. |
Is Mailchimp (older setup) or Mailgun’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Mailchimp (older setup) or Mailgun’s key under k1, check it, and name every other key the domain publishes.
The records
Mailchimp’s older record — a Mailgun k1 is a TXT with the key instead:
k1._domainkey.example.com CNAME dkim.mcsv.net
How it works
Neither service documents k1 now: Mailchimp’s help names k2 and k3, and Mailgun’s names pic, krs, smtp, mailo and mx for new domains. What we say about k1 is what the records on Mailchimp’s and Mailgun’s own domains show.
Questions
Is k1 safe to delete?
If it is a CNAME to dkim.mcsv.net and Mailchimp shows your domain authenticated with k2 and k3, yes. If it is a TXT, find the service that signs with it first — the s= tag of a message it sent says k1.
Sources
Checked on 27 September 2026 against these official sources:
- Set Up Email Domain Authentication — mailchimp.com
- Cloudflare DNS Setup Guide — help.mailgun.com