Skip to content
DMARC Pulse
Guides

Brevo (Sendinblue)

How to set up SPF, DKIM and DMARC for Brevo (Sendinblue)

Set up SPF, DKIM and DMARC for Brevo: add the Brevo code, two DKIM CNAMEs and one DMARC record, and learn when SPF matters on a dedicated IP.

How Brevo authenticates your mail

To set up DMARC for Brevo, you authenticate your domain so that Brevo signs your mail with it. DMARC checks whether a message passes SPF or DKIM on a domain that matches the From address. That match is called alignment.

Brevo's shared IPs are the default. On shared IPs without a branded subdomain, your mail passes SPF on Brevo's own return-path domain. The return-path is the address that receives bounces. Because that domain belongs to Brevo, SPF does not align with yours.

DKIM does the work. Once you authenticate your domain, Brevo signs your mail with your domain name in place of its default signature. That signature aligns with your From address, so DMARC can pass.

Publish the Brevo code, DKIM and one DMARC policy. The new branded-subdomain CNAME is optional on shared IPs and required on dedicated IPs; older dedicated-IP instructions use an SPF TXT. Follow the flow shown in your account.

Step 1: Add your domain

Check first where your DNS is managed. If your nameservers point to another service, such as Cloudflare, add the records there.

  1. In Brevo, go to Settings > Senders, Domains, IPs > Domains and click Add a domain.
  2. Enter the domain you send from.
  3. Go through the Branded subdomain and Setup method steps. Choose the manual option to see each record.
  4. Brevo shows your records on the Records step.

Step 2: Add the Brevo code and DKIM

Copy every value from your account. The xxxxxxxx parts below are unique to you.

  • Brevo code: publish the TXT at the account-generated authenticated-domain name, with the value beginning brevo-code:. Use @ only when that name is the DNS zone root.
  • DKIM with two CNAMEs: brevo1._domainkey points to b1.xxxxxxxx.dkim.brevo.com, and brevo2._domainkey points to b2.xxxxxxxx.dkim.brevo.com.
  • DKIM with one TXT record: Brevo gives some accounts this format. Its API examples show the record at mail._domainkey. Use the name and value your account displays.

The part before ._domainkey is the selector, the label that tells receivers which key to fetch. Brevo's selectors are brevo1 and brevo2, or mail for the single TXT record.

If the panel appends the DNS zone name, remove only that suffix. For zone example.com, brevo1._domainkey.news.example.com becomes brevo1._domainkey.news; root-domain setup uses brevo1._domainkey. Apply the same rule to brevo2, mail and branded hosts, using your account’s full names.

Step 3: Publish one DMARC record

If your domain has no DMARC record, create a TXT record named _dmarc. Brevo's example sends reports to rua@dmarc.brevo.com. To receive them in DMARC Pulse too, list both addresses and replace the first one with your DMARC Pulse reporting address:

Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com,mailto:rua@dmarc.brevo.com

p=none requests no DMARC handling change while you review reports; receivers can still filter or reject mail under other rules. Preserve existing policy and report addresses. For a new deployment, assess quarantine after legitimate senders align; reject is optional and needs a separate mailing-list risk assessment.

If you already have a DMARC record, keep it and keep its current policy. Add the extra address to its rua tag, separated by a comma.

Step 4: Authenticate and confirm

Return to Settings > Senders, Domains, IPs > Domains and click Authenticate this email domain. Each record shows as verified once Brevo finds it. Brevo notes that DNS changes can take up to 48 hours.

To confirm the result yourself:

  • In the DKIM checker, enter example.com as the domain and brevo1 as the selector. If your account uses the single TXT record, use the selector mail.
  • Check your record with the DMARC checker.
  • Send a test to a Gmail address, open it, choose Show original from the three-dot menu and look for PASS next to DKIM and DMARC.

If you automate this, GET https://api.brevo.com/v3/senders/domains/{domainName} returns verified and authenticated, plus a status for each record.

Step 5: SPF with a dedicated IP

