Opens in a new tab

include:spf.brevo.com — Brevo’s SPF include, and when you need it

include:spf.brevo.com — spf.sendinblue.com before the rebrand — lists Brevo’s sending servers. On Brevo’s shared IPs your mail carries Brevo’s own return-path (brevosend.com), so SPF checks Brevo’s domain, and Brevo says SPF is “not required to authenticate a domain”. It gives SPF records only for a dedicated IP, on the subdomain that IP sends from.

v=spf1 include:spf.brevo.com mx ~all
Belongs toBrevo (formerly Sendinblue) — marketing and transactional email
Needed on your domain?Only in some set-ups — by default SPF checks a different domain for its mail

What it costs, and is it in your record?

We measure include:spf.brevo.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether Brevo’s is there and what it costs.

What it covers

Brevo’s marketing campaigns and transactional email.

Do you need it?

On shared IPs, no: “By default, Brevo uses its own domains for tracking links, bounce handling, and the return-path in your emails (such as brevosend.com).” “The SPF and MX records are not required to authenticate a domain. We only provide these records when setting up a dedicated IP.” DMARC passes through Brevo’s DKIM.

With a dedicated IP, the subdomain linked to it becomes the return-path, and Brevo gives you an SPF record for that subdomain. Brevo’s newer “branded subdomain” — a CNAME such as mail.yourcompany.com — does the same for shared IPs, and “moves SPF alignment onto your sending domain” without an include on your root.

Its other forms

IncludeFor
spf.sendinblue.comThe same servers under Brevo’s former name. It publishes the same record today, and Brevo’s own return-path domain still includes it.

Common mistakes

  • A second SPF record instead of merging — “Having more than one SPF record can negatively impact your domain reputation.”
  • Dropping the mx that Brevo’s record carries when merging it into yours.
  • Authenticating yourcompany.com and sending from news.yourcompany.com: DKIM fails and Brevo replaces the sender domain with brevosend.com.

Setting up Brevo: SPF, DKIM and DMARC together →

Questions

Should I change spf.sendinblue.com to spf.brevo.com?

Both publish the same servers today. Brevo’s documentation shows only spf.brevo.com, but it has published no notice retiring the old name.

Sources

Checked on 26 September 2026 against these official sources:

Stay under 10 lookups without dropping a sender

Let us host your SPF record: you publish one include line, we flatten every service in it to their addresses and refresh it hourly, so however many there are they fit in a few lookups — and we tell you when a service changes its addresses. On the Personal plan and up.

Create a free account