Invalid email results: retain the reason

An invalid email result is a conclusive verification failure for an eligible address. It differs from malformed input skipped before checking and from an unknown outcome without a conclusion. Keep the reason attached to the source row so you can exclude it or investigate a correction without guessing a replacement address.

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

Key points

Invalid checks consume credits.
Malformed skipped rows do not.
Never invent a correction.

Detailed explanation

Investigate typos against authoritative records. Guessing can direct information to someone else. Retain original values beside confirmed updates.

Example

A missing @ is skipped; a structurally eligible address can be checked and return invalid.

How RefreshList handles it

Preflight reasons and provider outcomes remain separate, with an invalid-result export.

Limitations

The product cannot prove the correct replacement address. A failure relates to its checking context.

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.