Normalize
Interpret syntax, Unicode and domain representation without silently rewriting the user’s intent.
INPUT AUTHORITYClean separates what can be observed from what should be concluded. That boundary is the foundation of every single-address result, bulk decision, API response and receipt.
Each stage has a narrow job. Clean does not collapse every signal into one unexplained score.
Interpret syntax, Unicode and domain representation without silently rewriting the user’s intent.
INPUT AUTHORITYObserve domain routing, including MX, null MX and implicit MX conditions where applicable.
ROUTING EVIDENCESurface role, disposable and typo risk as evidence—not as an automatic moral judgment about the address.
RISK EVIDENCEAuthenticated workflows may add bounded mailbox-level SMTP evidence without sending a message.
PROVIDER EVIDENCEConvert the available evidence into safe, review, suppress or unresolved under a declared policy.
DECISION AUTHORITYPreserve the evidence, policy output, confidence and immutable receipt so the decision remains inspectable later.
PROVENANCEEvidence about an address and its routing environment.
A technically usable address does not establish permission to contact a person.
Provider acceptance and inbox placement depend on systems beyond email verification.
Temporary or incomplete evidence can remain unresolved instead of being mislabeled invalid.
Evidence supports use under the selected policy.
Usable evidence exists, but risk or ambiguity deserves human or workflow review.
Evidence supports excluding the address under the selected policy.
Clean does not have enough trustworthy evidence to force a stronger conclusion.
Open the buyer guide for the questions worth asking any verification platform.