Fix Brevo emails going to spam

Brevo silently rewrites an unauthenticated domain to brevosend.com, and free and most paid accounts send from its shared IP pools. The most important fix: authenticate your domain so DKIM signs as you, not as brevosend.com.

Run a free spam test How to test your sends

Why Brevo emails land in spam.

Brevo rewrote your From address to brevosend.com

When a domain is not authenticated in Brevo (DKIM missing or invalid), Brevo's automatic protection replaces the sending domain with @brevosend.com to satisfy the Gmail and Yahoo sender rules in force since February 2024. Nothing fails visibly: campaigns report as delivered while recipients see a substitute address or a via label, and your own domain builds zero reputation. Authenticate the domain under Settings > Senders, Domains, IPs > Domains, then confirm the DKIM d= domain on a live send.

By default SPF passes for Brevo, not for you, so DKIM carries your DMARC result

By default Brevo keeps the Return-Path on its own bounce domain (brevosend.com), so SPF passes for Brevo's infrastructure but does not align with your From domain. DMARC then passes through DKIM alone: if your mail._domainkey TXT record or the brevo1/brevo2 CNAMEs are missing or broken, every campaign fails DMARC outright, and an include on your root SPF record does not change that. Brevo's newer domain setup, being rolled out gradually, adds a branded subdomain (for example mail.yourdomain.com) that moves the return path onto your domain and aligns SPF there. Brevo requires it for dedicated IPs and strongly recommends it on shared IPs.

You share IP reputation with other Brevo senders

Free accounts and most paid accounts send from Brevo's shared IP pools. Your inbox placement moves with the pool, and you cannot pick your neighbors. The signal you do control is domain reputation: aligned DKIM, a clean list, and steady engagement, which is exactly why authentication matters more on Brevo than on ESPs with stricter onboarding.

The free plan's 300-email daily cap turns campaigns into multi-day drips

On the free plan you can send 300 emails a day: a campaign to a bigger list reaches only 300 contacts, and you have to send to the rest yourself on the following days until the whole list is covered. Mailbox providers see the same message arriving in small bursts across days, engagement data gets spread thin, and time-sensitive content lands late. If your list is bigger than a few hundred contacts, the cap itself is a deliverability problem, not just a billing one.

Marketing blasts and password resets share one domain reputation

Brevo sends campaigns and transactional mail (SMTP and API) under the same authenticated domain by default, so a bad newsletter drags down order confirmations and password resets. Brevo's own guidance is to separate streams on subdomains, for example news.yourdomain.com for campaigns, each authenticated in its own right. Keep in mind that Gmail counts all subdomains of one primary domain together toward its 5,000-a-day bulk sender threshold.

A dedicated IP you do not need, or never warmed up

Brevo offers dedicated IPs (one is included with Enterprise) and recommends them only if you send at least three campaigns a week to 3,000 or more contacts, or over 100,000 emails a month with no gaps longer than a week. If you send only once or twice a month, Brevo itself says a shared IP may be the better option. If you qualify, attach the IP to a dedicated sending subdomain and use Brevo's automatic warm-up, which raises volume by 20 percent per sending day and expects sends to at least 3,000 contacts daily or every other day in the first weeks.

Two more causes sit outside your platform: the domain behind your sending address on a blacklist and invalid addresses that bounce. Unspam has a free tool for each, the email blacklist checker for the domain after the @ and the email verifier for the mailbox itself.

How Brevo authenticates your mail.

Brevo authentication is three records from one wizard: a Brevo code TXT to prove ownership, DKIM, and DMARC.

