Sendinblue (legacy include) email authentication
The pre-rebrand Sendinblue include, still published for existing customers.
SPF record
Add Sendinblue (legacy include) to your domain's SPF record with this include:
include:spf.sendinblue.com
A complete record for a domain sending only through Sendinblue (legacy include):
v=spf1 include:spf.sendinblue.com ~all
What it costs you
1 of your 10 DNS lookups. That is the cheapest an include can be — the record it points at contains only IP ranges, with no further includes to follow. Behind it are 10 IP ranges.
Live record
This is what spf.sendinblue.com published when this page was generated:
v=spf1 ip4:185.41.28.0/22 ip4:94.143.16.0/21 ip4:185.24.144.0/22 ip4:153.92.224.0/19 ip4:213.32.128.0/18 ip4:185.107.232.0/22 ip4:77.32.128.0/18 ip4:77.32.192.0/19 ip4:212.146.192.0/18 ip4:172.246.0.0/18 -all
DKIM
Enable DKIM inside Sendinblue (legacy include) and publish the selector record it generates. DKIM matters more than SPF for deliverability, because a DKIM signature survives forwarding while SPF does not — see how selectors work.
DMARC
Neither SPF nor DKIM protects the address your recipients actually see until DMARC ties them
to it. Once Sendinblue (legacy include) is authenticating, publish a DMARC record — start at
p=none with a reporting address and
tighten from there.
Check it worked
DNS changes take minutes to hours to propagate. Once published, run the domain through the checker — it resolves the full include chain and reports the real lookup count.