If you are deciding what to send to a paid verifier, a useful first pass is to separate four things: syntax/typo, public DNS/MX, disposable signals, and role addresses. Ambiguous rows stay unknown; this is not SMTP probing, mailbox login, sending, or a deliverability guarantee. It is for buyer-owned lists and is bounded to 500 rows per run. I built the starter kit and maker notes here: https://whop.com/checkout/plan_Q...
Reusable Apify Actor source package for teams that want to classify syntax, MX, disposable, and role-address signals before a separate mailbox verifier. No SMTP probing or mailbox-existence claims. 500-address file: starter-batch example, not a technical or license cap. Default: 20,000 unique addresses; configurable maximum: 50,000. Dependencies: Apify SDK, Actor.charge(), Apify Actor Docker environment. No deliverability or inbox-placement guarantee.
