Bulk Email Verifier

Clean and validate a list of email addresses in bulk. For every address you get one structured record: is the syntax valid, does the domain actually accept mail (MX/DNS), is it a disposable or free-provider address, is it a role account (info@, support@…), and — if the address has an obvious typo — a suggested correction (john@gmial.com → did you mean gmail.com).

Built for lead-list hygiene: drop the junk before you import into your CRM or send a campaign, so you protect your sender reputation and stop paying to email dead addresses.

What you get per email

Field	Meaning
email	The normalised address (trimmed, lower-cased domain).
result	Overall verdict: valid, invalid, risky, or unknown.
reason	Short machine-readable reason behind the verdict.
isValid	true when syntax is correct and the domain has mail records.
syntaxValid	Address passes RFC-style syntax checks.
domain	The domain part of the address.
mxFound	The domain publishes MX (or fallback A) records — it can receive mail.
mxRecord	The primary mail host found for the domain.
isFreeProvider	Address is on a free webmail provider (gmail, yahoo, outlook…).
isDisposable	Address is on a throwaway / temporary-mail provider.
isRoleAccount	Local part is a role address (info, admin, support, sales…).
didYouMean	Suggested domain correction when a likely typo is detected.
smtpCheck	Optional best-effort mailbox check: deliverable, undeliverable, unknown, or skipped (when not requested).

Input

{
  "emails": [
    "ceo@stripe.com",
    "info@gmail.com",
    "john@gmial.com",
    "user@mailinator.com"
  ],
  "checkSmtp": false,
  "timeout": 8,
  "maxItems": 0
}

• emails (required) — the addresses to verify. Duplicates are removed automatically, so you are never charged twice for the same address.
• checkSmtp (default false) — also attempt a live SMTP mailbox probe. This is best-effort only: many mail hosts and networks block this kind of check, in which case the address keeps its syntax/MX/heuristic verdict and smtpCheck is unknown. Slower.
• timeout (default 8) — seconds to wait for DNS (and SMTP, if enabled) per email.
• maxItems (default 0) — cap on emails verified in one run; 0 means no cap.

Pricing

Pay per verified email. Deduplication means repeated addresses in your list are charged once. Syntax and heuristic checks are instant; MX/DNS lookups add a fraction of a second per unique domain.

Notes

• The verifier does not send any email and does not require a proxy — it only reads public DNS records (and, when enabled, performs a standard SMTP handshake without delivering a message).
• A risky result flags addresses that are technically deliverable but lower quality (role accounts, disposable domains) so you can decide whether to keep them.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.