Guide

Brevo deliverability: why your emails go to spam and how to fix it

You send through Brevo, the dashboard says the message was sent, and the bounce report is empty. But the recipient never sees it. It is in spam, or it is not there at all. This is the most common complaint from teams sending through Brevo, and it is almost never Brevo's fault. Brevo is doing exactly what you told it to do. The problem is upstream: the sending domain, the authentication records, the IP reputation, or the list you are sending to. Here are the five reasons Brevo deliverability drops, in order of likelihood, and the exact fix for each one.

1. Your SPF record is missing the Brevo include

Brevo sends your mail from its own IP range, so your SPF record must include Brevo. Add the Brevo include to your SPF record. For current accounts that is include:brevo.com. If you set up your domain before the rebrand from Sendinblue, you may see include:sendinblue.com instead, which still works but the Brevo dashboard now shows brevo.com as the include to add. Open your DNS, find the SPF record (the TXT record that starts with v=spf1), and add the include. If the include is missing, the SPF check fails and mailboxes treat your mail as unauthenticated. Keep the total number of SPF lookups under ten, because exceeding that limit makes the whole record fail. The Brevo dashboard shows the exact include under your sender or domain settings, so copy it from there rather than typing it by hand.

2. DKIM is not enabled or the DNS record is missing

Brevo signs your mail with DKIM, but only if you enable it and add the DNS record it generates. In the Brevo dashboard, open your sender or domain settings and turn on DKIM signing. Brevo shows you a record to add, usually a TXT record with a long key. Add it to your DNS exactly as shown. If the record is missing, expired, or points to the wrong value, Brevo cannot sign your mail, and every message you send goes out unsigned. Unsigned mail is one of the strongest spam signals a mailbox sees. If you recently switched DNS providers, this record is the first thing to re-add. After you add the record, wait for it to propagate and then send a test message, because DNS changes can take a few minutes to an hour to take effect.

3. You are sending from a domain you have not verified in Brevo

Brevo requires you to verify the domain you send from. If the domain is not verified, or if you send from a different domain than the one you verified, Brevo delivers with a lower reputation or rejects the send. Verify the exact domain you send from, not a subdomain, unless you intend to send from that subdomain. A common mistake is verifying mail.example.com and then sending from example.com, which Brevo treats as a different, unverified domain. Check the sender settings in the Brevo dashboard and make sure the domain you send from is the one marked as verified. If you send from more than one domain, verify each one.

4. Your shared IP pool has a bad reputation, or you have not warmed up

By default, Brevo sends your mail from a pool of shared IPs. Other senders on that pool affect your reputation. If a neighbor is sending spam or has a high complaint rate, your mail can suffer even if your own sending is clean. If you are a new sender or a new domain, use Brevo's warm-up feature to increase your sending volume gradually over a few weeks instead of jumping to full volume. Jumping to full volume on a new domain is one of the fastest ways to get flagged as spam. At higher sending volume you can request a dedicated IP, but you still need to warm it up gradually instead of jumping to full volume. You can watch your sending statistics in the Brevo dashboard, but the dashboard only tells you what happened after the fact. Inboxproof monitors your domain around the clock and alerts you the moment a record breaks or an IP gets listed, so a reputation drop never catches you blind.

5. Your bounce and complaint rates are too high

Brevo tracks bounces and complaints per sending domain. If your bounce rate climbs or your complaint rate climbs, Brevo degrades your reputation and can suppress your sends. Clean your list before you send, validate addresses, and honor unsubscribes the same day. Brevo maintains a suppression list of addresses that have bounced or complained. If you keep sending to those addresses, you hurt your reputation and waste sends. Remove hard bounces from your list, stop sending to addresses that have not opened your mail in a long time, and keep your engagement healthy so the addresses you do send to actually open the mail. A list that is mostly disengaged addresses is a list that will get you flagged, no matter how clean your DNS is.

Find out which of these is breaking your Brevo deliverability

Run a free audit of your domain. It checks SPF, DKIM, DMARC, MX, TLS, PTR and blocklists in one pass, and tells you exactly which record is wrong and how to fix it. No account needed.

Run the free audit

Want to know the moment any of these breaks? Inboxproof Pro monitors your domain around the clock and alerts you the instant a record changes or an IP gets listed. See pricing →

Related guides
Deliverability for agencies and developers
Amazon SES deliverability
Transactional email API deliverability
Why email goes to spam
DKIM not signing emails? How to fix it