Brevo sends campaigns, automations and transactional mail. To send that mail as your domain and pass DMARC, publish the records below and check the alignment notes.
What to add.
include:spf.brevo.com in your SPF record, plus the DKIM records below.
What signs your mail. DKIM records Brevo generates for your account.
Brevo lets you send a campaign from a domain other than the one you authenticated, and that mail fails DMARC.
The SPF record
Add this include to the SPF record on your sending domain:
A complete record for a domain that also sends through Google Workspace:
Brevo shows the current include on the Senders, Domains screen, and when I last checked it
was this one. Accounts set up under the Sendinblue name may still carry
include:spf.sendinblue.com, which continues to resolve. Don't keep both. The
second one wastes a lookup.
Then count your lookups, because SPF allows ten DNS lookups across the whole chain of includes. A sender that receivers need an eleventh lookup to find gets a permerror and fails SPF, even though the record looks right when you read it. Run the domain through the SPF checker after every change. The count also moves when a provider changes its own records.
DKIM
Brevo hands you a DKIM TXT record and a separate verification TXT record for the domain, and lists both on the authentication screen. Publish them, press the verify button, and check the tick appears against the domain rather than assuming the DNS change was enough.
DMARC alignment with Brevo
DMARC passes when SPF or DKIM passes and the domain it authenticated matches the domain in your visible From address. A provider can pass both checks for its own domain while your mail fails DMARC.
- Free and low-tier accounts share sending infrastructure. Authentication makes your mail align, and it still shares a sending reputation with the other accounts on those servers.
- Brevo appends its own footer on the free plan. That happens before signing, so DKIM still passes. The footer does put Brevo's branding in your mail.
- Transactional and marketing traffic share the domain unless you move them onto separate subdomains, and that's worth doing.
The DMARC alignment guide covers the general case, and the dmarc=fail page shows how to read the Authentication-Results header.
Verification
Substitute your domain, and run these after the TTL on anything you replaced has expired:
Then send one message through Brevo to a Gmail address you control, open Show original,
and look for dkim=pass with your domain in header.i. A test
message shows what a receiver does with your mail. A DNS lookup only shows what you
published.
Our SPF checker gives you the lookup count. The DKIM checker shows whether a selector resolves and whether the key is long enough, and the DMARC checker reads your policy back to you. You can use them free, without an account.
I checked the values here against Brevo's own documentation, at Brevo help center. Providers change their DNS requirements without much notice. If their screen shows something different from this page, follow their screen and tell us.
A record can be correct and still fail alignment once real mail goes through it. Receivers record that result in the reports they send. We read the reports for you, and on a paid plan we email you the day a new sender fails. See whether this sender passes. Your first domain is free.
Is Brevo authorized to send as your domain?
We look for include:spf.brevo.com in your SPF record and count the
lookups it costs you.
Free · No signup · The result names what to change
Keep reading
Adding this to a domain that already sends? Our SPF record generator merges the include into the record you publish today rather than replacing it, the SPF checker resolves every include and counts the lookups, and the DKIM checker confirms the selector answers.