Mailchimp domain authentication (formerly 'domain verification') ensures your campaigns are sent using your own domain's DKIM signature rather than Mailchimp's shared domain. This improves inbox placement and removes the 'via mcsv.net' label in some email clients.
DNS Records Required
| Type | Host | Value | TTL | Notes |
|---|---|---|---|---|
| CNAME | k1._domainkey | dkim.mcsv.net | 3600 | DKIM authentication for Mailchimp |
| TXT | @ | v=spf1 include:servers.mcsv.net ~all | 3600 | Add to existing SPF — don't replace |
Step-by-Step Setup
Go to Domain Authentication in Mailchimp
In Mailchimp → Audience → Domains → Authenticate a Domain. Enter your sending domain.
Copy the DKIM CNAME record
Mailchimp shows you a CNAME record for k1._domainkey.yourdomain.com pointing to dkim.mcsv.net.
Add the CNAME to DNS
In your DNS provider, add the CNAME record exactly as shown. The host is k1._domainkey (add your domain if the provider doesn't auto-append it).
Update SPF record
Add include:servers.mcsv.net to your existing SPF record. If you don't have one, create: v=spf1 include:servers.mcsv.net ~all
Authenticate in Mailchimp
Return to Mailchimp and click Authenticate. DNS propagation may take up to an hour.
Copy-ready records: Use the DNS Record Builder — select this service from the dropdown and enter your domain to get all records formatted and ready to copy.
After Adding Records
DNS changes can take anywhere from a few minutes to 24 hours to propagate. Use the DNS Propagation Checker to verify your records are live globally, then return to the service's admin console to verify domain ownership.
It's strongly recommended. Without it, your emails show as sent 'via mcsv.net', and spam filters may score them lower since they can't verify your domain's authorization.
Yes — a CNAME for DKIM and an SPF update. Mailchimp doesn't require MX records since it only sends email, not receives it.
No. Authentication improves deliverability for future sends. Your audience and campaign data are unaffected.