Email deliverability glossary: 40 terms every sender should know
Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
How to clean a Brevo contact list: connect with an API key, verify the list, write results to an attribute, move dead contacts to a suppression list or blocklist, and know when to re-run it.
To clean a Brevo contact list, export or connect the list, verify every address over SMTP, then write the verdict back as a contact attribute and move undeliverable contacts to a suppression list or Brevo's blocklist. On a 20,000 contact list the whole process takes under an hour, and it is the single most effective way to protect the shared sending IPs that most Brevo accounts send from.
Brevo (formerly Sendinblue) handles bounces for you: when an address hard bounces, Brevo blocklists it so it cannot be emailed again from your account. That is good hygiene after the fact, but the bounce has already happened, and bounces are the metric that matters most to the receiving providers.
On Brevo's free, Starter and most Business plans you send from shared IP pools. Your reputation is pooled with other senders, and Brevo's own deliverability team monitors accounts whose hard bounce rate climbs; a campaign that bounces heavily can be paused and your account reviewed. The typical line where receivers start throttling is around 2% hard bounces, and a list that has not been cleaned for a year will usually sit well above that on its first send, since lists decay at roughly 22% a year.
There is also the cost of a wasted send. Brevo prices by emails sent, not contacts stored, so every message to a dead address is a paid message that was never going to be opened.
Prioritise by what will be emailed soonest:
A contact who clicked last week is proven; skip them this round.
VERIFYRE_STATUS, type Category, with the values deliverable, undeliverable, risky and unknown. Optionally add VERIFYRE_SCORE (Number) and VERIFYRE_CHECKED (Date).VERIFYRE_STATUS and, if you want it fully automatic, tick the option to move undeliverable contacts to the suppression list or add them to the blocklist.VERIFYRE_STATUS equals risky. Send to it separately, at lower frequency, and watch the bounce figure on that campaign alone.If you would rather not connect an API key, the export and import route works:
VERIFYRE_STATUS, so segments can use it.The manual route is fine for a quarterly clean. The integration earns its keep when contacts arrive continuously, because it can be scheduled and it never works from a stale export.
| Verdict | Score band | Brevo action |
|---|---|---|
| Deliverable | 90 to 100 | Keep in the list, send normally |
| Risky (catch-all, full mailbox, role account) | 30 to 89 | Segment separately, low frequency, no cold campaigns |
| Unknown (server would not answer) | 30 to 89 | Re-verify after 48 hours; treat as risky if still unknown |
| Undeliverable | 0 to 29 | Move to the suppression list or blocklist; exclude from all campaigns |
Blocklisting is stronger than suppression: a blocklisted address cannot be re-added by a later import without you unblocking it, which protects you from re-importing the same dead addresses next quarter. Suppression keeps the contact's history visible and is the better choice if you may want to re-confirm those contacts later.
Repeat verifications of unchanged addresses within 24 hours are free, and the bulk list cleaning page describes how scheduled runs work.
No. It writes attributes and, if you choose, moves contacts to a list or the blocklist. Nothing is deleted, and the contact history stays intact.
No. The check is an SMTP conversation that stops before any message content is transmitted, so contacts see nothing and there is no unsubscribe to worry about.
The blocklist is account-wide and permanent until you remove the address; Brevo refuses to send to it from any campaign or transactional flow. A suppression list is just a normal list you exclude from campaigns by hand.
One credit per unique address, so a 20,000 contact list uses at most 20,000 credits. Duplicates and anything verified in the last 24 hours cost nothing.
Related reading
@Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
@Real-time email validation checks an address as it is typed: syntax, typos, disposable domains, role accounts, MX and an optional mailbox check. Here is how it works.
@Gmail, Outlook and Yahoo addresses carry no company signal, so B2B teams segment them. When free addresses are legitimate, how the free and role flags route them, and bulk detection.
Photos: Freepik