Skip to content
DMARC Pulse

Email senders

Mandrill DMARC setup: DKIM, SPF and return-path

Mandrill needs DKIM and a DMARC record before it sends. See how Mailchimp Transactional signs your mail and why its default return-path does not align.

SPF include for Mailchimp Transactional (Mandrill)

Resolves in DNS
Add to your SPF recordTXT
include:mandrillapp.com

Mailchimp Transactional (Mandrill) does not require this include. If you use it, add it to the SPF record you already have: a domain must publish only one.

DNS lookups it uses
2 of 10
Needed in your SPF record
No
Last checked in DNS
2026-11-11

DKIM for Mailchimp Transactional (Mandrill)

Selectors
mte1 mte2 mandrill
How to enable it
Two CNAME records on your domain: mte1._domainkey points to dkim1.mandrillapp.com and mte2._domainkey points to dkim2.mandrillapp.com. The first-send guide also describes one TXT record at mandrill._domainkey, so follow what View DKIM settings shows for your domain.

Mailchimp Transactional (Mandrill) signs with your domain

The signature carries your domain in d=, so DKIM can align with your From address and pass DMARC on its own.

Envelope-from and SPF alignment

SPF counts for DMARC only when this domain matches the domain in your From address. If it is Mailchimp Transactional (Mandrill)’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.

Envelope-from (Return-Path)
mandrillapp.com by default, or a subdomain of yours set up as a return-path domain

Sending ranges of Mailchimp Transactional (Mandrill)

Use these to recognize Mailchimp Transactional (Mandrill) in your reports. They change over time, so do not copy them into your SPF record.

8 of 13
  • 198.2.176.0/20
  • 198.2.132.0/22
  • 198.2.136.0/23
  • 198.2.178.0/23
  • 198.2.186.0/23
  • 205.201.136.0/23
  • 198.2.128.0/24
  • 198.2.145.0/24

Updated 2026-11-15

Does your domain authorize Mailchimp Transactional (Mandrill)?

Enter your domain. The SPF Checker reads your record and names the senders it authorizes.

Mailchimp Transactional (Mandrill) documentation

Mandrill DMARC setup happens on the Sending Domains page of Mailchimp Transactional, the product also known as Mandrill. Mailchimp will not send from a domain until it is verified and has valid DKIM records and a DMARC policy.

How it authenticates

DKIM is the signature a receiver checks against a public key in DNS. You publish two CNAME records under your own domain, using the selectors mte1 and mte2. Because those names sit on your domain, the signature can align with your From address.

DMARC is a TXT record named _dmarc. Mailchimp accepts a monitoring policy:

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

If your domain already has a _dmarc record, keep it and do not publish a second. Read your reports under p=none before you tighten the policy.

The return-path receives bounces and is the domain checked by SPF. Its default mandrillapp.com does not align with your From domain, so DMARC relies on DKIM. For SPF alignment too, point an unused bounce.example.com subdomain to mandrillapp.com with a CNAME and add it under Tracking & Return Path Domains. A CNAME cannot share a name with other records; leave occupied names alone.

What to watch for

An SPF include on your root domain does not create alignment here, because receivers check the return-path domain instead. Mailchimp's Transactional setup pages do not ask for one.

Mailchimp's own pages disagree on DKIM. The authentication docs and the December 2023 changelog entry use the two CNAME records, while the first-send guide also describes one TXT record at mandrill._domainkey. Copy what View DKIM settings shows, then confirm it with the DKIM checker.

The return-path must be a subdomain, and it can belong to only one Transactional account. With aspf=s in your DMARC record, a return-path on a subdomain does not align with a From address on the parent domain, so DKIM carries the result alone.

Mailchimp warns that some DNS hosts add your domain after _dmarc automatically. Check that it does not appear twice before you click Test DNS Settings.

Check it now

Find and validate DKIM keys

Frequently asked questions

Do I need to add Mandrill to my SPF record?
DMARC does not need it. Mailchimp's Transactional setup docs list DKIM, DMARC and domain verification, and they never mention SPF. A general Mailchimp article shows include:mandrillapp.com if you choose to publish it.
What are the Mandrill DKIM selectors?
The authentication docs use mte1 and mte2, published as two CNAME records. Mailchimp's first-send guide also describes a TXT record at mandrill._domainkey, so copy what View DKIM settings shows for your domain.
Why was my Mandrill message rejected as unsigned?
Mailchimp says an unsigned rejection means the sending domain has not been properly set up. Check DKIM, DMARC and domain verification on the Sending Domains page, then click Test DNS Settings.
Does the default Mandrill return-path align with DMARC?
No. It defaults to mandrillapp.com, which is a different domain from yours. DKIM can still pass DMARC. For a second route, set up a return-path on a subdomain of your own domain.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.