record default the problem the fix
Brevo code (TXT) Absent until you start authentication; Brevo generates a unique value like brevo-code:9b87d61c... per account. Without it Brevo cannot verify domain ownership, so the wizard never completes and senders on the domain stay unauthenticated, which triggers the brevosend.com rewrite. In Settings > Senders, Domains, IPs > Domains, click Authenticate next to your domain and publish the brevo-code TXT record at the root (@) of your DNS, then re-verify. Full validation can take up to 48 hours.
DKIM Unauthenticated domains get no DKIM for your domain; Brevo signs and sends with its substitute brevosend.com identity instead. Mail keeps flowing but recipients see a substitute address or via label, your domain builds no reputation, and DMARC has nothing aligned to pass on. Publish exactly what your account shows: either one TXT record at mail._domainkey, or two CNAMEs, brevo1._domainkey and brevo2._domainkey, pointing to b1.yourdomain.com.dkim.brevo.com and b2.yourdomain.com.dkim.brevo.com. Different accounts see different formats, so copy from your own Domains page, not from a tutorial.
SPF By default the Return-Path is a Brevo-controlled bounce domain (brevosend.com), so SPF passes against Brevo's domain. SPF passes without aligning to your From domain, so it contributes nothing to DMARC; DMARC reports showing SPF pass with alignment fail are normal on Brevo without a branded subdomain. Brevo says SPF is not required to authenticate a domain. Without a branded subdomain, an include on your root SPF record does nothing for alignment, so rely on aligned DKIM. Brevo's newer domain setup, being rolled out gradually, adds a branded subdomain (for example mail.yourdomain.com) that moves the return path onto your domain and aligns SPF; it is required for dedicated IPs and strongly recommended on shared IPs. Keep one SPF record per domain, within 10 DNS lookups.
DMARC Brevo's wizard proposes v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com at _dmarc.yourdomain.com. Bulk senders without any DMARC record get throttled or rejected by Gmail and Yahoo. Worse, the automatic flow offers to replace an existing DMARC record with Brevo's, which silently reroutes your reports and resets your policy to p=none. If you already publish DMARC, authenticate manually and keep your record, optionally adding Brevo's rua address as a second report recipient. If you have no record, accept Brevo's p=none version and tighten the policy once reports run clean.

By default the envelope stays on Brevo's infrastructure, so DKIM does the DMARC alignment work unless you add a branded subdomain. Everything lives under Settings > Senders, Domains, IPs > Domains, with an automatic option that logs into your DNS provider from Brevo and a manual copy-paste path.

Once you have updated these records, confirm they pass with Unspam's free SPF checker, DKIM checker, and DMARC checker.

How to test a Brevo campaign with Unspam.

Brevo's Preview & test sends go to a dedicated test list capped at 20 addresses, and personalization renders from whatever attributes your test contacts happen to have.

Read more

A one-off message to a handful of addresses is not scored the way a bulk campaign drop is, and on the free plan a test cannot reproduce the 300-a-day drip your real send will follow. The only honest test is a real campaign to a seed address.

  1. 1

    Get your Unspam seed address

    Start a spam test or inbox placement test in Unspam and copy the test address it generates. Placement tests include seed addresses at ten mailbox providers, Gmail, Outlook and Yahoo among them. An inbox placement test also issues a Test ID. Paste it into the subject line or the body before you send, or the message reaches the seed mailboxes and is never matched to your test.

  2. 2

    Add the seeds as regular Brevo contacts

    Go to Contacts > Lists, create a normal list named something like Deliverability seeds, and add the Unspam addresses to it. Use a regular list, not Brevo's test list: the test list exists for the Preview & test feature, which is the path you are trying to avoid.

  3. 3

    Build the campaign exactly as you plan to ship it

    In Campaigns > Email, keep the final subject line, final content, and a From address on your authenticated domain. Placeholder copy and a throwaway subject change how filters score the message, so test the real thing.

  4. 4

    Send it for real, not via Preview & test

    Select the seed list as the recipient and use Send now or Schedule, so the mail leaves through the production path with your live DKIM signature and the unsubscribe link Brevo enforces at send time. On the free plan this counts against the 300-email daily cap, so send seeds while you have quota left.

  5. 5

    Read the results in Unspam

    Check the SpamAssassin-style spam score, placement per provider, client previews, and the heatmap, plus SPF, DKIM and DMARC verdicts on the live send: the DKIM d= domain should be your domain, not brevosend.com. The free tier covers 5 spam tests and 3 inbox placement tests per month with no card; the paid Custom plan starts from a $5 monthly minimum with a 14-day refund.

The same test renders your campaign in 50+ real email clients, Gmail, Outlook, Apple Mail, iPhone, and Android among them, including dark mode, via email client previews, so you confirm placement and rendering in one pass.

Your platform has its own test send too. Sending a test email in Brevo covers what it does, what it quietly changes, and where it stops.

Brevo features that quietly affect delivery.

The brevosend.com rewrite is silent

