The DNS records
For Mailchimp marketing email, copy the Name and Value of CNAME 1 and CNAME 2 from the Domains page. The Transactional values are fixed.
Marketing: CNAME 1
Type: CNAME · Host: k2._domainkey
<Value shown for CNAME 1 in Mailchimp>
Marketing: CNAME 2
Type: CNAME · Host: <Name shown for CNAME 2 in Mailchimp>
<Value shown for CNAME 2 in Mailchimp>
Marketing: DMARC record
Type: TXT · Host: _dmarc
<Value shown in Mailchimp, if you have no DMARC record yet>
A domain has one DMARC record. If you already publish one, keep it rather than adding a second.
Transactional: selector mte1
Type: CNAME · Host: mte1._domainkey
dkim1.mandrillapp.com
Transactional: selector mte2
Type: CNAME · Host: mte2._domainkey
dkim2.mandrillapp.com
Set it up and turn on signing
- Verify the email domain first: Mailchimp requires verification before authentication.
- Click your profile icon and choose Account & billing (account Managers choose Account), open the Domains tab, and click Start authentication next to the verified domain.
- Pick your DNS provider. Mailchimp recommends its automatic option through Entri; to do it yourself, click Or manually authenticate your domain.
- Copy CNAME 1 and CNAME 2 into your DNS, then the DMARC TXT record, clicking Next after each. The domain shows Authentication in progress and then Authenticated, usually within minutes and at most 48 hours.
- Mailchimp Transactional: under the sending domain, click View DKIM settings, add the
mte1andmte2CNAMEs, then click Test DNS Settings.
DMARC alignment
Until a domain is authenticated, Mailchimp authenticates your campaigns with its own domain, so DKIM passes for Mailchimp but not in alignment with your From address. After authentication, DMARC can pass on DKIM for your domain. Free mailbox addresses can't be authenticated at all: Mailchimp rewrites a Gmail or Yahoo From address to one of its own domains, because those providers' DMARC policies would otherwise reject the mail.
Key length and rotation
Both setups delegate the key to Mailchimp through CNAMEs, and Mailchimp doesn't publish a key length or rotation schedule. What it does document is that it records your CNAME values when you authenticate: if you change them afterward, disable authentication on the Domains page and authenticate again, or Mailchimp's records won't match DNS.
Common mistakes
- The domain appended twice. Mailchimp's example: entering
k2._domainkey.example.comcreatesk2._domainkey.example.com.example.com. Enterk2._domainkeyonly. - Editing the CNAMEs after authenticating without disabling and re-authenticating in Mailchimp.
- A second DMARC record. Keep a single
_dmarcrecord; merge rather than add. - Mixing up the products. Marketing and Transactional use different selectors; set up the pair for each product you send with.
Check your Mailchimp DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
Why does Mailchimp need a DMARC record to authenticate my domain?
Mailchimp's manual setup includes one DMARC TXT record alongside the two DKIM CNAMEs. Gmail and Yahoo require DMARC from senders of more than 5,000 messages a day, and a domain with no DMARC record can't meet that.
Can I authenticate a Gmail or Yahoo address in Mailchimp?
No. Authentication only works for domains you own and control. Mailchimp rewrites free mailbox From addresses to one of its own sending domains, because those providers' DMARC policies would otherwise reject the mail.
What DKIM records does Mailchimp Transactional (Mandrill) use?
Two CNAMEs: mte1._domainkey pointing to dkim1.mandrillapp.com and mte2._domainkey pointing to dkim2.mandrillapp.com. After adding them, click Test DNS Settings next to the sending domain.
Sources
- Mailchimp Help: Set up email domain authentication
- Mailchimp Help: About email domain authentication
- Mailchimp Developer: Transactional authentication and delivery
- Mailchimp Help: Limitations of free email addresses
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Mailchimp's documentation on October 9, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
Compare every provider's selectors in one table · SPF record for Mailchimp
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated