Treat verification as a time-bound signal. Email verification is not permanent because people change jobs and domains change settings.1 Even carefully verified lists become risky within weeks.2 Use two clocks: a recurring cycle for the stored database and a pre-send check for records tied to the next meaningful send. A clean historical status does not tell you what is true when you use the record, and many teams miss that second check.
The recurring cycle keeps active records from sitting untouched until a campaign exposes the damage. Set up automated refresh cycles, verify contact data for active accounts at least quarterly, and verify target-account data before significant outreach.3 Let verification cadence guide coverage, with database size as a secondary consideration.4
Apply the recurring check to records you still plan to use. Save the verification date, the result, and the reason for any rejection or review status. Keep records with no current result out of outbound until they pass a fresh check. The cycle is complete when every active record has a recorded outcome and a next review point.
Use the second clock close to the action. It catches changes after the routine refresh, so an old status does not clear a new campaign. Verify the list shortly before sending, especially for cold campaigns.5 Do this even when a target account passed its recurring refresh. For each record, confirm that the contact detail is still eligible for the send, then route anything uncertain out of the send queue until someone resolves it.
An eight-week experiment found that 5.5 percent of verified emails degraded, with 2.3 percent becoming invalid and 3.2 percent becoming accept-all.6 Those results give the pre-send check a separate job from the quarterly refresh: the recurring check protects the database, while the pre-send check protects the campaign.
Proceed when every recipient has a recent check result and a clear send disposition. If the list still contains unresolved records, hold that portion of the campaign and continue with the records you can clear.
The check's value comes from what you do with its result. Treat each outcome as a routing instruction and keep the disposition visible in the workflow. A passing result can continue toward send. An invalid result should leave the send queue. An accept-all result should enter a review path because its status remains uncertain even when the address has not produced a bounce.
Record the outcome on the contact record and preserve the date of the check. Keep rejected and review records separate from cleared records so a later campaign cannot pull them back through a broad filter. If the same account produces several uncertain results, give that account a tighter review trigger before the next outreach.
Use the outcome to decide when the record can move again. A record that passes today can return to the recurring pool after the campaign, while a rejected record needs a new reason to be considered.
Campaign performance shows when the current cadence is too loose for a segment. Respond to the affected records first, then decide whether the wider account group needs the same treatment. When a segment produces an unusual bounce pattern, stop that segment, run verification again, and clear the affected records before the next send. Keep remediation tied to the segment that produced the problem so one bad batch does not force unnecessary work across the whole database.
After each cold campaign, compare the result with the segment's prior behavior. A worsening pattern calls for a shorter path from refresh to send. A clean result lets the segment return to its normal recurring cycle, with the pre-send gate still in place.
What not to do
A refresh schedule can look active while stale or uncertain records still reach outreach.
- Sending invalid emails into a campaign causes hard bounces that directly damage sender reputation.7
- Treating accept-all addresses as cleared increases risk and uncertainty even when they do not bounce immediately.8
- Leaving stale data in rotation leads to missed prospects and long-term deliverability issues.9
- A cold outreach bounce rate above approximately 2 percent is a red flag and needs investigation.10
Put the recurring check on the active-account schedule and make the pre-send check a release gate for target outreach. Log every result so the next review starts with a known status, a date, and a clear action. If bounce behavior worsens, tighten the affected segment before sending again.