Email Finder by Name & Domain - Verified Work Emails

What does Email Finder by Name & Domain do?

Email Finder by Name & Domain takes a list of people — first name, last name and the company's domain — and returns each person's work email: the address the company publishes on its own website, or the one the company's mail server confirms exists. An address is never guessed: when the mail server accepts every address, or does not answer, the row says so, shows the likeliest address as unverified, and costs nothing.

Give it a CSV, a JSON list or the dataset of another Actor — a LinkedIn, Google Maps or decision-maker scrape — and get back a verified email per person, with where it came from.

You pay only per email found. It runs on the Apify platform: API access, scheduling, integrations (Make, Zapier, n8n, Google Sheets) and run monitoring included.

Why use it?

• Verified or free. An email in the email column is either printed on the company's website (published) or exists according to the company's own mail server (confirmed). Nothing else goes into that column, and nothing else is charged.
• The company's own pattern first. Each company's website is read before its mail server is asked. An address it prints costs no check, and the pattern its other addresses follow — j.doe@, doe@, jane.doe@ — makes the first question the right one in 30 of 32 cases in our test. Finders that try only the four American patterns miss every German nachname@ and v.nachname@ company.
• A catch-all server fools nobody. One company in six accepts every address. Each domain is first asked for a mailbox that cannot exist, and only a server that refuses it is believed. Tools that skip this sold the wrong first.last@ as "found" for 14 of 15 such people in our test.
• German names the German way. Müller is mueller@ in a German mailbox, not muller@. On October 4, 2026 we asked German mail servers about 18 people with an umlaut in their name, in both spellings: 6 had a mailbox only as ae/oe/ue, none only with the mark dropped. On .de, .at and .ch domains that is the spelling asked for.
• A mailbox two people could own is nobody's. apelt@ of a clinic with two Apelts, daniel@ of a company with two Daniels, is not assigned to either.
• Every row says where the address came from: the page that prints it, or mail server of <domain> — and how many addresses were checked to get it.
• Cheap to run. About 2.5 mail-server checks per person, at $0.00089 each, plus the price per email found.

Use cases

• Lead lists — names and companies from an event, a directory or a scrape, turned into addresses you can write to.
• CRM enrichment — the contacts you already have, with their current work email.
• After a LinkedIn or decision-maker scrape — feed the dataset in; the names come back with emails.
• Email patterns — company_pattern and pattern_source tell you how each company spells its mailboxes, with the evidence.

How to use it

1. Paste your People as JSON objects — {"firstName": "Jane", "lastName": "Doe", "domain": "acme.com"} — or plain lines like Jane Doe, acme.com. Field names from common exports are recognized (first_name, surname, name, website, url …). Or give the dataset ID of another Actor's run.
2. Leave Confirm unpublished emails on to have the mail servers asked, or turn it off to get only the emails the websites publish.
3. Leave Read the company websites first on: it is where the published addresses and the company's pattern come from.
4. Click Start. Download the results as JSON, CSV, Excel or HTML.

Input

Field	What it does
People to find emails for	One object per person: a first name, a last name and the company's domain or website. Also accepted: a name with the whole name, surname, website/url instead of domain, plain strings "Jane Doe, acme.com". Titles before a name (Dr., Herr) and letters after it (MD, CPA) are dropped.
Or a dataset of people	The ID of an Apify dataset whose items carry a name and a company domain — read after the people listed above.
Confirm unpublished emails	Ask the company's mail server which of a person's usual mailboxes exists (default on). Runs bounceverify's email verifier in a separate run on your account, which bills $0.00089 per address checked.
Read the company websites first	Read each company's website for published addresses and its email pattern before asking its mail server (default on).
Max contact and about subpages	How many contact-like pages to read per website (default 5). Up to 4 team pages and 8 pages of single people are read on top.
Proxy configuration, Retry refused sites	As in our other Actors: websites that refuse a cloud address are retried through Apify Proxy.

Output

One row per person. The values below are invented:

