Cold email tools send. They do not clean.
Every cold email tool is good at something — sequencing, inbox rotation, warmup, scheduling. None of them removes the need for a quality gate before the list enters.
The list enters your sender and carries everything that was in it. Invalid addresses bounce. Catch-all domains produce uncertain results. Role-based inboxes get filtered or ignored. Stale records reach people who have left the company. None of that is a sending problem. All of it is a list problem, and list problems should be resolved before the sender is ever involved.
| Layer | Responsible for | Not responsible for |
|---|---|---|
| Lead source | Producing contact records | Confirming deliverability |
| BillionVerify | Verifying and segmenting emails | Sending messages |
| Warmup | Building sender reputation | Fixing bad records |
| Sender | Executing campaigns | Deciding what enters |
Bad lists damage more than bounce rate.
A bounce is the visible symptom. The damage usually starts earlier and runs deeper.
| Risk | What it looks like | Why it compounds |
|---|---|---|
| Hard bounce | Invalid address rejected at delivery | Sender reputation drops with each bounce |
| Soft bounce accumulation | Repeated failures on the same domain | Mailbox providers start throttling traffic |
| Spam trap hits | Address was deactivated and re-used as a trap | Immediate reputation damage, hard to undo |
| Low engagement signals | Valid emails that never open or click | Inbox providers deprioritize future sends |
| Domain reputation decay | Too many bad records from the same campaign | Rebuilding takes weeks, not days |
Warmup does not reverse these. Warmup builds reputation for healthy infrastructure. It cannot absorb the cost of weak records.
Know each signal before you send.
BillionVerify checks every address and returns a signal. Each signal requires a different action before the record enters your sender.
| Signal | What it means | Cold email action |
|---|---|---|
| Valid | Mailbox exists and accepts mail | Send if the contact matches your campaign |
| Invalid | Mailbox does not exist or rejects permanently | Remove before import |
| Catch-all | Domain accepts all addresses — exact mailbox uncertain | Segment separately, use caution or enrich |
| Role-based | Shared inbox such as info@, sales@, support@ | Separate group, adjust messaging for shared ownership |
| Disposable | Temporary or low-trust address | Remove |
| Unknown | Result not clear enough for automatic sending | Review before committing to high-volume send |
| Domain or MX issue | Technical problem with the address or domain | Remove or fix before sending |
The standard pre-send flow.
This order matters. Verification before import keeps weak records out of the sender before campaign pressure makes them hard to remove. Warmup after verification means infrastructure builds on a clean base.
Apply different rules for different scenarios.
Your sending context changes which signals need the most attention.
| Scenario | Verification priority |
|---|---|
| Gmail sender (GMass, Mailmeteor) | Check before syncing Google Sheets. Gmail accounts are sensitive to bounce spikes. |
| High-volume sender (Instantly, Smartlead) | Catch-all and unknown records need explicit routing rules before entering mailbox rotation. |
| Agency sending across clients | Each client list needs a separate verification pass and a separate suppression file. |
| Enterprise SDR team (Salesloft, Outreach) | Set import rules at the CRM or sequence level before records reach the sender. |
| Founder-led outbound | Small lists from a small number of domains — one bad batch causes proportionally more damage. |
Verify before any sender import.
Apply the right workflow before launch.
Compare cold email senders and verification options.
Cold email verification common questions.
1. Does warmup remove the need to verify?
No. Warmup builds sending reputation. It does not change whether a specific address exists or is safe to send to. A warmed inbox still bounces on invalid records.
2. Is a built-in verifier enough?
A built-in verifier is better than nothing. It is not the same as a dedicated pre-send quality gate applied before import. The difference matters when you care about catch-all policy, role-based handling, or unknown record routing.
3. Should I verify catch-all domains?
Yes. A catch-all domain accepts all addresses, which means the specific mailbox you are targeting may not exist. BillionVerify flags catch-all so you can route those records into a lower-volume, higher-caution segment rather than mixing them with confirmed valid addresses.
4. What bounce rate is dangerous for cold email?
Any consistent bounce rate above 2% is a signal to review your import process. Hard bounces above 5% on a campaign will begin to affect sender reputation. The right answer is to prevent bounces upstream, not to monitor them after they happen.
5. Should I delete all role-based emails?
Not automatically. A role-based address can be a legitimate contact path for many businesses. The right approach is to segment role-based records separately, adjust your messaging for shared inboxes, and avoid mixing them into personal-contact sequences where the targeting assumption does not hold.
6. How often should I re-verify a list?
Any list older than 90 days should be re-verified before reuse. Inbox conditions change. Employees leave. Domains expire. A list that was clean three months ago may carry new risk today.