Before a CRM import
Separate suspect rows for review and keep the remaining source data intact.
Separate likely-valid, risky and invalid addresses before you send. Up to 100 unique emails per run.
| Status | Score | Disposable | Role |
|---|
The list cleaner checks address syntax, domain existence, MX records, disposable-domain risk and common role inboxes. It intentionally does not run SMTP mailbox probing in bulk, which keeps the tool fast and avoids presenting uncertain mailbox behavior as a hard fact.
For one address where mailbox-level signals matter, use the deliverability checker.
The cleaner combines repeated-input removal with the free bulk checks. It reports results for review rather than silently discarding every address with a warning.

Use new lines, commas or semicolons. Keep a separate copy of your source list.
Distinguish invalid, risky, unknown and likely_valid before deciding what to keep.
The CSV includes statuses so you can apply a documented rule in your spreadsheet or CRM.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
A functional address can be the correct destination for a business contact.
Next action Review the reason, not only the label.
The checker could not collect enough evidence at that moment.
Next action Retry later or ask for confirmation.
A format or destination problem was detected.
Next action Check the original record before suppressing it.
Separate suspect rows for review and keep the remaining source data intact.
Review typos among contacts who supplied their addresses. Verification does not replace permission to send.
No. You must preserve and apply your own unsubscribe and suppression records.
Yes. This export reports checked rows with their status and score so you can decide what to include.
No. The public cleaner uses the free bulk checks without per-row SMTP probing.