Brevo emails going to spam? Check your domain in 60 seconds.
We verify Brevo's DKIM CNAMEs (brevo1/brevo2._domainkey — or mail/mail2 on earlier accounts), DMARC, SPF, MX and 24+ blocklists.
Free · no signup · unlimited checks · reads public DNS only
Brevo's domain authentication asks for a handful of records, and they're not interchangeable: a Brevo verification code TXT proves you own the domain, but only the DKIM CNAME records — brevo1._domainkey and brevo2._domainkey on current accounts, mail._domainkey and mail2._domainkey on earlier ones — make Brevo sign email as YOUR domain. Plenty of setups add the code, see 'verified' in the dashboard, and stop — leaving every campaign signed by shared infrastructure.
Enter your domain and we'll check which Brevo DKIM generation answers in your DNS, whether DMARC exists and what it instructs, and whether the domain's SPF, MX and blocklist status hold up underneath.
How Brevo setups actually fail
Verification code added, DKIM skipped
The dashboard shows a green domain because ownership was verified — but ownership isn't authentication. If our probes find neither brevo1/brevo2 nor mail/mail2 DKIM records, your campaigns aren't carrying your domain's signature. Add the CNAMEs from Brevo's Senders, Domains & Dedicated IPs page.
Records from two account generations mixed up
Guides for the old Sendinblue records (mail._domainkey TXT) float around alongside Brevo's current CNAMEs. Following both, or the wrong one for your account's generation, leaves records that exist but don't match what Brevo signs with. Our report shows exactly which names answer and with what.
An SPF include your account doesn't use
Brevo's spf.brevo.com include matters for dedicated-IP setups; on shared infrastructure Brevo handles the envelope itself. A stray include isn't fatal, but each one costs DNS lookups against SPF's limit of ten — and a broken SPF fails everything.
Fix anything above in your Brevo dashboard following the official Brevo setup guide, then re-run the check — DNS changes usually show within minutes.
Record names and provider behavior on this page were last verified against Brevo's official documentation on 12 July 2026.
Questions, answered plainly
Why are my Brevo emails going to spam?
Most often: the domain was 'verified' with Brevo's code TXT but the DKIM CNAME records were never added, so campaigns sign as shared infrastructure instead of your domain. Missing DMARC and foundation issues (SPF, MX, blocklists) come next — this checker covers all of it from your domain name.
What DNS records does Brevo need?
Current accounts: the Brevo verification code TXT plus DKIM CNAMEs at brevo1._domainkey and brevo2._domainkey, and a DMARC record. Earlier accounts used mail._domainkey/mail2._domainkey. Your exact values are in Brevo under Senders, Domains & Dedicated IPs.
Do I need Brevo in my SPF record?
Only for dedicated-IP setups — Brevo's docs provide the SPF and MX records in that case. On shared sending, DKIM is your authentication path and your root SPF record stays as it is.
Is DMARC required to send with Brevo?
Gmail and Yahoo require DMARC from bulk senders since February 2024, so effectively yes for any real list. It's one TXT record at _dmarc.yourdomain.com, starting with v=DMARC1; p=none.
The full guide
Brevo emails going to spam? 'Verified' doesn't mean authenticated
Brevo's green checkmark proves you own the domain, not that your emails are signed by it. The DKIM records that actually matter, and how to tell which generation yours are.
Read the guide →More free checkers
A passing check is a snapshot: records that are right today drift, expire and get overwritten, and nobody gets notified. That slow rot is what we call deliverability decay, and it has its own curriculum in Decay University.