Email Verifier, Validator & Finder - Bulk Email Verification

Clean and verify any email list before you send - cold outreach, newsletters, sign-up forms, CRM imports. Paste or upload thousands of addresses and get back a clean, deliverability-scored list in seconds. Or find a person's email from just a name and a company domain.

No login and no API key. The validator combines syntax checks, live domain (MX / SPF / DMARC) checks and an optional live SMTP mailbox check that confirms whether an inbox really exists.

Drop-in replacement for the most popular Apify verifier

Every record includes the same normalized fields as the market-leading email verifier (michael.g/email-verifier-validator), so you can switch actors without changing a single line of your workflow, n8n/Make/Zapier scenario or MCP integration:

Field	Values
status	good / risky / bad - business verdict, safe to send?
technical_status	valid / invalid / unknown / catch_all / disposable / error
score	0-100 deliverability score
reason	ok, invalid_syntax, no_mail_infrastructure, disposable_email, catch_all_domain, smtp_unreachable, request_failed
verification_details	nested object with every individual check result

Our richer legacy fields (deliverabilityScore, verificationStatus, mailboxExists, catchAll, mxProvider, suggestedCorrection...) are all still there - this actor is a strict superset of the leader's schema.

What this email checker does

• Bulk email verification - validate thousands of addresses in one run.
• Real deliverability, not just regex - domain (MX) checks confirm the domain can actually receive mail and reveal the provider (Google Workspace, Microsoft 365, Zoho, Yandex...).
• SPF & DMARC checks - confirms the domain publishes SPF and DMARC records (a strong signal the domain is a well-managed mail sender).
• Live SMTP mailbox check - confirm the specific mailbox exists and detect catch-all domains. Works on cloud platforms.
• Email Finder - guess and verify a person's address from Name + domain.
• Typo rescue - recover misspelled domains (gmial.com -> gmail.com).
• List hygiene - flag disposable, role-based and free-webmail addresses.
• Plus-tag detection - surfaces user+tag@domain.com aliases (emailTag / isTagged).
• Smart de-duplication - Gmail dots and +tags are normalized.
• Deliverability score - a transparent 0-100 score with plain-English reasons.

Pricing

Pay per result - you are billed only for addresses actually returned (via the result charge event). Tiered by your Apify plan, platform usage paid by user:

Plan	Price per verified email
FREE	$0.10 (anti-abuse)
BRONZE	$0.001
SILVER	$0.0008
GOLD and above	$0.0006

From $0.60 per 1,000 verified emails on paid plans. No monthly subscription, no seat fees, no API key. The optional live SMTP mailbox check is opt-in, so you only spend extra time on the lists that need mailbox-level certainty. Use the filters (only-valid / only-deliverable) to return fewer records and pay for just the addresses you keep.

What you get for every email

Field	Meaning
status	business verdict: good, risky or bad (leader-compatible)
technical_status	valid, invalid, unknown, catch_all, disposable, error (leader-compatible)
score	0-100 deliverability score (same value as deliverabilityScore)
reason	snake_case primary failure reason, or ok (leader-compatible)
verification_details	nested per-check detail: syntax, MX, A fallback, SMTP, catch-all, disposable, role, free, tag, SPF, DMARC
verificationStatus	legacy status: valid, risky, invalid or unknown
deliverabilityScore	0-100 confidence score (legacy name of score)
syntaxValid	passes RFC-aware syntax rules
normalizedEmail	de-duplication key (Gmail dots / +tags ignored)
emailTag / isTagged	the +tag part of an aliased address, if present
hasMx / mxProvider	domain can receive mail + detected provider (Google Workspace, Microsoft 365, Zoho...)
hasSpf / hasDmarc	domain publishes SPF / DMARC records (null if DNS lookup failed)
mailboxExists	the inbox really exists (when the live mailbox check is on)
catchAll	domain accepts any address, so a single mailbox can't be confirmed
smtpConnected	whether the live mailbox check reached a mail server
freeProvider	free webmail (Gmail, Outlook, Yahoo...)
roleBased	group mailbox (info@, sales@, support@)
disposable	throwaway / temporary domain (18k+ domains)
suggestedCorrection	typo fix, e.g. john@gmial.con -> john@gmail.com
reasons	plain-English explanation of the score

Why use this email verifier

• Reduce bounce rate and protect sender reputation. Removing invalid and risky addresses before a campaign keeps your bounce rate low and your domain out of spam folders.
• Confirm mailboxes actually exist. The live mailbox check goes beyond syntax and domain checks - it confirms whether the specific inbox is real, and flags catch-all domains that accept everything.
• Typo rescue. Recovers misspelled domains (gmial.com, yaho.com, outlook.con) instead of silently dropping good leads.
• Broad disposable detection. Flags 18,000+ throwaway / temporary domains.
• Smart de-duplication. Provider-aware normalization catches john.doe+news@gmail.com and johndoe@gmail.com as the same inbox.
• Drop-in compatible. The same status / technical_status / score / reason / verification_details schema as the most popular Apify email verifier - zero switching cost.
• No API key, no signup. Nothing to register for.

Email Finder - find an email from a name and domain

Don't have the address yet? Give the finder a name + domain and it builds the common corporate patterns (john.doe@, jdoe@, john@, jsmith@...) and, when the SMTP check is on, verifies which one actually exists - skipping catch-all domains so you don't get false positives.

Input (one person per line):

Elon Musk, tesla.com
Bill Gates @ microsoft.com

Output per person:

