# SPF record for Brevo

URL: https://iblockspam.com/spf/brevo
Last updated: 2026-10-09

Include: None for standard sending; spf.brevo.com with a dedicated IP
Where it goes: Not needed (dedicated IP: your domain)
DNS lookups: 0 on your domain

For standard sending, Brevo says the SPF and MX records are not required to authenticate a domain: you add a Brevo code, DKIM and DMARC instead. Brevo provides an SPF record only when you set up a dedicated IP. Its merge example then combines Brevo with Google Workspace as v=spf1 include:_spf.google.com include:spf.brevo.com mx ~all.

## Example records

- Standard sending: your main domain on Microsoft 365 stays as it is (TXT, host @): `v=spf1 include:spf.protection.outlook.com -all`
- Dedicated IP with Google Workspace (Brevo's merge example) (TXT, host @): `v=spf1 include:_spf.google.com include:spf.brevo.com mx ~all` Use the exact value Brevo shows in your account. The mx term is part of Brevo's example record.

## Notes

- Brevo's branded subdomain links to Brevo's infrastructure with a CNAME for SPF and the return path, which Brevo says enables full SPF alignment on your sending domain.
- Brevo says a domain can only have one SPF record and gives a merge example; check the result with an SPF checker.

## How to add it

- In Brevo, open the Domains settings and add your domain.
- Publish the records Brevo shows: the Brevo code (TXT), the DKIM records and a DMARC record.
- If you use Brevo's branded subdomain, also add the branded CNAME record: Brevo uses it for SPF and the return path.
- Only with a dedicated IP: add the SPF value Brevo gives you to your existing SPF record, merging it into one record.

## DKIM and DMARC

Brevo's domain authentication is built on DKIM and DMARC: DKIM signs with your domain, so it aligns with your From address. Brevo says your domain should have only one DMARC record.

## Common mistakes

- Adding `include:spf.brevo.com` when you don't have a dedicated IP. Brevo doesn't need it for standard authentication.
- Publishing Brevo's SPF value as a second record instead of merging it into the existing one.

**Q: Do I need an SPF record for Brevo?**
Not for standard sending. Brevo says SPF and MX records aren't required to authenticate a domain and are only provided when you set up a dedicated IP. Authentication uses a Brevo code, DKIM and DMARC.

**Q: What is Brevo's SPF include?**
Brevo's merge example uses `include:spf.brevo.com`, together with an `mx` term: `v=spf1 include:_spf.google.com include:spf.brevo.com mx ~all` for a domain that also uses Google Workspace. Copy the exact value from your Brevo account.

**Q: How do I merge Brevo's SPF record with my existing one?**
Keep one `v=spf1` at the start, put every include and mechanism from both records in the middle, and end with a single `all`. Then check the result with the [SPF Checker](https://iblockspam.com/tools/spf-checker).

Sources:
- Brevo Help: Authenticate your domain with Brevo (Brevo code, DKIM, DMARC): https://help.brevo.com/hc/en-us/articles/12163873383186-Authenticate-your-domain-with-Brevo-Brevo-code-DKIM-DMARC
- Brevo Help: Merge multiple SPF records: https://help.brevo.com/hc/en-us/articles/4414335084434-Merge-multiple-SPF-records
- Brevo Help: Set up your domain in Brevo: https://help.brevo.com/hc/en-us/articles/35337929909778-Set-up-your-domain-in-Brevo

---

Source: iBlockSpam, https://iblockspam.com/spf/brevo (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt