Email Pattern Finder — the likely work address, labelled as likely

Give it a name and a company domain, get the addresses that person probably has. Ranked by how common each naming convention actually is, with a real DNS check on whether the company accepts mail at all.

Quick start: press Start with no configuration. It ships with ten sample contacts so one run shows you the whole output shape — including a dead domain and a free mailbox provider, so you can see how it handles both. Then paste in your own list.

Sample output

fullName	domain	bestCandidate	candidateCount	domainAcceptsMail	mxHost
Jane Doe	stripe.com	jane.doe@stripe.com	5	true	aspmx.l.google.com
Wei Chen	cloudflare.com	wei.chen@cloudflare.com	5	true	mailstream-central.mxrecord.io
Ana Silva	nosuchdomain-xyz-98765.com	—	0	false	—

Every row also carries firstName, lastName, domainStatus, domainReason, isDisposable, isFreeProvider, mailboxChecked, confirmedAddress, note, and a candidates array where each entry has the email, the pattern that produced it (first.last, flast, …) and that pattern's real-world frequency.

Why this one

A candidate is not a find, and this Actor never pretends otherwise. Most tools in this market return one address and call it "found". Without a mailbox-level check that is a guess wearing a fact's clothing, and the buyer learns which it was when the message bounces. Here confirmedAddress stays null until a mail server has actually accepted the address, and note says in plain English what the row does and does not prove.

The ranking is published, not hidden. Each candidate names its pattern and how common that pattern is, so you can disagree with the order instead of inheriting it. If you know the company uses flast, you can see which candidate that is.

The domain check is real. One DNS lookup per company establishes whether the domain exists, whether it publishes MX records, and whether it is a disposable or free-mail provider. A company that cannot receive mail returns zero candidates and says why, rather than eleven addresses that will all bounce.

A free mailbox provider is answered honestly. gmail.com has no company convention to infer — addresses there are whatever the person chose at signup. The row says so instead of quietly generating patterns that carry no signal.

Names are handled the way mail servers handle them. Accents are folded (José → jose), punctuation is stripped (O'Brien → obrien), middle names are dropped rather than guessed at, and a single-word name yields only the patterns that do not need a surname.

What you can do with it

• Reach a named prospect you found on LinkedIn, a conference page or a press release, where you have the person and the company but no address.
• Fill gaps in a CRM export — the contacts whose email field is empty.
• Enrich a list before a campaign, then pass the candidates through a verifier to rank them.
• Feed an AI agent. Rows are about 1 KB, identically shaped, and every claim is scoped to what was actually checked.

Input

Field	Default	Notes
contacts	10 samples	First Last, company.com. A comma, an @, a pipe or plain whitespace all work as the separator, and a full URL is accepted instead of the domain.
checkMailbox	false	Ask the company mail server which candidate is real. See the limit below.
maxCandidates	5	Five covers roughly four in five real conventions.
onlyDeliverableDomains	false	Drops companies that cannot receive mail. You are charged per row returned, so this is the cheaper way through a long list.
concurrency	10	Parallel lookups. DNS resolvers start refusing above about thirty.

The limit worth knowing before you buy

Outbound port 25 is blocked on most cloud platforms, including this one. That means the SMTP mailbox check usually cannot run, and when it cannot, the row says so — mailboxChecked stays false and the run summary carries mailboxCheckBlockedReason. It never upgrades a guess to a find because the check was unavailable. Leave checkMailbox off unless you know your account can open port 25.

What this Actor proves without it is still substantial: that the company exists, that it accepts mail, which server handles it, and which addresses are worth trying in which order.

Pricing

Pay per person returned. People removed by your filters are not charged, and duplicates are dropped before anything is counted.

Disclaimer

This Actor generates addresses from naming conventions and checks public DNS records. It scrapes no website and calls no third-party API — there is no database of people behind it and none is consulted.

It returns candidates about a named person at a named company, supplied by you. Sending unsolicited mail is regulated in most jurisdictions — GDPR in the EU, CAN-SPAM in the US, PDPA in Thailand among them — and complying with the rules that apply to you is your responsibility, not this Actor's.