Sender Identity

Home · Guides · Mailchimp / Mandrill

ESP · Mailchimp

Mailchimp and Mandrill: authenticated domain records.

22 October 2026

This guide covers Mailchimp / Mandrill: where to copy SPF and DKIM values, how to publish them at your DNS provider, and how to point DMARC aggregate reports at a mailbox you control—or at Hosted DMARC on Sender Identity.

Before you change DNS

  1. Run the free static audit and keep a copy of the current SPF and DMARC text.
  2. List every system that already sends as this domain (office mail, billing, marketing, tickets).
  3. Prefer one organizational-domain DMARC record. Subdomain records override the org policy when present.

Where to copy the values

  1. Mailchimp → Domains / authenticate domain, or Mandrill → sending domains.
  2. Copy the DKIM CNAME or TXT and the SPF include Mailchimp shows (often Mandrill uses include:spf.mandrillapp.com and selector mandrill).
  3. Publish at your DNS provider and wait for Mailchimp’s verifier.

Typical DNS shape

TypeName / hostValue / points toNote
TXT@v=spf1 include:spf.mandrillapp.com -allMerge with existing includes; stay under 10 DNS lookups.
CNAMEmandrill._domainkey(value from Mailchimp / Mandrill)Confirm the exact host in the console.

DMARC aggregate reports

Two workable patterns:

The free audit suggests a starter p=none record for your own mailbox. It never writes p=reject and never points rua at reports.senderidentity.com—that only happens on the paid hosted path.

Verify

  1. Wait for DNS, then run the free audit. Add any unusual DKIM selector under “DKIM selectors” if the default probe list misses it.
  2. Sender Identity’s vendor catalog can label known includes and selectors in paid monitoring; labels never publish DNS for you.
  3. Keep p=none until aggregate reports show only senders you recognize, then stage quarantine and reject in Account.