Bulk Email Verifier & Validator
Pricing
from $2.70 / 1,000 results
Clean an email list before you send: syntax, MX records, disposable and role mailboxes, typo repair and an SMTP mailbox probe with catch-all detection. Every address gets deliverable, undeliverable, risky or unknown - never a guess dressed up as a verdict.
One address per line. Display-name forms ('Jane Doe jane@acme.com') are accepted, duplicates are removed before anything is checked.
For pasting straight out of a spreadsheet or CRM export. Separate addresses by newline, comma or semicolon. Merged with the list above.
Ask the mail server whether the mailbox exists (RCPT TO, never DATA - no mail is sent). Needs outbound port 25, which many networks block; the run tests this once and reports the answer in the summary record instead of failing.
After an address is accepted, ask the same server about a random address on that domain. If it accepts that too, the domain takes everything and the acceptance proved nothing - reported as risky rather than deliverable.
info@, sales@, support@ and the like are real mailboxes but carry higher complaint rates on cold sends. Turn this off to score them purely on deliverability.
Keep the full MX list with preferences on each record. Turn off for a slimmer dataset; mxHost is always present.
Output nothing but confirmed deliverable addresses. The run summary still counts everything, so you keep the real rates.
Keep only the statuses you select. Leave empty to return everything.
[]How many addresses to work on at once. SMTP conversations are serialised per domain regardless, so a list of many different domains goes fast while one big domain stays polite.
Per MX lookup. Results are cached per domain for the run.
Per SMTP step. Raise it for slow or greylisting servers; a timeout is reported as unknown, never as undeliverable.
The hostname announced in EHLO/HELO. Using a domain you actually control, with matching forward and reverse DNS, measurably reduces how often servers stonewall the probe.
The envelope sender used during the probe. No mail is ever sent to or from it; some servers simply refuse to answer an empty sender.
Append one RUN_SUMMARY record with the status breakdown, deliverable rate, duplicates removed and whether port 25 was reachable from this run.
Also write the results to the key-value store in these formats. The dataset is always produced regardless.
[]Outbound port 25 is blocked on the Apify platform, so mailbox-level checks only work if a proxy allows a CONNECT tunnel to port 25. Enable this to try; the run reports which route it used and falls back to MX-only when the tunnel is refused. DNS is never proxied.
{ "useApifyProxy": false}