Email Verifier

Check a list of email addresses by syntax and by actually resolving the domain's mail servers (MX records) — with an honest, tiered verdict instead of a single misleading "valid/invalid". No live mailbox probe pretending to confirm delivery.

What you get

• Syntax check, domain resolution and MX lookup for every address — a real DNS answer, not a guess.
• A tiered verdict (valid_syntax_and_mx, invalid_syntax, domain_not_found, no_mx, unknown) instead of a flat true/false that hides WHY an address failed.
• Mail provider detection (Google Workspace, Microsoft 365, Yahoo, Yandex, Zoho, ProtonMail, Amazon SES, Fastmail, iCloud and more) from the MX records themselves.
• Disposable-domain and role-account (info@, admin@, support@...) flags — useful signals for cleaning a list before outreach.
• A known "catch-all" warning where the mail PROVIDER itself is documented to accept any address regardless of whether the mailbox exists (currently: Yahoo) — a static fact, not a live probe.
• Runs on Apify: schedule it, monitor it, call it from the API, export to JSON/CSV/Excel or push straight into your own pipeline.

How to run it

1. Click Try for free — no card needed on the free plan.
2. Paste your list of email addresses into Emails.
3. Hit Start and pull the results from the dataset (UI, API or webhook).

Pricing

Pay-per-event: $0.005 per run start + $0.001 per email verified. Every verdict — including a confirmed "this address is invalid" — is a real, delivered answer and is billed the same way; only a genuine DNS infrastructure hiccup (not a verdict on the address) is returned for free. 1,000 emails = $1.00 + the one-time start fee.

Input

Field	Required	What it does
emails	yes	Email addresses to verify. Max 100 per run.
maxConcurrency	no	How many emails to check in parallel (default 10).

{
    "emails": ["test@gmail.com", "not-a-real-email", "someone@this-domain-zzq123.example"]
}

Output

{
    "email": "test@gmail.com",
    "syntaxValid": true,
    "domainResolves": true,
    "mxFound": true,
    "mxRecords": [
        "gmail-smtp-in.l.google.com",
        "alt1.gmail-smtp-in.l.google.com",
        "alt2.gmail-smtp-in.l.google.com"
    ],
    "provider": "Google Workspace",
    "disposable": false,
    "roleAccount": false,
    "catchAllRisk": false,
    "verdict": "valid_syntax_and_mx",
    "mailboxChecked": false,
    "checkedAt": "2026-07-30T07:51:36.835Z"
}

Field	Meaning
verdict	valid_syntax_and_mx (domain can receive mail), invalid_syntax, domain_not_found (confirmed non-existent domain), no_mx (domain exists but cannot receive mail — including RFC 7505 "null MX" domains that explicitly opt out), or unknown (DNS infrastructure hiccup — not a verdict on the address).
mxRecords	Mail server hostnames, sorted by priority.
provider	Mail provider detected from the MX records, or null when none was found or matched.
disposable	Domain matches a static list of known temp-mail providers. Not exhaustive.
roleAccount	Local part looks like a shared inbox (info@, support@, ...) rather than a person.
catchAllRisk	true only when the detected PROVIDER is documented to accept mail for any address on its servers regardless of mailbox existence — a static, known-behavior flag, not a per-domain live test.
mailboxChecked	Always false. See FAQ.
error	null for every real verdict, including "invalid" ones; only set when a DNS infrastructure error prevented a verdict at all.

Related tools

Related tools for adjacent workflows in B2B lead generation and data enrichment.

Actor	What it does
Company Profile Lookup	Pair it in the B2B lead generation and data enrichment workflow: Turn a domain or company name into one unified company card: website tech stack (CMS, ecommerce, key tech)...
URL to Markdown Converter	Pair it in the B2B lead generation and data enrichment workflow: Fetch any URL and convert it into clean, LLM-ready Markdown — headings, links, lists and emphasis...
Company Registry Enricher	Pair it in the B2B lead generation and data enrichment workflow: Turn a company name, LEI or UK company number into an official registry card: legal name, status,...
Counterparty Risk Rollup — Sanctions, Courts, Registry, Hiring	Pair it in the B2B lead generation and data enrichment workflow: One call, one row per counterparty: sanctions screening (OFAC + EU), legal-entity registry (GLEIF),...
Intent Signal Aggregator	Pair it in the B2B lead generation and data enrichment workflow: Is this company in-market right now? Combines public hiring activity (Greenhouse, Lever, Ashby) and recent...

FAQ / Limitations

Does a valid_syntax_and_mx verdict mean the mailbox exists? No — it means the DOMAIN is correctly configured to receive mail. Confirming one specific mailbox exists requires an SMTP conversation with the mail server, which this Actor does not perform (mailboxChecked is always false). Cloud platforms — this one included — commonly cannot open outbound port 25 at all, which is why a live per-mailbox check is not offered as a false promise here.

What this is NOT. Not a deliverability guarantee, not a spam-score check, and not proof a specific person still reads that inbox. catchAllRisk flags a PROVIDER-level known behavior (some mail providers accept any address on their servers), not a per-domain catch-all test — that would require the same live SMTP conversation this Actor deliberately does not perform.

Found an address this Actor should classify differently, or need a bulk mailbox-check add-on for your case? Open an issue on this Actor's page.