Inspect
Parse the selected email column, count rows, detect malformed values, and map repeated addresses.

Refresh List separates file assessment from provider-backed mailbox verification. The result is a traceable workflow that keeps valid, invalid, and unknown outcomes distinct, preserves source-row context, and states the limits beside the result.
Last reviewed 18 September 2026 · No independent accuracy guarantee claimedFirst, RefreshScan inspects the file locally. After you review the eligible unique count, the authenticated workspace sends only those addresses to the configured verification provider. Refresh List records the provider outcome and reason, reconciles credits, and returns categorized exports with the original row context.
Duplicates and skipped rows are identified before any paid check.
Provider evidence is reported with its uncertainty and checking context.
Parse the selected email column, count rows, detect malformed values, and map repeated addresses.
Review the maximum unique requirement and reserve credits only after the input is understood.
Send eligible unique addresses to the configured provider. Surrounding columns stay in Refresh List.
Match returned rows to the source, keep reasons visible, settle credits, and export result groups.
A provider response can answer one question without answering every question about an address. Refresh List keeps the core outcome separate from additional signals such as role, catch-all, or disposable classifications when supported.
Verification cannot account for sender reputation, message content, consent, receiving policy, timing, or later mailbox changes.
Read the result status guideRefresh List uses a simple rule: one completed unique check uses one credit, regardless of whether the outcome is valid, invalid, or unknown. Duplicate and skipped rows are removed from the eligible set before verification.
A reservation is not the final bill. Unprocessed work can be returned at settlement; completed unknown checks remain chargeable because verification work was performed.
Provider performance varies by address, domain, time, and receiving behavior. Refresh List does not publish an unsupported benchmark.
Role, catch-all, and disposable signals depend on supported provider evidence or documented coverage.
A mailbox outcome cannot guarantee that a later message will be accepted or read.
Refresh List sends eligible unique addresses to the configured verification provider. Provider evidence and reasons determine the recorded outcome; Refresh List does not invent a confidence score or claim a universal accuracy rate.
No. Local preflight checks file structure, duplicates, and eligibility in the browser. It does not contact a mailbox or establish whether an inbox exists.
They are distinct provider-backed outcomes. Valid means the available evidence supports a positive result at that time; invalid means a conclusive failure; unknown means the available evidence was not conclusive.
Each completed unique check uses one credit, including valid, invalid, and unknown outcomes. Duplicate and skipped rows are excluded before verification. Unprocessed reservations can be returned at settlement.
No. Receiving systems, sender reputation, consent, message content, timing, and policy can affect delivery. Verification is evidence about a checking moment, not a delivery promise.
Read the result, the reason, the accounting, and the limitation together.