Email Permutation Generator

Enter a name (and a domain, optionally) and get the address patterns companies actually use — with the top guesses verifiable on the spot.

How it works

There is no public directory of email addresses. When you know someone's name and employer, the practical route is pattern matching: companies standardize on one or two address formats, so generating every plausible pattern and checking which one is real is how most prospecting tools work under the hood.

One format dominates corporate email by a wide margin: first.last@ — think jane.doe@acme.com. Tech companies lean toward it even more than the average. Initials-based formats (f.last@, fi.last@) come next, with underscore and hyphen variants trailing. That is why the generator marks first.last@ as the most common — if you can only verify one guess, start there.

The hard line this tool keeps drawing: a generated pattern is a hypothesis, not an address. Every unverified guess you email is a potential bounce, and bounces are the fastest way to burn a sending domain. Tick 'verify the top 5' to check the likeliest candidates against live DNS, or let Reachfold find and verify the address as part of lead sourcing.

The math

Pattern list
first@ · first.last@ · firstlast@ · first_last@ · first-last@ · f.last@ · fi.last@ · firstl@ · first.l@ · last@ · last.first@ · lfirst@Generated from your input, deduplicated, in rough order of how common each format is in the wild.
Most common
first.last@domainThe dominant corporate format — verify this one first.

Benchmarks

Most common formatfirst.last@The default at most modern companies, especially in tech.
Unverified guessesdon't sendEvery wrong guess is a bounce; even a few percent of hard bounces damages domain reputation.
Verify before send100% of cold addressesVerification (DNS or better) should gate every first touch.

Common mistakes

  • Emailing unverified guesses. The top pattern is often right, but 'often' means every miss lands in your bounce rate — verify first, always.
  • Trying one pattern per prospect and giving up. Formats vary within the same company by department and tenure; check several patterns before concluding the person has no address there.
  • Ignoring role and disposable flags after verification. An address can resolve cleanly and still be a shared info@ inbox or a temp-mail alias — neither is worth a send slot.

FAQ

Are the generated addresses safe to email as-is?

No — treat every output as a candidate until verified. The 'verify the top 5' checkbox runs live DNS checks on the likeliest patterns, but for list-scale prospecting you want verification (including catch-all handling) built into the pipeline, which is what Reachfold does before a lead ever enters a campaign.

Why is first.last@ so dominant?

It is unambiguous at scale (two Jane Smiths can coexist as jane.s@ and jane.s1@ conventions aside) and it is what Google Workspace and Microsoft 365 default to, so companies formed in the last two decades overwhelmingly standardized on it.

How does the verification here differ from the Email Verifier tool?

It is the same check — DNS-stage syntax, domain, MX, disposable and role flags — just run against generated candidates instead of an address you already have, capped at the top 5 to respect rate limits.

What if none of the patterns verify?

Either the person has no address at that domain (contractor, different legal entity, left the company) or the company uses a non-standard format. Rather than emailing increasingly exotic guesses, find the address through a source that verifies — or reach out on LinkedIn instead.

Keep reading: How to find anyone's email address · Building a lead list that converts

Share this tool

Stop guessing addresses — let the agent find the verified one

Reachfold is AI-native, deliverability-first outbound: multi-channel sequences across email and LinkedIn, an agent that asks before it acts, and a measured inbox rate gating every campaign.