Email list verification: account for the whole database

Email list verification applies mailbox checking to a database while recording how the input was handled. A useful output is more than a valid-address file: it maps source rows, skipped records, duplicate addresses, verification outcomes, and credit accounting so your team can review the batch and explain its treatment.

Last updated 2026-09-14. Read the scope and limitations before applying a result.

Key points

Record source and unique counts.
Keep a full report.
Reconcile each batch.

Detailed explanation

Confirm column and header selection before processing. Completed and unprocessed counts should account for the eligible set; retain checking dates across batches.

Example

A client handoff retains CRM IDs beside results instead of requiring a manual merge.

How RefreshList handles it

Jobs track eligible, processed, valid, invalid, and unknown counts, with free duplicate and skipped-row assessment.

Limitations

Differently dated batches cannot truthfully share a single freshness claim.

Methodology and sources

Product behavior is described from the current RefreshList implementation and provider contract. Protocol context should be checked against the applicable standards and provider documentation. This page does not create a benchmark or certification.