Mailchimp always sends with its own bounce domain, so your SPF record never decides whether its mail passes — DKIM does. Domain authentication is two CNAME records, k2 and k3, plus a DMARC record, which Gmail and Yahoo require from bulk senders.
| SPF | Not needed |
| DKIM | CNAMEs k2 and k3 |
| Bounce domain | Mailchimp’s own — SPF never aligns |
| Set up in | Profile menu → Account & billing → Domains |
Is your domain set up for Mailchimp?
We read your SPF record, look for Mailchimp’s DKIM key and check DMARC. Nothing is stored.
SPF for Mailchimp
Mailchimp’s bounce (Return-Path) address is always its own — Mailchimp says it “usually contains mcsv.net, mcdlv.net, mailchimpapp.net, or rsgsv.net”. SPF is checked against that domain, not yours, and Mailchimp’s current setup guide asks for no SPF record. An include:servers.mcsv.net left over from older instructions spends a lookup and decides nothing for Mailchimp mail.
DKIM for Mailchimp
In Mailchimp, open the profile menu → Account & billing → Domains, verify the domain, then choose Authenticate. It lists two CNAME records and one TXT record; you can let Mailchimp publish them through your DNS provider, or add them by hand.
Until the domain is authenticated, Mailchimp signs with its own domain and recipients see “via mailchimpapp.net” or “on behalf of mcsv.net”.
| Name | Type | Value |
|---|---|---|
k2._domainkey | CNAME | <value from your Mailchimp account> |
k3._domainkey | CNAME | <value from your Mailchimp account> |
_dmarc | TXT | v=DMARC1; p=none; … (only if you have none) |
The exact values come from Mailchimp; copy them from there. Placeholders are in angle brackets.
Bounce domain and DMARC
Because SPF can never align, Mailchimp mail passes DMARC only on DKIM. Keep both k2 and k3 published before moving your policy past p=none. If you already have a DMARC record, keep it — a domain may have only one.
No DMARC record yet? Start with one that only reports, read the reports for a couple of weeks, then tighten it: build it with the DMARC generator.
Common mistakes
- Record names duplicated by the DNS host: k2._domainkey.yourdomain.com.yourdomain.com. Enter only k2._domainkey.
- Sending from a Gmail or Yahoo address: those cannot be authenticated, and Mailchimp rewrites the From address to one of its own.
- Adding a second DMARC record because the setup screen shows one.
Questions
Should I add include:servers.mcsv.net to my SPF record?
No. Mailchimp’s bounce address is its own, so that include is never used for Mailchimp mail; it only spends one of your ten SPF lookups.
Sources
Checked against Mailchimp’s own documentation on 25 September 2026:
- Set Up Email Domain Authentication — mailchimp.com
- My Email From Name Shows “mailchimpapp.net” or “mcsv.net” — mailchimp.com