How Often Should You Re-Verify Your Email List? A Cadence Guide

Re-verify any address you have not verified or successfully mailed in the last three months, immediately before you send to it. Verify every new address at entry. Cold B2B lists should be checked before every campaign; lists mailed weekly mostly clean themselves through bounce suppression. Schedule by trigger, not by calendar, because what matters is how long since you last knew the address worked.

That rule of thumb sits on two sets of facts: how fast the things behind an address change, and how long a verification result stays true. Both are sourced below. Where we give a cadence that is our judgement rather than a published figure, we say so.

Why addresses go bad

Addresses die for two main reasons: people leave jobs, and providers close mailboxes nobody uses. Neither is visible from your side until you check or send.

People change jobs

A work address almost always stops working when its owner leaves. The US Bureau of Labor Statistics gives two measures of how often that happens:

• Tenure. In its January 2026 tenure survey, released 24 September 2026, the median time wage and salary workers had been with their current employer was 4.1 years. For workers aged 25 to 34 it was 3.0 years.
• Monthly separations. In its JOLTS release for August 2026, published 29 September 2026, total separations were 5.1 million, a rate of 3.2% of employment, in that single month.

These are economy-wide figures, not email data, and they do not translate directly into an email decay rate: some jobs turn over far faster than others, and not every departure closes a mailbox straight away. What they establish is the scale. In any given month, millions of US jobs end, and each one that came with a work address usually takes that address with it. Lists of younger professionals and high-turnover roles decay faster than lists of senior, long-tenure ones.

We have not found a primary-source figure for B2B email decay specifically, so we do not quote one. You will see widely repeated percentages online; we could not trace them to a published dataset. More on this in how fast B2B contact data decays.

Consumer providers close unused mailboxes

The big consumer providers each publish an inactivity rule:

Provider	Published rule	Source
Outlook.com / Hotmail	Mailbox closed and email deleted if not signed in "at least once in a one-year period"	Microsoft Support
Yahoo Mail	Mailbox inactive after 12 months without access; it "stops receiving new emails"	Yahoo Help
Gmail (personal)	Account may be deleted after 2 years unused, from 1 December 2023	Google Account Help

So a consumer list that has not been mailed for a year can contain Hotmail and Yahoo addresses that were real and engaged when collected and are now closed. Provider-specific details are in verifying Outlook and Hotmail addresses, why Yahoo addresses are hard to verify and checking a Gmail address.

How long a verification result stays true

A result describes the mailbox on the day of the check, and vendors themselves put short windows on their confidence. Two published examples:

• Clearout's documentation says its "safe to send" status holds "provided emails are sent within 24 hours of the verification time".
• Bouncer's guarantee covers addresses marked deliverable that bounce "within 72 hours after verification".

Neither says results are useless after that. Most mailboxes that exist today will exist next month. But the windows show where vendors are willing to stand behind a result, and it is days, not quarters.

Triggers beat calendars

The question that matters is "how long since I last knew this address worked?", and a calendar schedule answers it badly. An address you mailed successfully last week does not need verifying. An address imported two years ago and never mailed does, whatever the calendar says.

Three events tell you an address is known good:

1. It was verified as valid.
2. You sent to it and it did not bounce.
3. The person replied or clicked.

Track the most recent of those per address. That date, not the date of your last bulk clean, decides whether to re-verify.

The triggers

Trigger	Action
A new address enters your list (form, import, finder, CRM entry)	Verify it now, before it is ever mailed
You are about to mail addresses with no known-good event in the last 3 months	Re-verify those addresses just before the send
You are reactivating a segment not mailed for 6 months or more	Re-verify all of it, then send a small batch first
A campaign's bounce rate jumps above your normal level	Stop, re-verify the remaining unsent addresses
You import a list from a colleague, vendor, event or acquisition	Verify all of it, regardless of what you are told about its age
Hard bounce received	Suppress immediately; no re-check needed

The 3-month and 6-month thresholds are our judgement, chosen to sit comfortably inside the one-year closure rules above and to reflect monthly job turnover. Tighten them for cold B2B, loosen them for engaged consumer lists.

Cadence by type of list

The right frequency depends mostly on how often you mail the list and who is on it.

List type	How it decays	Suggested approach
Cold B2B prospects	Fast: job changes, and the list was never confirmed by the recipient	Verify immediately before every campaign or sequence. Re-verify anything older than about a month before follow-ups resume
Engaged newsletter, mailed weekly	Slowly, and bounces are suppressed automatically	Verify at signup. No bulk re-verify needed while sending is regular
Newsletter mailed rarely (quarterly or less)	Bounces accumulate between sends	Re-verify before each send
Customer list (transactional plus occasional marketing)	Moderate: consumer accounts close after a year unused	Re-verify segments that have not purchased or been mailed in 6 months before a marketing send
CRM contacts used by a sales team	Fast and uneven: depends on who updated what	Verify on entry; re-verify any contact before it enters a sequence. See email verification for SDR teams
Event or trade-show list	Typos at capture, then normal decay	Verify within days of the event, before follow-up. See cleaning an event attendee list
Old list being revived after a year or more	Highest risk, including possible spam traps from recycled addresses	Re-verify everything, send to a small confirmed batch first, and expect to drop a large share

Why regularly mailed lists need less

Your sending platform already removes hard bounces, so a list you mail often is being cleaned by every send. The cost is that each dead address bounces once before it is suppressed. On a list mailed every week, that is a handful of bounces per send, spread out. On a list left alone for a year, all of that year's decay arrives in one campaign, which is how a normally healthy sender ends up with a bounce rate high enough to trigger a review. Amazon SES, for example, documents that a bounce rate of 5% or more places an account under review.

That is the real case for re-verification: not that lists need cleaning on a schedule, but that gaps in sending let decay pile up, and re-verifying before the first send after a gap spreads the cost back out.

A note on caching

Some verifiers, including ours, cache results for a period so that re-checking an overlapping list does not repeat work. SimpleVerifier keeps confirmed results for 14 days. That means re-running a list within 14 days returns the earlier result rather than a fresh check, which is the right trade-off for routine overlap but worth knowing if you are re-checking because you suspect something changed this week. Transient failures are retried rather than cached.

Practical takeaway

Stop asking "how often" and start asking "how long since this address was last known good". Record that date per address, re-verify anything past three months before you mail it, verify every new address at entry, and treat any list returning from a long gap as a fresh, unverified import. If you want to see what a re-check finds on a single address before you commit to a whole list, use the free email verification tool.