How often should you re-verify your email list?

The honest answer to “how often should I re-verify?” is: it depends on what the list is about to do. A brand-new import you’re mailing tomorrow and a segment that’s been sitting untouched for eight months carry very different risk, so a single interval can’t serve both. The reliable approach is to attach verification to events in the list’s life rather than to the calendar — verify when data enters, and verify again just before you rely on it.

Why email lists decay

Email lists rot quietly. People change jobs and their work address dies. Consumers abandon inboxes. Domains lapse, providers shut down free-mail services, and mailboxes that filled up get deactivated. None of that generates a notification — the address simply stops working, and you only find out when you send and it bounces. Across the industry, list decay is commonly estimated at around 20–30% per year (that’s a widely cited industry figure, not a VerifyAnyEmail measurement). At that rate, an address you verified as good last year has a meaningful chance of being dead today — which is exactly why a one-time verification isn’t enough.

Verify at import — the first trigger

The cheapest place to catch a bad address is before it ever enters your list. Verify at every intake point:

• Sign-up forms: validate in real time so typos and dead addresses never get stored, and so you catch disposable and role addresses at the door (more on those in the disposable & role-based guide).
• Bulk imports: a purchased list, an event export, or a CRM migration should be run through verification before you send it a single message.
• Re-added contacts: anyone coming back into the list after being suppressed gets re-checked, not waved through.

Verifying at import means most of your list is already clean, and later re-verification only has to catch the decay since.

Re-verify before every major send

Before any high-stakes campaign — a product launch, a Black Friday blast, a big announcement — re-verify the list you’re about to mail. This is the single most valuable trigger, because it’s the moment a stale list does the most damage: a spike of bounces from months of accumulated decay, all in one send, is exactly what pushes you past the ~2% bounce threshold that Gmail, Yahoo and Outlook watch. Re-verifying first turns that spike back into a trickle. Fold it into your pre-send routine alongside the rest of your list-cleaning workflow.

Re-verify before re-engaging dormant or inactive segments

The riskiest mail you can send goes to people you haven’t mailed in a while — and that’s precisely where decay concentrates. Two triggers here:

• Dormant segments: before a win-back or re-engagement campaign to subscribers who’ve gone quiet, re-verify. Many of those addresses are dead, and some abandoned mailboxes get recycled by providers into spam traps — mailing them is a fast way to hurt your reputation.
• After a period of your own inactivity: if you paused sending for a season (or your side of the business went quiet), the whole list has aged. Re-verify before you resume, because months of silence means months of unmeasured decay.

For why re-engaging a stale list quietly wrecks deliverability, see the bounce-rate guide.

How to run and automate re-verification

Make the triggers routine, not heroic:

1. Check the list’s state first. Pull an Email List Health Report to see what share is deliverable, catch-all, unknown or risky — that tells you how urgently a full re-verify is needed.
2. Re-verify the list with the Email Verifier before the send, and suppress everything that comes back undeliverable.
3. Catch decay continuously by always removing hard bounces the moment they happen — every bounce is a free re-verification signal your sends hand you for nothing. See reducing bounce rate.
4. Validate at the edge with real-time verification on sign-up and API-based checks on import, so the list stays clean between big re-verifications.
5. Let engagement do the rest. Segment by opens and clicks; contacts that never engage are your next re-verification (or suppression) candidates regardless of the calendar.

Failure modes to avoid

• Promising a fixed interval. “Re-verify every 30/60/90 days” sounds tidy but ignores what the list is actually doing — a dormant segment needs it sooner, an actively-mailed one that already sheds bounces may not need a full pass. Triggers beat timers.
• Verifying once at import and never again. That ignores decay entirely; the list is stalest exactly when you least expect it.
• Re-engaging a dormant segment without re-verifying. The classic reputation own-goal — old addresses and recycled spam traps in one send.
• Not removing hard bounces immediately. Every send re-verifies your list for free; ignoring the results means mailing known-dead addresses again next time.
• Treating catch-all/unknown as clean. They’re unconfirmed — handle them per the catch-all guide rather than assuming a green light.

Sources

List decay of roughly 20–30% per year is a widely cited industry estimate, not a VerifyAnyEmail measurement — treat it as a planning heuristic, not a guarantee. The reputation stakes that make re-verification worthwhile come from the mailbox providers themselves: Google’s Email sender guidelines spell out the low bounce and complaint rates senders must hold, and Yahoo’s sender best practices echo them. Pair this with the list-cleaning guide to build the full routine.