Lorixen.
EN

Authenticating Your Domain in Mailchimp or Brevo: Custom Sending Domain Setup

Short answer: Both Mailchimp and Brevo give you a short list of DNS records to add for your sending domain: DKIM records (usually CNAMEs) that let them sign mail with your domain, sometimes a TXT verification code, and a check that a DMARC record exists. Copy each record exactly into your DNS host, switch off the Cloudflare proxy for any CNAME, then press verify in the platform. Once DKIM passes with your domain, DMARC aligns and you can gradually tighten your DMARC policy. You rarely need to add the platform to SPF, which helps you stay under SPF's ten-lookup limit.

Why authentication matters for newsletters

Without your own authentication, a campaign from news@yourshop.co.uk is signed by the platform's domain rather than yours. Mailbox providers see a mismatch between the visible From address and the domain that vouches for the message. Large inbox providers now expect bulk senders to authenticate properly and publish a DMARC record, so unauthenticated newsletters drift into spam or get rejected.

Authenticating also means the "via" or "on behalf of" note some mail clients show next to your name usually disappears.

What each platform asks for

Exact hostnames and values are generated for your account, so always copy them from the platform rather than from an article.

Mailchimp

In Mailchimp, go to your account settings, then Domains. Add and verify the email address on your domain, then choose Start Authentication. Mailchimp shows records to add, typically:

  • Two CNAME records for DKIM, with hostnames ending in ._domainkey
  • A DMARC TXT record at _dmarc if you do not already have one

Mailchimp's domain authentication help page explains each record and shows provider-specific notes.

Brevo

In Brevo, open Senders, Domains and Dedicated IPs, then the Domains tab, and add your domain. Brevo usually lists:

  • A TXT record containing a Brevo verification code
  • DKIM records, currently CNAMEs in most new accounts, though older setups may show a TXT key
  • A DMARC record recommendation

Brevo can also connect automatically to some DNS providers, but adding records manually gives you full control and a record of what changed.

Adding the records at common DNS hosts

Most small businesses manage DNS in one of these places:

Where DNS lives Where to add records
Cloudflare Domain, DNS, Records, Add record
GoDaddy My Products, Domain, DNS
123 Reg, IONOS, Namecheap Domain list, Manage, DNS or Advanced DNS
Hosting control panel (cPanel) Zone Editor
Microsoft 365 or Google Domains successors The registrar now holding the domain

Practical tips that save a second round:

  1. Hostname format. Some hosts want only the part before your domain, such as k2._domainkey. Others accept or require the full name. If you paste the full name into a host that adds the domain automatically, you end up with k2._domainkey.yourshop.co.uk.yourshop.co.uk, which never verifies.
  2. Trailing dots. Some panels need a trailing dot on CNAME targets, others strip it. Follow the panel's own examples.
  3. Cloudflare proxy off. In Cloudflare, every CNAME you add for DKIM must be set to DNS only, the grey cloud. A proxied CNAME returns Cloudflare's addresses instead of the platform's key, and verification fails.
  4. One DMARC record only. If _dmarc already exists, edit it instead of adding a second. Two DMARC records count as none.

Verifying

DNS changes often show up within minutes, but can take longer depending on the record's time to live. Back in the platform, press Verify or Authenticate. If it fails:

  • Use a public DNS lookup tool to query the exact hostname and confirm the value matches.
  • Look for typos, extra spaces or a doubled domain name.
  • Check you edited DNS at the provider your nameservers actually point to. Many owners edit records at the registrar while DNS is hosted at Cloudflare or a web host.

After it verifies, send a test campaign to a Gmail address, open the message, choose Show original, and confirm DKIM shows PASS with your domain.

DMARC alignment and stepping up your policy

DMARC passes when either SPF or DKIM passes and that domain matches the From domain. For newsletter platforms, DKIM alignment is what matters, because the bounce address usually stays on the platform's domain.

A sensible progression:

  1. Start with monitoring: v=DMARC1; p=none; rua=mailto:dmarc@yourshop.co.uk
  2. Read the reports for a few weeks. Make sure every service that sends as your domain, such as your mailbox provider, invoicing tool, shop platform and newsletter, shows aligned passes.
  3. Move to quarantine with a percentage, for example p=quarantine; pct=25, then increase.
  4. Consider reject only once nothing legitimate is failing.

Report files are hard to read raw, so a free DMARC report viewer or a mailbox rule that collects them helps.

Keeping SPF under the lookup limit

SPF allows only ten DNS lookups when a receiving server evaluates your record, as defined in the SPF specification, RFC 7208. Every include: counts, and nested includes inside them count too. Owners often add every tool they have ever used, then SPF returns a permanent error and stops helping at all.

Because Mailchimp and Brevo authenticate through DKIM and their own bounce domain, you generally do not need to add them to SPF unless the platform specifically tells you to for your setup. Review your SPF record and remove includes for services you no longer use.

FAQ

Do we need a separate subdomain for newsletters?

It is optional. Some businesses send marketing from a subdomain like news.yourshop.co.uk to keep its reputation apart from day-to-day mail. Both platforms support either approach.

Why does Mailchimp still say our domain is not authenticated?

Usually a CNAME is proxied in Cloudflare, the hostname has the domain twice, or the records were added at the wrong DNS provider. Query each record publicly to check.

Can we use a free Gmail or Outlook address as the sender?

Not reliably. Those domains publish strict DMARC policies, so mail claiming to be from them via a newsletter platform fails. Use an address on your own domain.

Should we set DMARC to reject straight away?

No. Start with monitoring, confirm all legitimate senders pass, then tighten in steps.

Newsletters still landing in spam after all this? Contact us and we will review your sending setup record by record.

Sources

WhatsAppBook a call