{
  "first_name": "Jane",
  "last_name": "Doe",
  "name": "Jane Doe",
  "domain": "acme.com",
  "email": "j.doe@acme.com",
  "email_status": "confirmed",
  "email_source": "mail server of acme.com",
  "likely_email": null,
  "company_pattern": "f.last",
  "pattern_source": "r.roe@acme.com",
  "checks": 1,
  "website": "https://www.acme.com/",
  "website_status": "ok",
  "company": "Acme GmbH",
  "company_email": "info@acme.com",
  "company_phones": ["+493012345678"],
  "note": "The company's mail server confirmed this mailbox exists.",
  "billed": true
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Field	Meaning
first_name, last_name, name, domain	The person as given, the name without titles and letters, the company's registered domain.
email	The person's work email: published or confirmed. null otherwise.
email_status	published — printed on the company's website. confirmed — the company's mail server says the mailbox exists. catch_all — the server accepts every address, so none can be confirmed. unanswered — the server did not answer, twice. not_found — none of the usual mailboxes of this name exists. not_checked — confirmation is off. no_mail — the domain accepts no mail. invalid — the row had no name or no company domain.
email_source	The page that prints the email, the website when it was found elsewhere on the site, or mail server of <domain>.
likely_email	For a person without an email: the address the company's pattern — else the commonest one — would give them. Unverified; a catch-all server may or may not deliver it.
company_pattern, pattern_source	How the company spells its people's mailboxes (first, first.last, last, f.last, flast, firstlast …), and one published address as the evidence.
checks	How many addresses the mail server was asked about for this person.
website, website_status	The company website as read, and whether it answered.
company, company_email, company_phones	The company's name from its legal notice, its general inbox and phone numbers — in every row, free.
note	One sentence on what the status means.
billed	Whether this row was charged.

Accuracy

On October 2, 2026 we took 64 people at 35 companies — local businesses in Ireland, the UK and Australia, US startups, German firms — whose work address was known: 41 printed on the company's own website, 23 confirmed by the company's mail server a week earlier. Then we asked for each of them by name and domain only, with the website reading turned off, and ran the two most used email finders on Apify Store on the same 64 people.

64 people, name and domain only	this Actor	the pattern-and-SMTP finder with 299 users	the $0.001 finder with 169 users
Right address returned	45	26	0 — no result in 33 minutes (its CAPTCHA solver failed)
… of the 41 printed on the websites	22	10	—
Wrong address sold as found	0	14 — first.last@ guessed on catch-all domains	—
Catch-all domain, said so, free	15	0	—
Not found	1	21	—
Mail-server checks	161 for $0.14	$0.81	—
Cost per right address	$0.003 + the price per email	$0.031	—

Where the difference comes from: German companies spell their mailboxes nachname@ and v.nachname@; the other finder tries the four common American patterns and found none of them. And on the six catch-all domains it returned a first guess as "found" for all 15 people — 14 of them not the address the company prints.

With the websites read first, as the Actor runs by default, the 41 printed addresses are found without a single check, and the company's pattern makes the first question right in 30 of 32 cases: about one to two checks per person.

How much does it cost?

• Verified work email — $0.005 ($5 per 1,000), charged for each person with a published or confirmed email. Once per address in a run.
• Free: a person whose address was not found, whose company's mail server accepts every address or did not answer, an invalid row, the likeliest address beside each of them, the company's pattern, inbox and phones.
• Confirming emails is done by bounceverify's email verifier in a separate run on your account: $0.00089 per address checked. In the test above 161 addresses were checked for $0.14 for 64 people: about 2.5 checks, or $0.002, per person — one to two with the websites read first.

1,000 people, all found, cost about $5 plus $2 of checks plus the platform usage of reading 1,000 websites (about 0.3 compute units).

Tips

• Give the domain the company uses for mail. It is usually its website's; a company that moved to another domain is followed there when the website is read.
• Columns from any export work: firstName/lastName, first_name/last_name, name, surname, domain, website, url.
• One name twice for one domain is asked once.
• A catch_all row means the company's server will accept likely_email whether or not the mailbox exists — write to it at your own risk, or ask the company's inbox in company_email.
• Mail servers are asked in batches of up to 40 companies, after their websites are read: rows appear batch by batch.

FAQ

Where do the emails come from?

From two places only: the company's own website, read at the moment of the run (team pages, legal notice, contact pages, the pages of single people), and the company's own mail server, asked whether a mailbox exists. No database, no LinkedIn.

Why confirmed and not just "valid"?

Because a mail server that accepts every address — one in six — would call any address valid. Each domain is first asked about a mailbox that cannot exist. A server that accepts it is not believed about anything else, and its people come back as catch_all, free, with the likeliest address beside them.

Why does a person have no email?

The company does not print one, and its mail server either accepts every address, did not answer, or knows none of the usual mailboxes for the name — a nickname, a double first name (marietherese@), a middle initial. A busy server is asked once more; one that stays silent may answer on another day.

Can I feed it another Actor's output?

Yes: paste the dataset ID into Or a dataset of people. Items with any of the usual name and domain fields are read; LinkedIn scrapers' fullName and companyWebsite, Google Maps scrapers' website, our decision-maker finder's first_name, last_name and domain all work.

Is this legal?

The Actor reads public company websites, respecting robots.txt, and asks mail servers the question every mail client asks before delivery. A person's name and work email are personal data: under the GDPR you need a legal basis to process them and must inform the people concerned; in Germany §7 UWG requires prior consent for advertising emails in most cases, and other countries have rules of their own (CAN-SPAM, CASL, PECR). You are responsible for how you use the data.

Related Actors

• Decision Maker Email Finder — the people who own or run each company on a list of websites, with their emails; feed its output here for the rest of the names.
• Website Contact & Email Scraper — emails, phone numbers and social profiles from any list of websites, priced per contact.
• Google Maps Email Extractor — local businesses from a Google Maps search, each with the email from its own website.
• Shopify Store Leads & Emails — Shopify stores by product keyword and country, with each store's email.
• No Website Leads — local businesses on Google Maps without a real website.
• Impressum Email Scraper — German company websites: the company, its representatives and contacts from the Impressum.

Disclaimer

This Actor is a tool. You are responsible for complying with the GDPR and local marketing law, the target sites' Terms of Service, and robots.txt. It does not build or sell contact databases.

Support

Got an address that bounced, or a not_found for a person whose mailbox exists? Open an issue on the Issues tab with the name and domain — accuracy reports shape the roadmap directly.