Mailchimp
Mailchimp SPF record: how to set up DKIM and DMARC
The Mailchimp SPF record explained: add the two DKIM CNAMEs and the DMARC TXT record Mailchimp asks for, then confirm that DMARC passes.
Check your current setup:
The Mailchimp SPF record has a simple answer: Mailchimp's current setup does not ask you to publish one. To authenticate your domain, it asks for two DKIM CNAME records and one DMARC TXT record. Follow the steps below to add them and confirm that DMARC passes.
How Mailchimp authenticates your mail
SPF (Sender Policy Framework) lists the servers allowed to send for a domain. Receiving servers compare that list with the envelope sender, also called the Return-Path. This hidden address collects bounces. Mailchimp says it is based on its sending servers and usually contains mcsv.net, mcdlv.net, mailchimpapp.net or rsgsv.net.
DMARC (Domain-based Message Authentication, Reporting and Conformance) passes when SPF or DKIM passes on a domain that matches your From address (RFC 9989 §5.3.5). That match is called alignment (RFC 9989 §4.4). SPF can pass on Mailchimp's domain, but that domain differs from yours. SPF therefore does not align.
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message. After you authenticate your domain, the signature carries your domain and DMARC can pass through DKIM. Until then, Mailchimp authenticates your mail with its own domain.
Step 1: Verify your sending domain
Verification proves that you can read mail at an address on the domain. Mailchimp requires it and says it does not change delivery by itself.
- Click your profile icon and choose Account & billing.
- Click Domains.
- In the Email Domains section, click Add & Verify Domain.
- Enter an address on your domain and click Send Verification Email.
- Click Verify Domain Access in the message, or enter the code in the pop-up and click Verify.
The link and the code expire after seven days. A subdomain such as news.example.com needs its own verification.
Step 2: Start domain authentication
- On the Domains page, click Start authentication next to the verified domain. Account Managers open this page through Account instead of Account & billing.
- In Select your domain provider, open the Select your DNS provider list, choose your provider and click Next.
Mailchimp also offers this step from the Home screen checklist and from the From field of the email builder.
Mailchimp recommends Entri, a service that connects to your DNS provider and creates the records for you. Click Continue, then Log in, and wait for the message that the records were created.
To do it by hand, click Or manually authenticate your domain, select your provider or Other, and click Next. Steps 3 and 4 cover the manual path.
Step 3: Add the Mailchimp DKIM records
A CNAME record makes one DNS name point to another. Mailchimp shows two of them as CNAME 1 and CNAME 2, each with a Name (Host) and a Value. Copy both into your DNS panel. Go back to the Domains page and click Next.
The part of the name before ._domainkey is the selector, the label a receiver uses to find the right DKIM key. Mailchimp's help shows k2._domainkey as an example name and does not publish the full pairs, so copy the exact values from your account. Once they are live, check them with the DKIM checker.
Step 4: Add the Mailchimp DMARC record
DMARC tells receivers how to treat mail that fails these checks and where to send reports about it. It lives in a TXT record, a DNS entry that holds plain text. Mailchimp's manual flow shows the host, _dmarc, and the value to use.
Google requires DKIM and DMARC from senders of more than 5,000 messages daily to personal Gmail accounts. Yahoo requires them for bulk senders but publishes no fixed numerical threshold. Configure both for your sending domain.
If the domain has no DMARC record, create one with the value Mailchimp shows. To receive reports, make sure it has a rua tag, which names the mailbox that collects them:
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
With p=none, you ask for reports and do not ask receivers to act on failures. RFC 9989 §5.1.4 describes this as the usual starting point. If you use DMARC Pulse, put your DMARC Pulse address in rua.
If the domain already has a DMARC record, do not add another and do not overwrite it with the value Mailchimp shows. Keep its p= value. Change it only to add a rua address, separated by a comma from any address already there. Return to the Domains page and click Next. Mailchimp starts checking your records.
Step 5: What to do with the Mailchimp SPF record
Mailchimp's setup article lists what it needs: 2 CNAME records for DKIM and 1 TXT record for DMARC. SPF is not on that list, so you do not need to change your SPF record for Mailchimp campaigns.
A general Mailchimp article about SPF says third-party services such as Mailchimp must appear in your include statement. It gives no value to use for campaigns.
Many third-party guides cite include:servers.mcsv.net. Mailchimp's help pages on domain authentication do not mention that value. If your record already has it, you can leave it there. It uses one of the 10 DNS lookups SPF allows (RFC 7208 §4.6.4). It cannot make SPF align, because receivers check SPF against the envelope sender on Mailchimp's domain.
If you edit SPF for another reason, keep a single record on the domain. A second SPF record causes a permanent error (RFC 7208 §4.5). The SPF checker shows what you have published.
Step 6: Confirm that it worked
Most records update within a few minutes, but validation can take up to 48 hours. Mailchimp emails you when it finishes. The domain shows Authentication in progress while it waits and Authenticated when it succeeds.
Send a test message and inspect the results added by your receiving provider. Confirm dkim=pass and dmarc=pass; read d= in the corresponding DKIM-Signature for the actual signing domain and s= for the selector. header.i is the AUID and can contain an address or subdomain; it is not DMARC’s alignment input, especially under adkim=s.
Step 7: Move toward enforcement slowly
Aggregate reports are XML summaries that receivers send to your rua address (RFC 9990). In DMARC Pulse, expect Mailchimp to appear with DKIM aligned and SPF not aligned. That result is normal for this provider.
Preserve any existing policy and report destinations. For a first deployment, monitor at p=none. After every legitimate sender passes with alignment, assess p=quarantine. Consider p=reject separately, including mailing-list and forwarding risks; it is optional. Receivers decide how to handle individual messages.
Common problems
- The CNAME name has your domain twice. Some DNS panels add your domain automatically. If
k2._domainkey.example.comturns intok2._domainkey.example.com.example.com, enter onlyk2._domainkey. - Authentication does not finish. Correct records can take up to 48 hours to validate. After that, compare each record with your Mailchimp screen and use Resolve or Restart authentication.
- Cloudflare changes the CNAME. Set both records to DNS only (gray cloud). Cloudflare also warns that CNAME flattening can stop email providers from reading a record, so turn it off for these names.
- The domain has two DMARC records. Mailchimp asks for a TXT record at
_dmarc. If one already exists, a second record makes receivers discard both. Keep only one (RFC 9989 §4.10). - You changed the CNAMEs after authenticating. Mailchimp stores your authentication when you set it up, and later changes can conflict with it. Disable authentication on the Domains page, change the records, then authenticate again. While authentication is off, your mail loses your domain's DKIM signature and fails DMARC. At
p=quarantineorp=reject, pause campaigns until the domain shows Authenticated again. - Your From address is on Gmail or Yahoo. Mailchimp cannot verify or authenticate public domains. It may replace the From domain with
send.mailchimpapp.comormail.mailchimpapp.com. Replies still reach your address, but the domain shown is Mailchimp's. Send from a domain you own. - Inboxes still show
via mailchimpapp.net. Authenticating your own domain removes this in most email clients. Mailchimp notes that some, such as Outlook, may still show it after custom DKIM is set up. - The verification email does not arrive. Add
accountservices@mailchimp.comto your safe senders. If you asked more than once, use the most recent message. Your IT team can also allowlist the delivery IPs Mailchimp publishes. - Reports still show Mailchimp as unaligned. Reports cover a past period, so messages sent before authentication finished still appear. Compare the report dates with the day the domain became Authenticated.
- Mailchimp Transactional (Mandrill) has its own setup. It uses different CNAMEs:
mte1._domainkeypoints todkim1.mandrillapp.comandmte2._domainkeypoints todkim2.mandrillapp.com. It will not send from a domain that lacks verification, a valid DMARC policy and DKIM records. See Mailchimp Transactional.