Mailchimp Deliverability:
Shared Infrastructure, Monitoring Gaps, and What to Watch

Mailchimp's Sending Infrastructure

Mailchimp is the world's most widely-used email marketing platform, with an estimated 11 million active accounts. That scale means Mailchimp operates one of the largest email sending infrastructures in existence — a massive fleet of IP addresses organized into pools, routing billions of emails per month.

By default, all Mailchimp accounts (including free) send from shared IP pools. Mailchimp segments these pools by account quality and plan level, so paid accounts and accounts with better engagement history generally use better-quality pools than brand-new or free accounts. However, the fundamental dynamic remains: your mail shares an IP address with other Mailchimp senders, and their behavior affects your IP reputation.

Mailchimp maintains a compliance team that monitors for abuse and removes accounts exceeding certain bounce and complaint thresholds. The platform automatically suspends accounts that:

• Exceed a hard bounce rate of 3%
• Receive complaint rates over 0.3% (below Mailchimp's published thresholds)
• Send to purchased lists or harvested addresses

Mailchimp Pro plan and high-volume paid accounts can request dedicated IPs at approximately $30/month. Dedicated IPs on Mailchimp require approval and a warm-up process similar to other ESPs.

What Mailchimp Handles for Deliverability

Mailchimp's platform includes several deliverability safeguards that run automatically in the background. Many Mailchimp users don't realize how much is being managed for them until they migrate to a more developer-focused ESP like AWS SES and have to build it all themselves.

Bounce Processing

Mailchimp automatically suppresses email addresses that hard bounce — meaning the address doesn't exist or permanently rejects mail. After the first hard bounce, the address is added to the account's suppression list and never contacted again. Soft bounces (temporary failures like a full inbox) are tracked but only result in suppression after repeated failures.

Unsubscribe Management

Mailchimp processes unsubscribes automatically and globally. When a contact unsubscribes from any campaign, they're added to a suppression list that prevents future campaigns from reaching them. Mailchimp's List-Unsubscribe header implementation also enables one-click unsubscribe in Gmail and Outlook — this is handled automatically and cannot be disabled.

DKIM Authentication

By default, Mailchimp signs all outbound mail with DKIM using Mailchimp's domain (mcsv.net). This provides authentication, but the DKIM signature is from Mailchimp's domain rather than yours. For proper DMARC alignment, you should configure a custom sending domain (see Authentication Configuration below) so the DKIM signature matches your From domain.

Standard Analytics

Mailchimp's campaign reports include: open rate, click rate, bounce rate (hard and soft), unsubscribe rate, and spam complaint rate (for complaints processed through Mailchimp's feedback loop connections). These metrics are valuable for list health monitoring — but they don't tell you about ISP-level deliverability signals.

Mailchimp's Deliverability Monitoring Gaps

The most important thing to understand about Mailchimp's reporting is the distinction between what Mailchimp measures and what actually determines inbox placement. Mailchimp measures what happens at the level of its own servers and feedback loops. ISPs like Gmail and Yahoo operate their own reputation systems that Mailchimp has no window into.

The Gmail Disconnect

Gmail handles approximately 40-50% of consumer email in many English-speaking markets. Gmail's spam filtering operates on domain reputation scores maintained in Google Postmaster Tools — and these scores can be completely disconnected from what Mailchimp reports as your complaint rate.

Gmail doesn't operate a traditional feedback loop where it sends complaint data to ESPs. Instead, Gmail measures what percentage of received mail gets marked as spam by its users, and it surfaces this via the Postmaster Tools API. Mailchimp has no access to this data. Your Gmail spam rate as measured by Google can be trending upward for weeks before it manifests as a visible drop in your Mailchimp open rate metrics.

Missing Data Points

