B2B email list decay: why work addresses go stale and when to re-verify
· 4 min read · Email validation
B2B email lists decay because work addresses are tied to a job, and jobs end. When someone leaves, their employer usually disables the mailbox, and your perfectly valid record starts hard bouncing. Companies also rebrand, get acquired or move to a new domain. The fix is to re-verify any segment you haven't mailed recently before you send to it, and to treat verification results as having an expiry date.
Why work addresses stop working
People change jobs. The US Bureau of Labor Statistics reports that median tenure with the current employer was 4.1 years in January 2026, and 3.0 years for workers aged 25 to 34. A median of current tenure isn't the same as an annual turnover rate, so don't turn it into a "percent per year" figure. It does tell you that a contact list of mid-career professionals is not a stable asset over a couple of years.
Mailboxes get disabled, not just deleted. Depending on the company's mail setup, a departed employee's address may reject mail outright, forward to a manager for a while, or keep accepting mail into a shared mailbox. The first produces a hard bounce. The others look deliverable but reach the wrong person.
Domains change. Acquisitions fold one domain into another. Rebrands move everyone to a new domain and the old one may stop accepting mail after a transition period. Startups shut down and their domains lapse.
Roles get reshuffled. marketing@ or partners@ may be re-routed or retired as teams change.
None of this shows up in your CRM until you mail the address or check it.
What decay costs you
The obvious cost is bounces, and bounce rate is one of the signals mailbox providers and sending services watch. Amazon SES recommends staying below 2% and suggests that if you must mail addresses you haven't contacted lately, do it with only a small portion of your overall sending. SES also notes that spam traps can be built from addresses that "were once valid, but have been unused (and bouncing) for an extended period of time". Mail a dead address long enough and it might turn into a trap.
The quieter cost is wasted pipeline. Sequences sent to people who left, reps chasing accounts through contacts who can't answer, lead scores built on stale records.
How to spot decay in your own data
You don't need an industry statistic. You have better data:
- Bounce rate by contact age. Group sends by when the contact was created or last verified. If contacts older than a year bounce at several times the rate of new ones, that's your decay curve.
- Quarterly re-verification sample. Re-verify a random sample of a few hundred contacts each quarter and count how many moved from
validtoinvalid. That gives you an actual rate for your audience. - Out-of-office and "no longer with" replies. Route auto-replies somewhere you can count them. They often arrive before the mailbox is disabled, which makes them the earliest signal you get.
A re-verification cadence that works
| Data | When to verify |
|---|---|
| New leads from forms | At capture, in real time |
| Imported or purchased lists | Before the first send, every time |
| Active segments you mail weekly | Rely on bounce suppression; spot-check quarterly |
| Segments not mailed in 3+ months | Before the next send |
| Contacts going into a new outbound sequence | Before enrollment if last verified more than about a month ago |
The pattern: the longer a contact sits unmailed, the less you know about it. Verification resets that clock, and a send that doesn't bounce resets it too.
Re-verifying without busywork
Do it where the data lives. In a CRM, keep a "last verified" date next to the status and let a workflow re-check contacts when it gets old. Verifying emails in HubSpot and Salesforce lead email verification show the setup for each.
With pingutil, /v1/verify/batch checks up to 50 addresses per request and returns status, reason, score and a checked_at timestamp you can store as the last-verified date. Results are cached for 30 days, so a monthly re-check is the natural rhythm; a request inside that window returns the cached answer with cached: true. For one-off lists, the dashboard takes CSV uploads of 50 rows at a time. See the verify API docs or try a few addresses on the email verification page.
Verification reports what the mail server says today, which has limits. An address that now forwards to a manager or a catch-all domain may still look fine, and catch-all domains come back risky (accept_all) because the server accepts everything. For those, engagement is the better signal: if nobody has opened or replied in months, stop mailing. More on reading those results in catch-all email domains.
Put a "last verified" field on every contact this week. It's the one change that makes decay visible.
Questions people ask
- How fast does a B2B email list decay?
- There is no reliable public figure for it, and it varies with your audience. Lists heavy with younger employees, startups or high-turnover roles decay faster. Measure it yourself by re-verifying a sample of your list every quarter and tracking how many valid addresses turn invalid.
- Can a work email become valid again after it bounces?
- Sometimes. A company may reassign an address to a new employee or restore a mailbox. That is a reason to suppress hard-bounced addresses rather than re-verify and re-mail them: even if the mailbox exists again, the person who gave it to you is gone.