Email permutator

What this permutator does

You type a first name, a last name, and a domain. We generate every common work-email pattern we use in production — the same 13 patterns behind the finder — and show them as candidates. Nothing on this page is a real person. Nothing on this page has been checked against a mail server.

That is intentional. Guessing addresses is cheap and, done in public, it is how personal data ends up in search indexes. Hunter's 2026 position was that contact data should not be a public SEO product. We agree. This tool shows *formats*, not people.

The finder, one click away, is where a candidate becomes a mailbox. Use this page to understand the formats, to pre-fill a pattern, or to see why jdoe@ and jane.doe@ are different bets.

The 13 patterns, with a fictional example

For Jane Doe at company.com:

• {first}.{last} → jane.doe@company.com
• {first} → jane@company.com
• {f}{last} → jdoe@company.com
• {first}{last} → janedoe@company.com
• {f}.{last} → j.doe@company.com
• {first}{l} → janed@company.com
• {last}.{first} → doe.jane@company.com
• {last}{first} → doejane@company.com
• {last} → doe@company.com
• {first}_{last} → jane_doe@company.com
• {f}_{last} → j_doe@company.com
• {first}-{last} → jane-doe@company.com
• {f}-{last} → j-doe@company.com

These are listed with longer notes on work email formats. The highlighted row on a format page is the pattern that page is about.

Jane Doe is not a real person at that domain. If you need a real mailbox, verify one.

Why companies pick a pattern at all

IT has to issue addresses somehow. The cheapest way is a rule: first.last, or first initial plus last name, applied to everyone. Once you know the rule, you can guess the next hire. That is why permutators exist, and it is why they are dangerous as a sending strategy: a consistent pattern is not the same thing as a live mailbox.

Some companies mix patterns after a merger. Some give executives first@ and everyone else first.last@. Some use plus-addressing internally (jane.doe+news@) which you should never put on a cold list. The permutator will not detect any of that. The finder will at least ask the server.

What this page will not do

• It will not tell you which pattern a *specific real company* uses. We do not publish per-company directories.
• It will not check SMTP. Zero mail-server conversations happen here. The page is free and uncapped because of that.
• It will not generate exotic patterns (first.middle.last, numbered duplicates like jane.doe2@). Those exist; they are a rounding error next to the 13 we actually probe.
• It will not "complete" a name from a LinkedIn URL. Type the name.

How to use it in a real workflow

1. Generate the candidates here so you can see what you are about to ask.
2. If you already strongly believe the company uses first.last, open the first.last format page and read why that pattern is common before you bet a whole list on it.
3. Take the name and domain to the finder and let the mail server pick.
4. If the finder returns catch-all, you now know the pattern is probably right and the mailbox is still unconfirmed. Do not "verify" it by sending.

If you are writing Clay formulas or a spreadsheet CONCAT, this page is the spec. Copy the pattern, not a scraped address.

Common mistakes

• Sending all 13 candidates to the same person. That is how you get marked as spam by one human, not how you find a mailbox.
• Using a permutator output as a "verified" column in a CRM. It is a hypothesis.
• Generating candidates for gmail.com. Personal inboxes do not follow company patterns.
• Publishing a page of real employees' permutated addresses. Don't.

Related reading

• Email pattern in the glossary
• Free work email finder
• MX lookup if you are not even sure who hosts mail