Brevo (Sendinblue) SPF & DKIM Setup with DMARC

Authenticate your domain in Brevo (formerly Sendinblue): publish the DKIM records and DMARC TXT, and learn where SPF fits in. Beginner-friendly, step by step.
4 min read
Updated 2026-11-04
Brand Specific
brevosendinbluedkimspfdmarc

Brevo (formerly Sendinblue) is one of the easiest ways to start sending email — and one of the easiest places to get authentication right. Without it, Brevo sends your campaigns through its shared infrastructure on its own domains: recipients see a generic sender, DMARC never aligns with your From address, and the Gmail, Yahoo and Microsoft bulk-sender rules quietly push your mail away from the inbox.

Authentication fixes this in one short session: add the domain in Brevo, publish the records it generates, click verify. This guide walks through it from scratch, including where SPF fits — the point where most copied-from-a-blog instructions go wrong.

What you need

  • A Brevo account — any plan, including the free tier.
  • The domain you send from, with access to its DNS settings at your registrar or DNS host.
  • About 15 minutes. Most records verify within minutes.

Configuration steps

  1. Log in to Brevo and go to Senders & IPs > Senders, then open the Domains tab and click Add a domain. (In older accounts this lives under the Senders page directly.)
  2. Enter your sending domain, for example yourdomain.com. Brevo generates the records for authentication:
  • A Brevo code TXT record — proves you control the domain.
  • A DKIM record — either one TXT record or a pair of CNAME records, depending on your account. When offered the CNAME form, take it: the CNAME pair uses 2048-bit keys, the single TXT 1024-bit, and 2048-bit is what current receiver standards expect.
  • A DMARC TXT record — Brevo suggests a starting record; you can publish it as shown or customize the reporting address.
brevo-verification=xxxxxxx   TXT  (Brevo code - exact value from your account)
xxx._domainkey               TXT  (DKIM public key - exact value from your account)
_dmarc                       TXT  v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
  1. Copy each record into your DNS provider exactly as Brevo displays it — same type, same host, same value. If your DNS panel appends your domain to the host name automatically, keep only the part Brevo shows.
  2. Return to Brevo and click Verify. The status turns green once DNS resolves, usually within a few minutes and almost always within a few hours.

Where SPF fits in

On Brevo's shared infrastructure, the envelope sender (Return-Path) stays on Brevo's side, so DKIM with your domain is what satisfies DMARC alignment — that is why Brevo's authentication flow centers on the DKIM records and the Brevo code, and why its FAQ notes that domain authentication does not require SPF or MX records.

If you later add a dedicated IP or a custom Return-Path, SPF becomes relevant, and Brevo's current SPF include value is:

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

The legacy value spf.sendinblue.com still resolves, but use spf.brevo.com in new records. And if your domain already has an SPF record (for your mailbox provider, for example), merge the include into that single record — never publish a second v=spf1 TXT record. Check the result with the SPF Checker or build it with the SPF Generator.

Verify

Send a test email from Brevo to a Gmail address and open Show original. You should see DKIM pass with d=yourdomain.com and DMARC pass. SPF may show pass for a Brevo domain — that is expected on shared infrastructure and does not affect the DMARC result.

Then verify the records: run the DKIM Checker with your domain and Brevo's selector, the DMARC Lookup for the DMARC record, or the Email Health Check for the whole domain. If SPF and DKIM pass but DMARC fails, it is an alignment problem — see the authentication fundamentals guide.

Common mistakes

  • Sending from free-mailbox domains. gmail.com, outlook.com and similar domains cannot be authenticated in Brevo, so those From addresses are filtered or rejected. Use your own domain.
  • Publishing a second SPF record. If you add Brevo's include as a new TXT record while an SPF record already exists, SPF breaks for every sender on the domain. Merge into one record.
  • Accepting the 1024-bit TXT DKIM option when CNAME is offered. The CNAME pair carries 2048-bit keys. Prefer it unless your DNS host cannot do CNAMEs at that host name.
  • Trusting copied record values. Host names and values are account-specific. Copy from your own Brevo screen, not from a tutorial.
  • Starting DMARC at quarantine or reject. Begin with p=none and read the aggregate reports with the DMARC Report Analyzer; escalate only when every legitimate sender passes.

Frequently asked questions

Is Sendinblue SPF the same as Brevo SPF?

Yes — same company, renamed. The current include value is spf.brevo.com; the old spf.sendinblue.com value still resolves, so existing records keep working, but use the new value when you write records.

Do I need SPF at all for Brevo?

For domain authentication on Brevo's shared infrastructure, no — DKIM alignment carries DMARC. SPF with include:spf.brevo.com matters once you use a dedicated IP or a custom Return-Path, or when your organization's policy requires authorizing every sending IP.

Why does Gmail show SPF pass for a Brevo domain?

Because SPF is evaluated on the envelope sender, which sits on Brevo's infrastructure. The DMARC verdict comes from the aligned DKIM signature, and that one shows your domain.

Can I use my root domain for everything?

You can, but separate subdomains for marketing and transactional mail (news.yourdomain.com and mail.yourdomain.com) keep their reputations independent — one mail type's problems do not drag the other down. Repeat the same steps per subdomain.

Was this guide helpful?