Free Email Permutator

Find anyone's work email format in seconds

Most professional email addresses follow a predictable pattern built from a person's name and their company domain. The trouble is there are a dozen common patterns (first.last, flast, firstlast, first, and more) and you rarely know which one a company uses.

This free email permutator generates all of them at once. Give it a name and a domain and it returns the complete list of likely addresses, so you can stop guessing one format at a time.

Then verify before you send

A permutated list is a list of possibilities, not confirmed addresses. Sending to guessed emails hurts your bounce rate and your sender reputation. Always verify the candidates first.

An email verifier checks which permutation is deliverable. The free checks on our own verifier pages are not running right now, and neither is the search on our email finder by name. Our free bulk email verifier still dedupes and syntax-checks a pasted list in your browser.

The most common professional email formats (with examples)

Every candidate is built from a handful of pieces: the full first name (john), the full last name (smith), and their initials (j and s). Joining those with a dot, hyphen, underscore or nothing produces the formats companies actually use. For John Smith at company.com the standard patterns are first.last (john.smith@company.com), firstlast (johnsmith@company.com), flast (jsmith@company.com), first (john@company.com), firstl (johns@company.com), and last.first (smith.john@company.com).

In our list of 36 large, well-known companies (formats as publicly reported, not measured by Emailchaser), 29 use first.last; the exceptions: Google, Meta, Stripe and Uber use first@, Nvidia and Cisco flast@, McKinsey first_last@. The full list, with an example address for each company, is on our company email format finder. Single-token formats like john@ turn up mostly at small startups where there is no risk of two people sharing a name, while bigger organisations lean on the full last name to avoid collisions. The order the tool lists candidates is not a ranking of likelihood, treat the six standard formats above as your first guesses and verify from there.

Every address this permutator generates (22 from a name and a domain)

Most permutator pages will not tell you how big the list is before you run it, which matters because you have to verify whatever comes out. This one is fixed and countable: a first name, a last name and a domain return exactly 22 addresses. Fill in the optional middle name and nickname fields as well and you get 30. Identical results are removed, so a name where two patterns collapse into the same address returns fewer, and a first name on its own returns two.

Every candidate belongs to one of five families. The separators covered are the dot, the underscore, the hyphen and no separator at all, applied in both name orders, alongside the versions built on initials. There is no padding in the set: each pattern is one that real companies assign, which is what keeps 22 small enough to verify in a single pass instead of a spreadsheet of hundreds of throwaway strings.

The list is not ranked, because the tool does no lookup and has no way to know which pattern this particular company uses. If you want the formats ordered by how often companies pick them, run the same name through our company email format finder and start with its top candidates, then fall back to the full 22 if none of them verify.

What to type when the name or the domain is messy

The domain field is forgiving on purpose. Paste https://www.company.com/about-us and it is reduced to company.com before any address is built: the scheme, the www, a leading @ and everything after the first slash are stripped out. So you can copy a company URL straight from the address bar, or paste the part after the @ of an address you already have, without tidying it up first.

Names are lowercased and spaces are removed. A two-word first name like Mary Anne therefore becomes maryanne, which is a format some companies really use, but it should not be your only shot. Put the second word in the middle name field as well and you also get maryannesmith and mary.a.smith, which covers how most administrators would have created the mailbox.

Accents and hyphens are kept exactly as you type them, so José stays josé and Smith-Jones stays smith-jones. Some domains do use them, so that is the honest default, but plenty of companies strip accents when they create accounts. Run the plain spelling as a second pass (jose, nunez) and verify both sets. For a double-barrelled surname, try the hyphenated version and each half on its own.

If all you have is a full name in one string, or a messy exported list of them, split it into first and last with our free name splitter before you permutate. And when you genuinely only know one of the two names, enter it on its own: you get the two addresses that can exist for it rather than a padded list.

How to guess someone's email without sending a test message

The fastest shortcut is to find one address you already know at the same domain and copy its pattern. A named contact on the company's contact page, a press release, or the Contact info panel on a LinkedIn profile tells you the convention for the whole company: if mary.jones@acme.com is public, your target almost certainly follows first.last too. One confirmed address cracks the format for everyone.

If no reference address is available, treat the generated list as a shortlist and confirm it mechanically instead of emailing people to see what bounces. Run the domain through Emailchaser's MX lookup to check it can receive mail at all and see which provider hosts it, then verify the shortlist so you send only to the address that actually resolves.

The shortcut works in reverse too. If you already have one address at the domain and want to know whose it is before you copy its pattern, our reverse email lookup reads the name and the employer straight out of it, which tells you whether the format you are about to copy belongs to a real person or to a shared role account like info@.

Why a correct-looking guess still bounces

The first thing to rule out is a catch-all (accept-all) domain: it accepts mail to every local part, so a wrong guess will not bounce and a verifier can only report accept-all rather than a clean valid or invalid. On those domains you cannot infer the real address from delivery alone.

Beyond catch-alls, a well-formed guess commonly fails for a few reasons. The company may send from a subdomain or a different root than its website (the site is acme.io but mail runs on acme.com, check the MX records or a known public address). The person may use a nickname, a maiden or married name you did not supply, or an accented or hyphenated name that gets normalised inconsistently (Jose vs josé, mary-kate vs marykate). And addresses like info@ or sales@ are shared role accounts, not personal mailboxes. Filling in the middle-name and nickname fields widens the coverage for the first two cases.

Gmail, Google Workspace and Outlook format differences

On a company domain, both Google Workspace and Microsoft 365 let the administrator choose the staff format when accounts are created. first.last@ and flast@ are the usual defaults, but nothing is enforced across providers, which is exactly why generating the full set beats assuming one pattern.

Personal Gmail behaves differently: on @gmail.com addresses Google ignores dots, so john.smith@gmail.com, johnsmith@gmail.com and jo.hn.smith@gmail.com all reach the same inbox. Business domains do not do this, so on a custom domain each permutation is a distinct mailbox. On Microsoft 365 domains the sign-in name usually matches the primary address (often first.last@), though admins frequently add aliases that also deliver.

One rule cuts the list down on personal Gmail. Google's own username guidance (checked 30 August 2026) says a gmail.com username may contain letters, numbers and periods only, and rejects underscores, dashes, plus signs, apostrophes and two periods in a row, with no non-alphanumeric character at the start or end. So on an @gmail.com address the underscore and hyphen candidates in your list cannot exist and you can ignore them. On a company domain the administrator creates the mailbox, so those separators are back in play and worth verifying.