Home › Blog › How Old Can an Email List Be Before You Reverify It?
How Old Can an Email List Be Before You Reverify It? (The Decay Math)
A list verified in January is not verified in April, people change jobs, mailboxes get deactivated, and every month of shelf life converts a slice of your valid rows into future bounces. Here is how fast B2B email data actually decays, the reverification windows that keep bounce rates safe, and the test that measures decay on your own lists.
Quick Answer: 30 Days Free, 60 Days Careful, 90 Days Always
Counting from last verification: under 30 days, send; 30-60 days, reverify when the campaign matters; past 60 days, always; past 6 months, treat as never verified. B2B data decays roughly 2-3% a month from job churn, unevenly by segment, so measure your own curve: reverify samples of 7/30/60/90-day-old lists and read the invalid rate by age. Verification belongs at send time, and the last-verified date belongs as a column in your master database.
Why Valid Rows Go Bad on the Shelf
Nothing happens to your CSV; everything happens to the humans in it. People change jobs and their mailbox is deactivated within days; companies migrate providers and old addresses die; startups fold; IT teams purge dormant accounts in quarterly cleanups. Every one of those events converts a genuinely-valid-in-January row into a hard bounce in April, and none of them announce themselves. The database badge problem is this same decay wearing a vendor logo: "verified" always means verified as of some date, and the date is the load-bearing part.
The Aging Test and the Policy It Produces
SAMPLE 300+ rows each from lists last verified
~7, ~30, ~60, ~90 days ago
RUN all samples through your stage-1 verifier
today
READ previously-valid rows now invalid/unknown:
7d ~0-1% (baseline noise)
30d ~2-3% ← typical
60d ~5-8%
90d ~8-12% (segment-dependent!)
SPLIT by source + audience: startup/tech lists
decay ~2x enterprise lists
POLICY set reverify windows per segment where the
curve crosses ~2% projected bounce impact,
because 2% is where the warning band starts
(bounce stop rules post)- •Store last_verified per row, and let campaign prep read it: anything outside its window re-enters the waterfall automatically. Policy that depends on memory is not policy.
- •Reverification is cheaper than the first pass: aged lists mostly re-confirm, so the specialist stage sees only rows that flipped, and the marginal cost per list is small against the bounce risk it removes.
- •Watch decay after layoff news in your target industry: churn events are lumpy, and a sector shedding staff can double a segment's monthly decay for a quarter. The aging test after any such wave recalibrates your windows fast.
Frequently Asked Questions
How old can an email list be before it needs reverifying?
Our operating windows, counting from the last verification date: 0-30 days, send without re-checking; 30-60 days, reverify if the campaign matters (cheap insurance at bulk-verifier prices); 60+ days, always reverify, no exceptions; 6+ months, treat it as an unverified list entirely and run the full waterfall. The driver is employment churn: B2B contact data decays at very roughly 2-3% per month as people change roles, which compounds a January-verified list into meaningful bounce risk by spring.
How fast does B2B email data actually decay?
Industry estimates cluster around 25-35% per year for B2B contact data overall, roughly 2-3% a month, but the rate is wildly uneven by segment: startup and tech contacts churn fastest (job tenure is short), senior enterprise roles slowest, and recession or layoff waves spike everything. Which is why the useful number is not the industry average but YOUR decay rate per segment, measurable with the aging test below in one afternoon of setup.
How do I measure decay on my own lists?
Take lists you verified 7, 30, 60, and 90 days ago, pull a few hundred rows from each, and reverify them today. The share of previously-valid rows that now come back invalid or unknown IS your decay curve, by list age. Segment it by source and audience and you will find your windows: maybe your enterprise lists hold 90 days while your startup lists rot in 45. Set reverification policy from that curve instead of a blog's average (including this one).
Does reverification cost justify itself on a barely-aged list?
Run the math: reverifying 10,000 rows at bulk prices costs ~$20; a 2% decay slipped into a campaign is 200 hard bounces, which at typical volumes is the difference between a healthy fleet and tripping the 2-3% warning band on every domain that sent the list. Bounces cost placement on every FUTURE send from those domains, so the comparison is $20 versus compounding reputation damage. Past 30 days of age, reverification is always the cheap side of that trade.
When exactly should verification happen in the workflow?
At send time, not at acquisition time. The correct habit: verify (or reverify) as the last step before a list enters the sequencer, so the verification date and the send date are days apart, not months. Lists sitting in your master database carry their last-verified date as a column, and campaign prep begins by checking that date against your windows. Scrape-time verification expires quietly on the shelf; send-time verification is the only kind that protects the campaign actually being sent.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes