Mailchimp and Mandrill: authenticate your domain
What this guide is for
Mailchimp sends your campaigns from its servers. When you authenticate your domain, Mailchimp signs your emails with DKIM for your domain, which enables DMARC alignment and avoids the "via mcsv.net" notice at some recipients. Mandrill (Mailchimp Transactional) has its own procedure, described below.
Expected records (Mailchimp Marketing)
The current procedure requires 2 CNAME records (DKIM) and 1 TXT record (DMARC). The exact names and values are shown in your account: copy those.
| Type | Name (host) | Value |
|---|---|---|
| CNAME | k2._domainkey |
value shown by Mailchimp (usually dkim2.mcsv.net) |
| CNAME | k3._domainkey |
value shown by Mailchimp (usually dkim3.mcsv.net) |
| TXT (DMARC) | _dmarc |
v=DMARC1; p=none; rua=mailto:[email protected] |
- The
k2andk3names and their targets are the ones commonly observed; Mailchimp's public documentation does not list them. Rely on the instructions in your account. - Mailchimp does not ask for an SPF include in this procedure. An old
include:servers.mcsv.netmay exist in your SPF record: only remove it after checking that no sending depends on it. - If your host automatically appends the domain, enter only
k2._domainkey. Also check that the value did not get your domain appended (e.g.dkim2.mcsv.net.example.com).
Steps in Mailchimp
- Verify the domain first: on the domains page, click Add & Verify Domain and confirm with the verification email sent to an address on that domain.
- Click your profile icon, then Account & billing (or Account), and open the Domains tab.
- Next to the verified domain, click Start authentication, choose your DNS provider from the list and click Next.
- Mailchimp offers automatic setup through Entri. To do it yourself, choose Or manually authenticate your domain and add the records shown at your DNS host, returning to click Next after each set.
- While validation runs, the page shows "Authentication in progress". Updates usually take a few minutes, up to 48 hours. The Authenticated label appears when done.
Do not change the CNAME records after authentication: Mailchimp keeps the validated values on file.
Mandrill (Mailchimp Transactional)
In Mandrill, each sending domain is verified separately:
| Type | Name (host) | Value |
|---|---|---|
| CNAME | mte1._domainkey |
dkim1.mandrillapp.com |
| CNAME | mte2._domainkey |
dkim2.mandrillapp.com |
| TXT (DMARC) | _dmarc |
your DMARC policy |
Older setups used a DKIM TXT record and include:spf.mandrillapp.com in the SPF record. Follow the Mailchimp Transactional Authentication and Delivery page for the current procedure.
Check the setup
- In the Domains tab, the domain should carry the Authenticated label.
- Send a test campaign to a Gmail address, open Show original and check for
DKIM: PASSwith your domain. - Run a new scan in this tool.
DMARC
Publish a single TXT record at _dmarc.<your domain>, starting with monitoring:
v=DMARC1; p=none; rua=mailto:[email protected]
Read the reports for a few weeks, check that all your legitimate mail passes, then move gradually to p=quarantine and p=reject.