A verified B2B email list starts losing good addresses within weeks. When we re-checked 520 B2B contacts that a verifier had marked deliverable about 10 weeks earlier, 23% came back invalid and another 10% had turned catch-all (our data, October 2026). A list verified the week before sending bounced at 0%. Re-verify within 7 days of every send.
What happened when we re-verified a 10-week-old list?
Two in three addresses were still valid. In late July 2026, MillionVerifier marked a set of fintech and B2B contacts as deliverable. On 6 October 2026 we ran 520 of those same addresses through OmniVerifier and compared the results (our data, October 2026).
| October result | Contacts | Share of 520 |
|---|---|---|
| Valid | 349 | 67% |
| Catch-all | 53 | 10% |
| Invalid | 118 | 23% |
Two different tools ran the two checks. Part of the gap can come from the way each tool scores a mailbox, so treat 23% as the loss we saw in practice, with the tool effect included. For a team that verifies once with one vendor and then sends for months, that is the number that matters.
The list came from one batch of fintech and B2B contacts. Other sectors and other data sources can decay at different rates, so run the same re-check on your own list.
How much does list age raise the bounce rate?
Enough to trip the pause rule we run on every campaign. On the first 600 cold emails of one campaign, a list verified the week before sending bounced at 0%. Lists verified about 10 weeks earlier bounced at 3.7% to 5.2%. A crypto and web3 list from the same July batch bounced at 0.9% (our data, October 2026).
The samples are small, between 43 and 219 sends per segment. In a 43-send segment, one extra bounce adds 2.3 points to the rate. Trust the direction of the result more than the decimals. The sample is also too small to explain why the crypto list held up better than the other 10-week-old lists.
Our rule is to pause a campaign the same day its bounce rate passes 3% (our rule, October 2026). The lists at 3.7% to 5.2% would have tripped it. The week-old list, at 0%, stayed well under.
Why do verified addresses go bad so fast?
People leave their jobs. The median US wage and salary worker had been with their current employer for 4.1 years in January 2026, and the median for workers aged 25 to 34 was 3.0 years (BLS, September 2026). When a contact leaves, their old company often closes the mailbox, and the next email bounces.
Mail servers change too. A company can move to a new email provider or switch its domain to accept every address. When that happens, an address that verified cleanly in July returns "catch-all" in October, because the server now says yes to everything.
Verification also has a blind spot. A verifier asks the mail server whether a mailbox exists, without sending a message. If the person left but the company kept the mailbox open, the verifier still says valid. The email delivers, and nobody reads it.
How often should you re-verify a B2B list?
Before every send, whenever the last check is more than 7 days old. This is the cadence we use, with the reason for each row.
| Age of last verification | What to do | Why |
|---|---|---|
| 0 to 7 days | Send | Our week-old list bounced at 0% (our data, October 2026) |
| 8 to 30 days | Re-verify the whole list before the first email | We have no data point in this range, so we re-check |
| 31 days or older | Re-verify, then plan for a smaller list | Our 10-week-old list lost 23% to invalid and 10% to catch-all (our data, October 2026) |
| Any age, after a job-change or hiring signal | Re-verify that contact and confirm the title | The signal itself means the contact may have moved |
Sequences stretch the gap. If step three of a sequence goes out three weeks after step one, the address in step three is three weeks older than the address you verified. Re-verify before you add a list to a sequence, and again before you restart a paused sequence.
What should you check before every send?
Run this list in order before each campaign or each new segment.
- Re-verify every address last checked more than 7 days ago.
- Remove every invalid result. Keep "unknown" results out of the main send.
- Move catch-all addresses into their own segment.
- Confirm each contact still holds the title at that company. A verifier checks the mailbox, and only a profile or a website check confirms the job.
- Drop any contact whose title names a different company. Contact databases mix up records, and we found a founder title from one firm on another firm's record (our data, October 2026).
- Send the first part of each segment, then read the bounce rate before you send the rest.
- Pause a campaign the same day its bounce rate passes 3% (our rule, October 2026).
- Cut the volume if messages start to bounce or defer, and raise it again slowly. Gmail's sender guidelines give this advice, and also say to unsubscribe recipients after multiple bounced messages (Google, accessed October 2026).
- Keep spam complaint rates in Google Postmaster Tools below 0.3%, and aim for below 0.10% (Google, accessed October 2026).
- Use lists you built or enriched yourself. Gmail's guidelines say: "Don't purchase email addresses from other companies."
Step 5 matters most for lists built from buying signals, where one wrong match sends a confident email to the wrong firm. We cover that failure in which buying signals predict a B2B purchase.
What should you do with catch-all addresses?
Send to them last, in their own segment. A catch-all server accepts mail for any address at the domain, so no verifier can confirm that a specific mailbox exists. In our re-check, 10% of the list landed in this group (our data, October 2026).
Send the clean segment first. Once its bounce rate holds below your pause line, release the catch-all segment in small batches and watch its bounces separately. If the catch-all segment bounces, stop it and keep the clean segment running. If you mix the two, you cannot tell which segment caused the bounces.
For a small list, catch-alls can be the difference between enough contacts and too few. Keep them, in their own segment. If you are deciding whether to run this process in-house or hand it to a partner, read outbound agency vs in-house SDR team.
To have every list re-verified in the week before it sends, see Outbound, from $5K a month plus a fee per meeting held.