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.
Cold lists are guessed, scraped and aged, so they bounce more. How to verify before every sequence, handle catch-all domains, stay under 1% bounces and keep the programme compliant.
Email verification for cold outreach means checking every prospect address before it enters a sequence, so that bounces stay under the 2% line that gets a cold domain throttled or blocked. Cold lists bounce far more than opt-in lists because the addresses were guessed, scraped or bought rather than given, and a single bad batch can burn a sending domain in an afternoon. Verifying first keeps the domain alive; handling catch-alls carefully and honouring opt-outs keeps the programme compliant.
An opt-in list was typed by its owners. A cold list was assembled, and every step of assembly introduces dead addresses:
Put together, raw cold lists typically run 10% to 30% invalid, against 1% to 3% for a maintained opt-in list.
Suppose a new domain sends 200 cold emails a day and 5% bounce. That is 10 hard bounces a day, every day. Mailbox providers read bounce rate as a direct measure of list quality, and a cold domain has no history to offset it. The usual sequence is:
Recovery takes weeks of warm-up at low volume. Verification before sending cuts the 5% to well under 1%, and a 1% bounce rate on 200 a day is 2 bounces, which most providers tolerate from a warming domain. The bulk list cleaning page covers what a full clean removes.
This is the hardest question in cold email. Many of the companies you most want to reach, especially mid-size and enterprise, run catch-all mail servers that accept every address, so a verifier cannot confirm a specific mailbox and returns risky. Catch-all domains explained covers why.
Dropping every catch-all throws away a large slice of the list. Sending to all of them reintroduces the bounces you were trying to avoid, because a wrong guess at a catch-all domain bounces late or vanishes after acceptance. The workable middle:
Before every sequence, not just once at import. A list verified in January and sent in May has lost several percent in between. The practical rule is a fresh check on any address older than 30 days, and the 24-hour cache means re-verifying a list you ran yesterday costs nothing. Upload through the dashboard or push through POST /api/v1/bulk with up to 50,000 addresses per job and a callback_url to notify your sequencer when results are ready.
| Verdict | Score | Outreach action |
|---|---|---|
| Deliverable | 90 to 100 | Add to the main sequence |
| Risky, catch-all | 60 to 89 | Small batches from a secondary domain, watch bounces |
| Risky, role address | 60 to 89 | Usually skip; info@ rarely replies and complains more |
| Unknown | 30 to 59 | Recheck in 48 hours, send only if it clears |
| Undeliverable | 0 to 29 | Remove, and fix the pattern that produced it |
| Free provider (gmail.com and similar) | Any | Route separately, see below |
The free flag deserves its own rule. A B2B prospect using a Gmail address is either a sole trader or a stale record, and the two deserve different messaging. The free email detector flags them in bulk, and free providers vs business domains goes into how to route them.
This is general information, not legal advice; the rules differ by country and the detail matters.
None of these laws is satisfied by verification alone. Verification keeps your bounces down; your process has to keep the opt-outs honoured and the sourcing documented.
A new sending domain should start at 20 to 50 messages a day and roughly double weekly as long as bounces stay under 1% and complaints near zero. Cold programmes typically cap a domain at 200 to 500 a day even when warm, and split volume across several domains. Keep cold sending on domains separate from the one your company uses for customers and transactional mail, so that a bad week in prospecting can never take down invoices and password resets. Verification is what makes the warm-up curve hold: one unverified import can undo a month of reputation.
Yes, but in controlled batches from a secondary domain, and only when there is some other evidence the address is right. Never mix them into the primary domain's volume.
Before every sequence, and at least every 30 days for anything still in rotation. Rechecks of the same address within 24 hours are free.
No. It tells you which addresses can receive mail, not whether you have a lawful basis to contact them. Sourcing, relevance and a working opt-out are separate requirements.
Under 1% hard bounces. Anything approaching 2% on a cold domain will show up as throttling within days.
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