Email List Decay: When to Reverify Existing Contacts

Start with the decision boundary: reverification should be triggered by observed risk and contact age, then validated with a cohort or holdout. is evidence for a sending decision, not a guarantee of acceptance, inbox placement, relevance, permission, or replies. Keep the original value, the observation time, and the rule that converted evidence into an action. This makes a list change explainable when a later event disagrees.

A practical workflow

1. Segment by age and source

Store collected_at, last_checked_at, source, role, domain, and prior event history. Compare cohorts rather than averaging the whole database; a recent opt-in and an old enrichment export should not share one freshness assumption.

2. Choose a testable hypothesis

Start with a proposed cadence only as an operational hypothesis. For example, select older or higher-risk cohorts for review, while leaving a comparable holdout. Do not publish the interval as a universal rule.

3. Recheck before high-impact sends

Trigger reverification when a list is old relative to your observed risk, a domain/source changes, repeated soft bounces accumulate, or an import is about to enter a large campaign. Keep the prior observation instead of overwriting it.

4. Act on unknowns explicitly

Route invalid, disposable, catch-all, role, and unknown outcomes to separate actions. If results conflict with delivery events, preserve both records and investigate the method, timing, and address history.

Decision table

Situation	Evidence to retain	Default action
Older cohort	Age, source, prior events, new result	Review or suppress based on policy
Recent hard bounce	Event ID, SMTP result, checked_at	Suppress address and investigate
Unknown or timeout	Method, retry count, timestamp	Hold for review; do not promote
Stable low-risk cohort	Sample size and holdout outcome	Continue monitoring; no automatic release

Edge cases and guardrails

There is no defensible universal answer to “how often should I reverify?” Domain changes, source quality, contact type, send volume, and your own event data matter. Opens are not a reliable sole trigger for reactivation or freshness decisions; use delivery and preference evidence too.

How this fits with list operations

Use RepMail’s existing list-hygiene and suppression guidance as the operational gate, while keeping re-verification observations in your data model. Do not describe a platform check as a permanent mailbox guarantee. Start with the lead-generation academy, then use the list hygiene checklist for the audience gate, the verification status model for technical outcomes, and the outbound suppression rules for cross-system enforcement.

Sources

• Google email sender guidelines
• Twilio SendGrid Email Address Validation
• Amazon SES account-level suppression list