What Email Verifier does
Email Verifier returns the repository's documented verification states from supported checks. It does not claim to eliminate future delivery failure.
Check documented email signals
Email Verifier preserves uncertainty
Evaluate supported format, domain, mail-server, disposable-address, role-address, and risk signals. A verification state does not guarantee delivery.
Supported input and returned output
Supported inputs
- Business emailSubmit one syntactically reviewable email address.
- Request contextUse the permitted workspace or scoped API context.
- Batch columnMap an email column in an approved CSV workflow.
Returned outputs
- Verification stateReceive verified, likely valid, risky, catch-all, unknown, or invalid when supported.
- Checked signalsReview available format, domain, mail-server, disposable, and role-address signals.
- Evidence contextSee confidence, freshness, and explicit unknown fields.
Typical workflow
-
Validate input
Confirm that the submitted value is a reviewable email.
-
Run supported checks
Evaluate the checks implemented by the current contract.
-
Normalize the state
Return a documented state without hiding uncertainty.
-
Review before use
Use the state as evidence, not as a delivery promise.
Primary use cases
Single-record review
Check one business email before saving a record.
CSV quality review
Evaluate an approved email column and retain row-level outcomes.
API validation
Request a documented state from a scoped interface.
Data confidence and field provenance
Verification confidence
Confidence reflects the available checks and can remain uncertain when evidence is incomplete.
Verification evidence
The result records safe check context and observation time without exposing protected response data.
Use through Workspace, CSV, or API
Workspace
Review a verification state next to the contact record.
CSV
Process approved rows while retaining invalid and unknown outcomes.
API
Use the documented verification endpoint with a scoped key.
Product maturity
Email Verifier
AvailableAvailable for the documented signals; the result does not prove mailbox delivery.
Not included or not currently available
- No delivery guaranteeA positive state cannot predict every future mail event.
- No forced certaintyIncomplete evidence remains unknown or risky.
- No invented checksOnly checks implemented by the current contract are shown.
Trust and controls
Stable states
The page uses only documented verification states.
Safe errors
Service details and protected configuration are not exposed.
No automatic send
Verification does not send an outreach message.
Frequently asked questions
No. It reflects supported checks at the time of evaluation.
The available evidence was not sufficient for a stronger supported state.
Yes. Approved batch workflows retain row-level states.
Related products
Use evidence, not promises
Review supported email checks
Create a workspace to use permitted verification workflows, or log in to continue.