Brevo swaps the sending domain on unauthenticated mail without failing anything. Campaign reports look normal while recipients see a brevosend.com address or a via label next to your name. Do not trust the dashboard on this: read the From and DKIM d= domains in a live header, or in Unspam's authentication check on a real send.

Two DKIM formats exist, follow your own screen

Depending on the account, Brevo issues either a single TXT record at mail._domainkey or a brevo1/brevo2 CNAME pair pointing at dkim.brevo.com, and its help center documents both formats. Blog tutorials usually show only one format. Copy values from your own Domains page; a record pasted from someone else's guide will never verify.

The automatic wizard can replace your existing DMARC record

Brevo's connect-your-DNS-provider flow detects an existing DMARC record and asks to replace it with v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com. Accepting downgrades an enforcement policy to p=none and reroutes your aggregate reports to Brevo. If you already run DMARC reporting or enforcement, authenticate manually instead.

Free plan mail carries Brevo branding and a drip schedule

Every free-plan email ships with a Brevo logo footer, and removing it is a paid add-on or a higher plan. Combined with the 300-a-day cap and manual resending, a free-plan send neither looks nor behaves like the campaign your paid competitors send. Both signals are visible to recipients.

Still landing in spam after these fixes? Our email deliverability consultants can audit your setup and work through the fixes with your team.

What real Brevo senders run into.

The deliverability problems Brevo senders hit most often, each with the fix that resolves it.

Brevo says 'delivered' but the customer swears they never got it

Shared SMTP IPs, Brevo's included, can end up on blocklists such as Spamcop or Spamhaus, and receiving servers that use those blocklists soft-bounce or silently drop the mail. Because the rejection is asynchronous, the dashboard often still shows 'delivered' while the recipient's own server quietly refused it.

The fix
  • Do not trust the 'delivered' label alone.
  • Open the transactional email History tab, filter for soft bounce or hard bounce, and click Show details to read the actual SMTP response, which comes from the recipient's server and names the blocklist and IP (for example "550-Rejected because 77.32.148.24 is in a black list at bl.spamcop.net").
  • A shared-IP listing is Brevo's incident to clear: Brevo automatically stops using an IP once a Spamhaus block is detected and works to delist it, so open a support ticket with the exact bounce text rather than changing your DNS or SPF.
  • If a critical stream like order confirmations or password resets cannot tolerate riding other senders' blocklist hits, move it to a dedicated IP.

Brevo suspended our whole account after one bad send, and we can't get it back

Brevo auto-suspends the campaign and account when a random-subset assessment (usually within 1 to 3 hours of a send) crosses hard lines: hard bounce over 2%, unsubscribe over 1%, or spam complaints over 0.2%. The first suspension often arrives with no warning, and Brevo's policy is that a second suspension can mean permanent, irreversible deactivation.

The fix
  • Treat the first suspension as your only warning.
  • It is reversible: go to the Deliverability center, follow the reactivation prompt, and clean your contact database exactly as instructed before resuming, because a second suspension can permanently deactivate the account with no reinstatement.
  • Cleaning means removing hard bounces, role and generic addresses, and anyone you cannot prove opted in (blocklist them in Brevo).
  • Structurally, keep hard bounce under 2% by validating every import externally, and keep unsubscribes under 1% and complaints under 0.2% by mailing only consented, recently engaged segments, since complaint rate is driven by consent and relevance, not list validation.

We imported a fresh list, hit send, and Brevo froze the campaign mid-send

Brevo watches sends to newly imported contacts especially closely: it evaluates the campaign on a random early sample, and if that sample crosses its limits (hard bounce over 2%, complaints over 0.2%, unsubscribes over 1%, or any spam-trap hit) it suspends the rest of the campaign and often the whole account. Senders who blast a purchased or long-dormant list immediately are the ones who get caught.

The fix
  • Never send a full blast to a freshly imported list.
  • Verify the list through an external validation service first to strip dead and trap addresses, then ramp: mail your most recently engaged contacts before touching cold or newly imported ones so the early sample stays clean.
  • If the import is old or you cannot prove consent, run a re-permission campaign to a small slice first instead of mailing the whole file at once.
  • If a campaign is frozen, you clean up and reactivate it from the Deliverability Center.

Our Brevo emails aren't in spam, they're buried in Gmail's Promotions tab

