Email validation vs verification

Email validation usually asks whether an address has acceptable structure. Verification asks whether available mailbox evidence supports an outcome. Vendors sometimes use these terms differently, so inspect actual checks rather than labels. RefreshList explicitly separates free local structural preflight from paid provider-backed mailbox verification throughout the workflow.

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

Key points

Syntax is not mailbox existence.
Preflight precedes reservation.
Read the actual methodology.

Detailed explanation

Structural rules reject obvious malformed input without contacting a service. Mailbox checking is separate and may still be inconclusive. Neither establishes permission to send.

Example

name@example.com can look plausible while its mailbox remains unchecked.

How RefreshList handles it

Local tools label structure and mailbox status separately. Actual verification uses the configured workspace.

Limitations

The local rule is basic and may not support advanced valid address syntax.

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.