• Google Postmaster domain reputation — High / Medium / Low / Bad score for your sending domain at Gmail
• Gmail spam rate — Percentage of your mail marked as spam by Gmail users (Mailchimp's complaint rate ≠ this number)
• Yahoo complaint rate — Yahoo Sender Hub provides this, but Mailchimp doesn't integrate with it
• Inbox vs. spam vs. promotions placement — No seed list testing in Mailchimp
• DMARC alignment status — Whether your mail is passing DMARC at receiving servers
• Blacklist status — No automatic blacklist monitoring for your sending IPs or domain
• Bot click separation — Mailchimp's click rate includes automated scanner clicks that inflate engagement metrics

Put side by side, the disconnect is obvious: the signals Gmail actually filters on are not the signals Mailchimp puts in front of you.

Authentication Configuration in Mailchimp

Proper authentication is the foundation of deliverability, and Mailchimp's default authentication setup is adequate but not optimal. Here's how to configure each component correctly.

Setting Up a Custom Sending Domain

1. Go to Account → Settings → Domains in Mailchimp
2. Click Verify a Domain and enter your sending domain
3. Mailchimp provides a verification email to confirm domain ownership
4. After verification, go to Authenticate and add the provided CNAME records to your DNS
5. These CNAME records enable Mailchimp to sign your mail with your domain's DKIM
6. Once DNS propagates, your From address can use your domain with proper DKIM alignment

Mailchimp SPF Record Setup

Mailchimp's servers need to be included in your SPF record to pass SPF checks. The SPF record Mailchimp needs is a single TXT record on your sending domain that lists Mailchimp's sending servers alongside any other service that sends mail for you. Mailchimp shows the exact value for your account in its authentication settings, so copy it from there. A domain can publish only one SPF record, so add Mailchimp to the existing one instead of creating a second.

SPF alone isn't sufficient for DMARC alignment, because DKIM alignment is also required. Use InboxEagle's SPF Record Generator to build a combined record, and the SPF Record Checker to confirm what is live. If you manage several domains, each sending domain needs its own SPF record with its own Mailchimp entry.

Mailchimp DKIM Setup

Mailchimp DKIM setup is the CNAME step above. By default Mailchimp signs with its own domain, so the DKIM signature does not match your From address. After you add the CNAME records, Mailchimp signs with your domain and DMARC can align. The DKIM Record Checker shows whether the records resolve.

• For SPF, Mailchimp sends from its own servers, so your SPF record must include them or SPF fails.
• For DKIM, Mailchimp signs mail with the key you publish through the CNAME records, which is what lets DMARC align on your own domain.

Publishing a DMARC Policy

After configuring custom DKIM and SPF, publish a DMARC record to your DNS. Use InboxEagle's DMARC Record Generator to create the correct TXT record. Start at p=none to collect alignment data without affecting delivery, then advance to p=quarantine once you've confirmed all your sending sources are properly aligned.

Shared IP Neighbor Risk in Mailchimp

Mailchimp's scale is its primary shared IP risk factor. The platform's free tier, which removes many sending quality barriers, attracts a wide range of sender quality. While Mailchimp's compliance team works to remove bad actors, the sheer volume of accounts means some low-quality senders are always cycling through the pools.

Free Tier vs. Paid Tier IP Pools

This is the most actionable piece of information about Mailchimp's shared IP structure: free accounts and paid accounts use different IP pools. ISPs — particularly Gmail and Outlook — have historical data on the quality distribution of senders from different Mailchimp IP ranges. Mailchimp's free-tier IP ranges carry a historically higher proportion of low-quality senders, which ISPs factor into their filtering decisions.

If you're on Mailchimp's free plan and experiencing deliverability issues — particularly elevated promotions tab placement or spam folder placement — upgrading to a paid plan that uses higher-quality IP pools is worth testing. The cost of a paid plan is often less than the revenue impact of degraded inbox placement.

When Shared IP Problems Manifest

Shared IP reputation damage from a co-tenant typically manifests as:

• Sudden spike in soft bounces (receiving servers temporarily deferring mail)
• Increased spam placement without any change in your own sending patterns
• Temporary blacklist appearance for a Mailchimp IP that routes your mail

On Mailchimp's paid pools, these events are usually resolved within hours as their abuse team responds. On free-tier pools, resolution may take longer. The way to detect these events early: active monitoring via inbox placement testing and blacklist monitoring.

Mailchimp SPF and DKIM FAQ

How do I set up DKIM and DMARC for Mailchimp?

In Mailchimp, go to Account, then Settings, then Domains, verify your sending domain, then open Authenticate and add the CNAME records Mailchimp provides to your DNS so mail is signed with your own domain's DKIM. Once DNS propagates, publish a DMARC TXT record at _dmarc.yourdomain.com, starting at p=none to collect data, and move to p=quarantine after every sending source is aligned. InboxEagle's free DMARC Record Generator builds the record.

Do I need SPF for Mailchimp?

Yes. Mailchimp's sending servers need to be included in your SPF record for SPF to pass, but SPF alone is not enough for DMARC. DMARC needs SPF or DKIM to align with your From domain, and Mailchimp's default DKIM signature is on its own domain, so a custom Mailchimp DKIM setup is also required for reliable alignment.

Where do I find my Mailchimp SPF record?

Mailchimp shows the SPF details for your account in its authentication settings, so copy the include from there instead of a third-party page. Add it to the single SPF record already published on your sending domain, because a domain can only have one SPF record. Mailchimp SPF records on a multi-domain account follow the same rule, one record per sending domain.

Is the Mailchimp delivery rate the same as inbox placement?

No. The Mailchimp delivery rate counts mail the receiving server accepted over SMTP. A message can be accepted and still land in spam or the Promotions tab, so a high delivery rate says nothing about the folder. A seed list test shows the folder at Gmail, Yahoo, AOL and Outlook.

Is there a DMARC Mailchimp setting I need to turn on?

No. DMARC is a DNS record you publish on your own domain, not a switch inside Mailchimp. Mailchimp handles the SPF and DKIM side through its domain authentication, and you then publish a DMARC record at _dmarc.yourdomain.com, usually starting at p=none before you tighten the policy. The free DMARC record generator builds the record, and InboxEagle checks the DMARC policy record every 24 hours and alerts on change.

What does Mailchimp SPF configuration involve?

Mailchimp SPF configuration means authorizing Mailchimp to send for your domain in your domain's SPF record. Check Mailchimp's documentation for the current include value, add it to your existing SPF record instead of creating a second one, and verify the result with the free SPF record checker.

Monitoring Mailchimp Deliverability With InboxEagle

InboxEagle provides the external monitoring layer that Mailchimp's platform cannot offer. Because InboxEagle monitors your sending domain and the ISP-level signals directly — not through Mailchimp's servers — it captures the deliverability data that Mailchimp has no window into.

Google Postmaster Tools Integration

InboxEagle connects to Google Postmaster Tools on your behalf and surfaces your Gmail domain reputation score, spam rate, and authentication pass rates. These are the signals Gmail uses to filter your mail — and they often diverge significantly from what Mailchimp's dashboard reports.

Yahoo and AOL Placement Testing

Yahoo Sender Hub is Yahoo's own tool for complaint rate data on Yahoo and AOL recipients. InboxEagle does not connect to it. Instead, its Yahoo and AOL seed mailboxes show whether each send lands in the Inbox or Spam, so you see a placement drop at those providers even before you receive formal warnings.

Inbox Placement Testing Across Providers

InboxEagle's seed list testing sends your Mailchimp campaigns to a network of real email accounts at Gmail, Yahoo, AOL, and Outlook, then reports exactly where each email lands. This separates your actual inbox placement rate from Mailchimp's open rate, which conflates placement quality with subscriber engagement.

DMARC Record Monitoring

After configuring your custom domain in Mailchimp, InboxEagle's DMARC monitoring checks your DMARC policy record every 24 hours and alerts you on any change, so an accidental edit does not go unnoticed. Processing the aggregate reports ISPs send, to see which streams align, is a separate product, DMARC Processing.