Brevo (formerly Sendinblue) authenticates a domain with three things: a brevo-code TXT record that proves you own it, a DKIM record, and a DMARC record. On shared sending, Brevo says SPF is not required — it provides SPF and MX records only for a dedicated IP.
| SPF | Not needed on shared IPs |
| DKIM | One TXT or two CNAMEs, depending on the account |
| Bounce domain | Brevo’s own on shared IPs |
| Set up in | Settings → Senders, Domains, IPs → Domains |
Is your domain set up for Brevo?
We read your SPF record, look for Brevo’s DKIM key and check DMARC. Nothing is stored.
SPF for Brevo
Brevo: “The SPF and MX records are not required to authenticate a domain. We only provide these records when setting up a dedicated IP.” On shared IPs the bounce address is Brevo’s, so SPF does not align with your domain.
For SPF alignment Brevo offers a branded sending subdomain (for example mail.yourcompany.com); with a dedicated IP, the records Brevo gives you make that subdomain the bounce domain.
DKIM for Brevo
In Brevo, open Settings → Senders, Domains, IPs → Domains and authenticate the domain. Depending on the account, DKIM is one TXT record at mail._domainkey or two CNAME records — use what your screen shows.
Automatic authentication through your DNS provider is offered too. It replaces an existing DMARC record; if you want to keep yours, authenticate by hand.
| Name | Type | Value |
|---|---|---|
@ | TXT | brevo-code:<code from Brevo> |
mail._domainkey | TXT | k=rsa; p=<key from Brevo> (or two CNAMEs, as Brevo shows) |
_dmarc | TXT | v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com |
The exact values come from Brevo; copy them from there. Placeholders are in angle brackets.
Bounce domain and DMARC
Brevo asks for a DMARC record with its own report address: v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com. If you already have a DMARC record, do not add a second one — add Brevo’s address to your existing rua tag, separated by a comma.
On shared IPs Brevo mail passes DMARC through DKIM, so make sure the DKIM record verifies before you tighten the policy.
No DMARC record yet? Start with one that only reports, read the reports for a couple of weeks, then tighten it: build it with the DMARC generator.
Common mistakes
- Cloudflare CNAME flattening turns a DKIM CNAME into a TXT answer and fails authentication; turn it off for those records.
- Letting automatic setup replace your existing DMARC record, and losing your own report address.
- Two DMARC records after pasting Brevo’s next to your own.
Questions
What is the brevo-code record?
A TXT record on your domain that proves to Brevo you control it. It does nothing for receivers; it can stay.
Sources
Checked against Brevo’s own documentation on 25 September 2026:
- Authenticate your domain with Brevo Brevo code DKIM DMARC — help.brevo.com
- Domain authentication and validation — developers.brevo.com