Email Verifier — Bulk Syntax, MX & Disposable Check

Clean your email list before you send. Verify addresses in bulk — syntax, mail-server (MX) deliverability, disposable/throwaway domains and role inboxes — without ever sending an email. No account, no API key.

What it does

Give it a list of emails and get one clear row back per address:

• Syntax check — catches typos and malformed addresses.
• MX / domain check — confirms the domain actually has a mail server that can receive mail.
• Disposable detection — flags temporary/throwaway domains (mailinator, 10minutemail, yopmail, …).
• Role-address detection — flags info@, admin@, support@, sales@, noreply@ and other shared, non-personal inboxes.
• Best-effort mailbox probe — an optional deliverability signal (see FAQ).
• valid verdict + reason — every row explains itself, so you can set your own cut-off.

Use cases

• Verify before you email — strip bounces and throwaway addresses out of a cold-outreach list to protect sender reputation.
• Clean before CRM import — validate contacts before they hit HubSpot, Salesforce or your database.
• Signup hygiene — flag disposable emails at registration.
• Automate it in n8n / Make / Zapier — drop verification into a workflow: scrape or collect leads, verify the list, then only email or import the good ones.

Input

{
  "emails": ["hello@apify.com", "info@gmail.com", "sales@mailinator.com", "bad@@nope"],
  "smtpCheck": false,
  "concurrency": 10
}

Field	Type	Description
emails	array	Addresses to verify (one per line). No mail is sent.
smtpCheck	boolean	Attempt a best-effort SMTP deliverability probe (off by default — see FAQ).
concurrency	integer	How many addresses to verify in parallel (1–30).

Output

One record per email:

{
  "email": "info@gmail.com",
  "valid": true,
  "syntaxOk": true,
  "domain": "gmail.com",
  "mxFound": true,
  "mxHost": "gmail-smtp-in.l.google.com",
  "disposable": false,
  "role": true,
  "smtpChecked": false,
  "deliverable": null,
  "reason": "Domain can receive mail; role address (shared inbox, not a person).",
  "ok": true
}

Output schema

Field	Type	Description
email	string	The address you submitted.
valid	boolean	Overall verdict: good syntax, a real mail server, and not a disposable domain.
syntaxOk	boolean	Whether the address is well-formed.
domain	string	Domain part of the address.
mxFound	boolean	Whether the domain has a mail server (MX / A record).
mxHost	string	Primary mail host, when found.
disposable	boolean	Whether the domain is a known throwaway/temporary provider.
role	boolean	Whether it's a shared role inbox (info@, support@, …) rather than a person.
smtpChecked	boolean	Whether the best-effort mailbox probe actually ran.
deliverable	boolean	Best-effort mailbox result (null when not checked or inconclusive).
reason	string	Human-readable explanation of the verdict.
ok	boolean	Whether this address was processed without error.

FAQ

Do you send any email? No. Verification is done from address format and public DNS records — nothing lands in anyone's inbox.

What is the SMTP probe? An optional, best-effort deliverability signal. Most cloud networks block the outbound port it needs, so it often can't run — when that happens smtpChecked stays false and you still get the full syntax / MX / disposable / role verdict, which already removes the large majority of bad addresses.

Can I automate it? Yes — via integrations on the Apify platform (n8n, Make, Zapier, and more) and the Apify API. Verify a freshly scraped list before you email it or push it into your CRM.

Notes

Original clean-room implementation.