Inspect one address deeply.
Use the authenticated verifier when an operator needs the full evidence set, recommended action and durable receipt.
Read the decision guide →See how Clean thinks before you sign in.
Run a real non-SMTP preview through Clean’s existing verification engine, then follow the same evidence path used by Single Verify, Bulk Clean and the API.
LIVE NON-SMTP PREVIEW
Start with one address.
This public preview evaluates syntax, normalization, domain/routing signals, known risk markers and policy. It deliberately does not perform SMTP mailbox probing. That evidence is available only when SMTP probing is explicitly enabled for authenticated verification.
REAL ENGINENot a canned demo result.
NO SMTPPublic preview stays bounded.
SAME VOCABULARYDecision and evidence semantics stay consistent.
CLEAN PREVIEWRead technical trust
live
01Enter an address to inspect live evidence.
Clean will not fabricate a sample verdict while the field is empty.
ONE ENGINE, THREE SURFACES
The workflow changes. The trust model does not.
Apply the same rules to a list.
Upload CSV, preserve source rows, process persisted items and reconcile queued or running work after interruption.
Open the Bulk Clean guide →Put trust at the point of capture.
Use the versioned verification endpoint with tenant-bound API credentials and the same decision vocabulary used by the product UI.
Review the API contract →WHAT THIS TOUR PROVES
A product tour should clarify boundaries, not hide them.
PREVIEWUses the real Clean preview path.No canned address or predetermined outcome.
MAILBOXSMTP mailbox evidence is excluded here.Authenticated verification may perform bounded mailbox probing when it is explicitly enabled.
CONSENTVerification is not permission to email.Clean supplies technical evidence, not legal consent.
CERTAINTYUnknown is allowed to remain unknown.The model does not force every address into a positive or negative claim.
Move from preview to a decision you can preserve.
Open Clean for authenticated verification, receipts, Bulk Clean and API credentials.