On shared IPs without a branded subdomain, Brevo uses its own return-path. SPF can pass there without aligning with your From domain, so aligned DKIM carries DMARC.

In the classic dedicated-IP setup, Brevo supplies a TXT SPF value for the sending subdomain. Publish it at the account's Host, merging it if that name already has SPF. Its help gives this example:

TXT
v=spf1 include:spf.brevo.com mx ~all

The new domain setup flow uses a Branded record CNAME for SPF and return-path. Copy that record from your account instead of adding an SPF TXT at the CNAME name: a CNAME cannot share its name with other data. The branded subdomain is required on dedicated IPs and optional on shared IPs in that flow.

The new flow is rolling out gradually. Follow the records your account shows; use the SPF checker on its actual return-path domain.

Common problems

Brevo cannot find your records

Your domain may use custom nameservers, or you may have edited the wrong domain. Add the records at the DNS host your nameservers point to. Then wait for the change to take effect before you try again.

DKIM fails even though the record looks correct

You may have typed the full hostname in the Host field, so the panel added your domain a second time. The Host should be brevo1._domainkey only. For a DKIM TXT record, copy the whole value in one go with no line breaks.

The CNAME will not save

A CNAME cannot share its name with another record. Look for an old record on the same Host and remove it only if its service is no longer in use. Squarespace also rejects a value that ends with a period.

DKIM CNAMEs behind Cloudflare

A proxied CNAME returns Cloudflare's IPs, and Cloudflare says records used for third-party verification should be DNS only. Its CNAME flattening for all CNAME records setting can make verification fail too, because the CNAME itself is no longer returned. Keep these records as DNS only. Our Cloudflare guide covers the zone settings.

Two DMARC or SPF records

RFC 9989, section 4.10, tells receivers to discard every DMARC record when one name returns several. Merge them into one record. The same goes for SPF: a second SPF record breaks the check.

Sending from a free mailbox or another domain

Brevo tells senders to avoid free addresses such as @gmail and @yahoo. You cannot add records to those domains, so your mail cannot align. Use an address on the domain you authenticated. Under relaxed alignment (RFC 9989, section 3.2.10.1), DKIM aligns when the signing domain and the From domain share the same organizational domain, so a subdomain of your authenticated domain can align as well.

Authentication passes and mail still lands in spam

Brevo points to reputation in this case, usually on a new domain. Warm up the domain gradually. Authentication makes your mail identifiable and cannot guarantee inbox placement.

Frequently asked questions

Do I need an SPF record to send with Brevo?
The default shared-IP setup needs no change to apex SPF. In the new flow, a branded SPF/Return-Path CNAME is optional on shared IPs and required on dedicated IPs. Follow your account records; classic dedicated-IP setup can use an SPF TXT.
Should I add include:spf.brevo.com to my SPF record?
Classic dedicated-IP help shows v=spf1 include:spf.brevo.com mx ~all. The new branded flow uses a CNAME instead. Copy your account records, keep one SPF per name and never add TXT at a CNAME name.
Why do my DMARC reports show SPF as not aligned for Brevo?
Default shared IPs without a branded subdomain use Brevo’s return-path, so SPF does not align with your From domain. The new branded-subdomain option can provide SPF alignment even on shared IPs. Aligned DKIM alone can pass DMARC.
What are the Brevo DKIM selectors?
Accounts with two CNAME records use the selectors brevo1 and brevo2. Brevo's API examples show a single TXT record at mail._domainkey, which is the selector mail. Your account shows which format applies to you.
Can I keep my existing DMARC record when I authenticate with Brevo?
Yes, and you should. A domain can have only one DMARC record. Brevo says to add its reporting address to the existing rua tag, separated by a comma, and not to create a second record.
How long does Brevo domain authentication take?
Brevo notes that DNS changes can take up to 48 hours. Each record shows as verified once Brevo finds it. Your own DNS host may apply changes sooner.

Sources consulted

Cloudflare: Proxy status
checked 2026-11-09
RFC 9989: DMARC
checked 2026-11-09
Brevo: Set up your domain
checked 2026-11-09
Brevo: Dedicated IP setup
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.