Fix guide
How to Fix DMARC Alignment for Mailchimp
Mailchimp requires a custom sending domain setup to pass DMARC alignment. Without it, Mailchimp sends from @mailchimpapp.com, failing alignment with your From: domain.
Why alignment fails
Mailchimp requires domain verification via CNAME or TXT, then DKIM-style records for authenticated sending. Marketing vs Mandrill (transactional) uses separate authentication flows. See DMARC alignment.
Exact DNS records
Values are generated per account. You will typically add verification TXT/CNAME, then DKIM CNAMEs shown in Account → Domains:
Step-by-step fix
Verify alignment and DNS in your browser
Open DNS Preflight →FAQ
Why does Mailchimp fail DMARC alignment?
Without a verified custom sending domain, Mailchimp uses its own infrastructure domains for signing and bounce handling, which do not align with your From: domain.
What is the difference between Mailchimp and Mandrill auth?
Mailchimp marketing domains are configured in Account → Domains. Mandrill (transactional) requires a separate domain setup in the Mandrill dashboard with its own DNS records.
How do I verify Mailchimp domain authentication?
Complete all CNAME and TXT steps in Mailchimp, then verify green checks in the dashboard. Use DNS Preflight to double-check DKIM and SPF records publicly.
What are common Mailchimp DNS mistakes?
Wrong host names, typos in CNAME targets, or verifying only marketing while Mandrill still uses an unauthenticated domain for transactional mail.
Does Mailchimp work with DMARC p=reject?
Yes once DKIM and SPF alignment pass for your sending domain. Start with p=none or quarantine and monitor aggregate reports before moving to reject.