Many Brevo senders find their campaigns in Gmail's Promotions tab rather than the primary inbox, which does not register as a spam failure but can still cost opens. It is driven mostly by promotional-looking content and many tracked links and images.

The fix
  • Promotions placement is a content and categorization signal, not an authentication failure, so do not chase it with DNS changes; DKIM, SPF, and DMARC can all pass and mail still lands in Promotions.
  • Reduce tracked links and heavy image blocks, lean toward a plain, one-to-one tone with a personal-looking sender name for mail that must reach Primary, and keep sending to engaged recipients so Gmail learns the mail is wanted.
  • Separate genuinely transactional streams like receipts and password resets onto their own authenticated subdomain.
  • Keep expectations realistic: Promotions is still the inbox, so weigh this against clearer wins like authentication and list hygiene first.

Brevo inbox placement gets soft on big sends while small sends land fine

Senders happy with Brevo's features report that inbox placement weakens specifically as send size grows, even with healthy overall metrics. The pattern of small sends landing while large ones crater points to the disengaged tail of the list dragging the whole send, compounded by Brevo's shared IP pool where you can inherit reputation from other senders on the same IPs.

The fix
  • Do not switch tools first, because stale lists and weak engagement follow you to any ESP.
  • Segment to recently engaged contacts and stop mailing the never-openers, since large sends drop when they reach the dead tail of the list.
  • Confirm SPF, DKIM, and DMARC actually align rather than just pass, and watch domain reputation in Google Postmaster Tools directly instead of trusting the sending dashboard.
  • Shared IP pools are the one genuinely Brevo-specific factor, so once your volume justifies it, move to a dedicated IP so no neighbor can tank your placement.

Brevo deliverability, answered.

Why does Gmail show "via brevosend.com" next to my sender name?

Your domain is not authenticated in Brevo, so Brevo signs and sends with its substitute brevosend.com domain instead of yours. Older threads mention sendinblue.com because Brevo rebranded from Sendinblue in 2023; the mechanism is the same. Authenticate the domain (Brevo code, DKIM, DMARC) under Settings > Senders, Domains, IPs > Domains, and the label disappears once verification completes, which can take up to 48 hours.

Do I need to add Brevo to my domain's SPF record?

Not for alignment. Brevo says SPF is not required to authenticate a domain. By default Brevo controls the Return-Path domain, so SPF is evaluated against Brevo's infrastructure and already passes, just without aligning to your From domain, and an include on your root SPF record does not change that. If your account has Brevo's newer domain setup, a branded subdomain moves the return path onto your domain and aligns SPF there. Without one, DMARC passes through DKIM alone, so the DKIM record from your Domains page is the fix that matters.

Is a Brevo dedicated IP worth it?

Only at volume. Brevo's own threshold is at least three campaigns a week to 3,000 or more contacts, or over 100,000 emails a month with no gaps longer than a week. If you send only once or twice a month, Brevo itself says a shared IP may be the better option. If you qualify, plan for weeks of warm-up; Brevo's automatic warm-up raises volume by 20 percent per sending day.

My campaign stopped partway through the list. Is Brevo blocking me?

Almost certainly not. On the free plan you can send 300 emails a day, so a campaign to a bigger list reaches only 300 contacts and you send to the rest yourself on the following days. That drip pattern also dilutes engagement signals, so if you send to more than a few hundred contacts regularly, a paid plan removes a real deliverability handicap, not just an inconvenience.

Can Unspam connect to my Brevo account and test campaigns automatically?

No. Unspam does not integrate with Brevo's API or any other ESP API. The workflow is manual by design: add Unspam's seed addresses as contacts in a regular Brevo list, send a real campaign to that list, and read the results in Unspam. Only a real send carries your final DKIM signature and the production sending path, so it is also the more accurate test.

Do my marketing campaigns hurt my transactional email on Brevo?

They can. Campaigns and transactional mail sent through Brevo share your domain's reputation by default, so complaints about a newsletter degrade receipts and password resets too. Brevo recommends separating streams on authenticated subdomains, such as news.yourdomain.com for campaigns. Note that Gmail still counts all subdomains of one primary domain together when applying its bulk sender rules.

Brevo platform details were verified against publicly available documentation in June 2026 and may have changed since. Brevo is a trademark of its respective owner. Unspam is not affiliated with or endorsed by Brevo.

Test your next Brevo email before your recipients do.