Give this tool one person's name and known email address at a company, and it detects which of the ten most common corporate naming conventions is in use — then applies that same pattern to predict an address for anyone else at that domain.
Most organizations settle on one consistent scheme for generating employee email addresses, chosen once during their email system setup and applied to everyone who joins afterward. This tool checks the known address you provide against ten of the most common patterns worldwide: first.last, firstlast, first, last, first initial + last (flast), first + last initial, first initial + last with a dot, last + first initial, last.first, and first + last initial with no separator.
Once a match is found, entering a second person's name applies the same transformation to predict their likely address at the same domain — useful for reaching a specific person at a company where you already know one colleague's format, without guessing blindly.
Not every organization follows one of these ten patterns consistently — some incorporate middle initials, employee numbers, nicknames, nonstandard separators, or simply don't have a uniform scheme at all, especially at smaller companies or after mergers. A detected pattern is a strong hypothesis based on one data point, not a confirmed rule. Always verify a predicted address — for example with the Email Deliverability Tester's MX check, or a low-risk method like checking a company directory — before relying on it for anything important.
If you have access to more than one known address at the same company, it's worth cross-checking that all of them agree on the same pattern before relying on a prediction, since a mismatch usually signals the company doesn't enforce one convention consistently across every team or office.
The tool will tell you the pattern wasn't recognized. That can mean the company uses a custom scheme, a nickname, a middle initial, or a numeric suffix that falls outside the ten most common formats checked here.
It's only as reliable as the assumption that the whole company follows one consistent naming convention, which is common but not universal. Treat a prediction as a strong first guess, not a confirmed result.
Yes — the second person's name and domain fields are optional. Leave them blank if you only want to see which pattern the first address matches.
No, it only applies a pattern — it doesn't check mailbox existence. Combine it with the Email Deliverability Tester for a domain-level MX check as a next step.
The domain is auto-filled from the known email you enter, but it's editable in case you want to apply a detected pattern to a different domain than the one it was detected from.