{
  "mode": "finder",
  "name": "Elon Musk",
  "domain": "tesla.com",
  "candidates": ["elon.musk@tesla.com", "elonmusk@tesla.com", "emusk@tesla.com", "elon@tesla.com"],
  "mostLikely": "elon.musk@tesla.com",
  "email": "emusk@tesla.com",
  "found": true,
  "verified": true,
  "catchAll": false,
  "reason": "mailbox verified via live SMTP check"
}

When the SMTP check is off or a mail server is unreachable, the finder still returns the ranked candidates and the mostLikely pattern (with verified: null) so the run is always useful.

Reliability

The live mailbox check works on cloud platforms. Some mail servers greylist or rate-limit verification, and catch-all domains accept any address - in those cases the actor returns its best signal from the domain/MX checks rather than a false "valid", and the run never fails. For the highest certainty on large lists, enable a proxy (see Input below).

Input

• Email addresses - one per line, paste a whole CSV column into the free-text field, or upload a CSV/TXT file directly. Name <john@acme.com> pastes are handled too.
• Email Finder - one First Last, domain.com per line to guess + verify a person's address (optional; runs alongside the validator).
• Check domain deliverability - toggle domain (MX / SPF / DMARC) checks on/off.
• Live SMTP mailbox check - confirm the mailbox exists + detect catch-all.
• Proxy - optional. For large lists a proxy improves throughput and reliability of the mailbox check. Use auto for Apify Residential, or paste your own proxy URL.
• Filters - return only valid / only deliverable, drop disposable, drop role-based, de-duplicate.
• Export format - full JSON, CSV-friendly columns, or both.

Output sample

{
  "input": "John.Doe+news@Gmail.com",
  "email": "john.doe+news@gmail.com",
  "status": "good",
  "technical_status": "valid",
  "verificationStatus": "valid",
  "score": 95,
  "deliverabilityScore": 95,
  "reason": "ok",
  "syntaxValid": true,
  "normalizedEmail": "johndoe@gmail.com",
  "emailTag": "news",
  "isTagged": true,
  "domain": "gmail.com",
  "freeProvider": true,
  "roleBased": false,
  "disposable": false,
  "hasMx": true,
  "mxProvider": "Google Workspace",
  "hasSpf": true,
  "hasDmarc": true,
  "mailboxExists": true,
  "catchAll": false,
  "smtpConnected": true,
  "verification_details": {
    "syntax_valid": true,
    "mx_records_valid": true,
    "a_fallback": false,
    "mx_records": ["gmail-smtp-in.l.google.com"],
    "smtp_checked": true,
    "smtp_connected": true,
    "mailbox_exists": true,
    "catch_all": false,
    "disposable": false,
    "role_based": false,
    "free_provider": true,
    "has_tag": true,
    "tag": "news",
    "spf": true,
    "dmarc": true
  },
  "reasons": ["domain has MX records", "SMTP confirmed the mailbox exists"]
}

API, MCP and no-code usage

Run the actor programmatically with any HTTP client - no SDK needed:

# Start a run (returns a run id; poll it until SUCCEEDED)
curl -X POST "https://api.apify.com/v2/acts/apivault_labs~email-validator/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["john.doe@gmail.com", "info@acme.com"], "smtpVerification": true}'

# Read the results (replace RUN_ID with the id from the previous call)
curl "https://api.apify.com/v2/actor-runs/RUN_ID/dataset/items?token=YOUR_APIFY_TOKEN"

• MCP: add this actor as a tool to any MCP client (Claude, Cursor, ChatGPT, ...) via the Apify MCP server and call it directly from your AI agent.
• n8n / Make / Zapier: use the official Apify integration nodes - start the actor with your email list and map the dataset items (status, score, reason, verification_details) straight into your workflow.
• Schedules & webhooks: run it on a schedule and push clean lists to Google Sheets, your CRM or a webhook endpoint automatically.

Common use cases

• Clean a lead list before a cold email campaign - drop invalid and risky addresses to keep your bounce rate low.
• Scrub a purchased or scraped list before importing to a CRM.
• Validate sign-up form input in bulk to stop fake and disposable signups.
• Find a decision-maker's email from their name and company domain.
• Protect sender reputation by removing spam-trap-prone role and catch-all addresses before you send.

FAQ

Does this actually check if an email address exists? Yes. With the live SMTP mailbox check enabled, the actor confirms whether the specific inbox exists. Catch-all domains are flagged separately because they accept any address and can't be confirmed individually.

Do I need an API key or account? No. There's no signup and no API key - only a standard Apify run.

How accurate is the mailbox check? Very accurate for most domains. Some large providers greylist or rate-limit verification, and catch-all domains accept everything - in those cases the actor returns its best signal instead of a false "valid", so you never get misleading results.

Why do some addresses come back as risky or unknown? Some mail servers greylist verification attempts, and catch-all domains accept everything. In those cases the actor returns its best signal instead of a false "good".

Can it find someone's email from just their name? Yes - use the Email Finder. Provide Name, domain.com and it generates the common corporate patterns and verifies which one exists.

How do I get a clean, deliverable-only list? Turn on the Return only deliverable filter (and optionally Drop disposable / Drop role-based) to export just the addresses safe to send to.

How much does it cost? From $0.60 per 1,000 verified emails on paid plans ($0.10 on the Free plan to deter abuse). You pay only for addresses returned, with no monthly subscription and no API key.

What formats can I export? Full JSON, CSV-friendly flat columns, or both. Dataset views include a ready-made "Deliverable (clean list)" table.