Providers

Mailchimp SPF Setup

Mailchimp sends from its own infrastructure and requires SPF authorization via include or authenticated sending domain configuration.

Beginner · 5 min read · Reviewed Jul 4, 2026

Quick answer

Mailchimp sends marketing email from its own SMTP infrastructure, requiring your domain SPF record to include Mailchimp authorization macros or to use Mailchimp authenticated domains with aligned DKIM and SPF on the bounce domain. Modern setups often use a campaign-specific return-path domain. Verify both root and sending subdomain policies when configuring Mailchimp alongside employee mail providers.

Beginner explanation

Mailchimp is one of the most common reasons marketing and IT teams first edit SPF together. Campaign mail does not leave your Microsoft or Google tenant; it originates from Mailchimp servers using a bounce domain configured in your account.

Depending on your setup, you may add a Mailchimp include to your primary SPF record or publish SPF on a dedicated sending subdomain used only for campaigns. Mailchimp's authenticated domain feature walks you through the required DNS entries.

SPF for Mailchimp is not a set-and-forget step. Domain authentication should be re-verified after major DNS migrations or when you change the From address domain for branding.

Technical explanation

Mailchimp documentation typically instructs customers to add include:servers.mcsv.net or newer equivalents to the SPF record on the domain used for campaign MAIL FROM addresses. DKIM CNAME or TXT records are published in parallel for alignment.

When you authenticate a domain in Mailchimp, the wizard shows exact DNS values. The bounce domain may differ from your website apex—for example, k1._domainkey and related SPF entries might target a subdomain while employee mail uses the root.

If you send high volume, combine Mailchimp authorization with DMARC monitoring to catch alignment failures early. SPF pass alone does not guarantee inbox placement if DKIM or DMARC alignment fails due to From domain mismatches.

Business impact

Mailchimp SPF failures hit marketing KPIs directly: lower inbox placement, higher bounce rates, and damaged sender reputation for promotional domains. Sales campaigns and newsletters underperform while analytics blame subject lines instead of authentication.

Because Mailchimp is often the first non-employee sender added to SPF, misconfiguration also pushes domains toward lookup limits that later break employee mail authentication.

Common mistakes

- Adding Mailchimp includes to the wrong hostname when authenticated domains use a subdomain bounce path
- Removing Mailchimp DNS entries while pausing campaigns, then launching again without re-verification
- Assuming Google or Microsoft SPF includes cover Mailchimp because the From display name shows your brand

How SPF Manager helps

SPF Manager recognizes Mailchimp include patterns and validates them against Mailchimp's current authenticated domain requirements. It shows whether campaign bounce domains have separate SPF needs from employee mail.

Before a major send, you can confirm lookup budget and DMARC alignment paths so authentication does not fail under launch traffic.