Email Finder — Name + Domain → Verified Professional Email

Turn "first name + last name + company domain" into the most-likely professional email address, pattern-ranked and MX-verified with a 0–100 confidence score. Built for sales teams, recruiters and founders enriching prospect lists. Pricing: $0.01 per email found — you pay only for rows that yield a deliverable best guess. No subscription, no API key.

🎥 Video walkthrough

Email finder: how name + domain becomes an email address

Companies overwhelmingly pick one of about a dozen email formats and apply it to everyone. Given jane, smith, acme.com, this Actor:

1. Generates every standard pattern — jane.smith@, jsmith@, jane@, janesmith@, j.smith@ and the rest.
2. Ranks them by real-world prevalence — first.last is roughly 1 in 3 companies; weights are baked into the ranking.
3. Runs one DNS MX lookup on the domain — proving the company can receive mail at all, and identifying who runs the mailbox (Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast…).
4. Returns bestEmail + a 0–100 confidence score plus the full ranked list of alternatives.

That's the same core job Hunter.io and Snov.io sell — done keyless and pay-per-result.

Pattern reference

Pattern	Example	Prevalence
first.last	jane.smith@acme.com	most common (~1 in 3)
first	jane@acme.com	very common at startups
flast	jsmith@acme.com	classic corporate
firstlast	janesmith@acme.com	common
first_last, firstl, f.last	jane_smith@, janes@, j.smith@	occasional
lastfirst, last.first, last, first-last, lastf	—	rarer

Already know a company's convention? Pass "knownPattern": "flast" on those rows and every teammate at that domain gets the same consistent format plus a confidence boost.

Try it: real input and output

Input (this is the exact prefill you'll see in the console):

{
  "people": [
    { "firstName": "John", "lastName": "Doe", "domain": "stripe.com" },
    { "firstName": "Jane", "lastName": "Smith", "domain": "notion.so" }
  ],
  "maxConcurrency": 5
}

Output — one record per person:

{
  "firstName": "john",
  "lastName": "doe",
  "domain": "stripe.com",
  "bestEmail": "john.doe@stripe.com",
  "confidence": 80,
  "pattern": "first.last",
  "hasMx": true,
  "mxProvider": "Google Workspace",
  "isDisposable": false,
  "isFreeProvider": false,
  "isCatchAllRisk": true,
  "allCandidates": [
    { "email": "john.doe@stripe.com", "pattern": "first.last", "weight": 34 },
    { "email": "john@stripe.com", "pattern": "first", "weight": 14 },
    { "email": "jdoe@stripe.com", "pattern": "flast", "weight": 13 }
  ],
  "reason": "ok"
}

Export as JSON, CSV or Excel, or read it back over the Apify API.

Input reference

Field	Type	Notes
people	array (required)	One object per person.
people[].firstName / lastName	string	Or use fullName — split automatically.
people[].domain	string	Company domain; scheme, www. and paths are stripped.
people[].knownPattern	string	Optional: force a known convention (first.last, flast, …).
maxConcurrency	integer	Parallel lookups, 1–25 (default 5).

Accents are stripped and names lowercased ("José-Luis Pérez" → joseluis / perez).

Reading the confidence score

• 80–100 — standard pattern on a healthy business mailbox with live MX. Act on it.
• 50–79 — plausible best guess; verify before a high-stakes send.
• Below 50 — thin name data, unusual domain, or no MX. No MX hard-caps the score: an undeliverable domain can't earn a high number, no matter how common the pattern.

Honest scope: MX-verified, not SMTP-confirmed

This finder proves the domain receives mail; it does not open an SMTP connection to confirm one specific mailbox. Port 25 is blocked from cloud IPs (false negatives) and catch-all domains accept everything (false positives) — so tools claiming cloud SMTP mailbox pings are overselling. Residual catch-all risk is surfaced honestly as isCatchAllRisk: true.

The clean workflow: find here → pipe bestEmail into the Email Verifier for the full deliverability read → send.

Hunter.io alternative without a subscription

Hunter.io's email finder is excellent but sells the job behind monthly seat pricing and credit tiers, keyed to an account. This Actor does pattern generation + MX verification keyless: no third-party account, no monthly minimum, $0.01 per found email on Apify's usage-based billing, and you own the output dataset. If you need Hunter's crawled-source citations, use Hunter; if you need the name→email job at list scale for cents, run this.

Who uses this

• SDRs / sales teams — turn a target-account roster into reachable inboxes.
• Recruiters — contact candidates and hiring managers from name + employer.
• Founders doing PR or partnerships — a "who to contact" shortlist becomes emails.
• CRM ops — fill the missing email column where person + employer are known.

FAQ

Can it find an email address from just a name and company? Yes — that is exactly the input: firstName + lastName (or fullName) + company domain. You get the most-likely address plus every ranked alternative.

Does it guarantee the email is real? No honest tool can without sending. It returns the most probable address and proves the domain can receive mail (live MX). For per-mailbox risk, verify with the Email Verifier and a low-stakes first send.

Why not SMTP-check each mailbox? Port 25 is blocked/greylisted from cloud IPs, and catch-all domains accept every address — an SMTP "yes" proves nothing. MX + pattern ranking is the reliable signal from the cloud.

Does it work for Gmail/Yahoo addresses? No — free consumer domains have no company convention to predict, so those rows return no guess (flagged isFreeProvider). This is a tool for business domains.

What am I charged for exactly? $0.01 per person that yields a deliverable best-guess email (real address on a domain with MX). Rows with no MX or bad input are free. ACTOR_MAX_TOTAL_CHARGE_USD caps are respected.

How is this different from an email scraper? A scraper (like the Website Contact Finder) extracts addresses already published on a site. This finder predicts a specific person's address when it isn't published anywhere — the two chain together well.

Can I run it from the API on a schedule? Yes — POST a people array via the Apify API/SDK, or schedule it in the console to enrich new CRM contacts nightly; pipe results to Sheets, Airtable, Zapier or Make.

How fast is it? Lookups run in parallel (up to 25 concurrent). A few hundred people complete in a couple of minutes.