Patterns generated
The tool generates common company email formats such as first, last, firstlast, first.last, flast, f.last, firstl, first.l, lastfirst, last.first, lastf, l.first, first-last, last-first, first_last, and last_first.
If you add a middle name or initial, it also adds middle-based formats such as fmlast, fm.last, firstm.last, first.middle.last, first-m-last, and first_middle_last.
The output is newline-separated so you can paste it into a spreadsheet, enrichment workflow, or contact research doc. For a full prospect list, use the bulk email permutator.
Domain mail check
The tool checks public DNS records for the company domain. If it finds MX records, the domain is configured to receive email. If it finds null MX, the domain explicitly says it does not accept email.
This is useful because it catches obvious dead ends before you copy a list of possible addresses. It still does not verify that any specific person has a mailbox at that domain.
Name cleanup
Names are converted to lowercase ASCII and punctuation is handled before patterns are generated. Hyphenated and multi-part names produce collapsed, hyphenated, and dotted variants.
Email domains are not case sensitive. The part before the @ can be case sensitive in the formal email specs, but most modern providers treat uppercase and lowercase versions as the same mailbox. The tool uses lowercase so the list is easier to compare, paste, and dedupe.
How to narrow the candidates
Start with the shortest list that could plausibly be right. Most companies use one or two formats across employees, so a known colleague email is stronger evidence than a long list of generated possibilities.
- Strong clue
- Another employee at the same domain uses the same pattern.
- Normal starting point
- first.last, firstlast, or first initial plus last name.
- Fallback
- Middle-name patterns, unless the person uses a middle initial publicly.
- Avoid
- Sending to several versions of the same person. Save alternates in a research note instead.
A Gmail contact chip can be a clue
One manual check is to copy the generated list, paste it into a Gmail draft, and look at the recipient chips before sending anything. If one address shows a richer hover card, profile photo, or detailed contact view while the other permutations show generic cards, check that address first.
Do not treat this as email verification. Google documents that Gmail contact suggestions can be based on contacts and prior interactions, including people you have emailed in Gmail. Google also says a Gmail profile picture can show up when someone sees your name in Gmail, but it does not publish a rule saying a richer hover card proves that a mailbox exists. See Google's contact suggestions documentation here and Gmail profile picture documentation here.
A visible photo or detailed card does not prove the mailbox exists. A generic card does not prove it is wrong. Use Gmail chip behavior only as a weak account-specific clue, then cross-check with a public company pattern, a known colleague email, or another reliable source before sending.
What it does not verify
This is a deterministic email permutator. It does not check whether an address exists, send test messages, or query mailbox providers.
Do not send the same email to every generated address. Use the permutations to narrow your research, then send to the best candidate once you have a stronger signal.
Treat the output as candidate addresses, not a verified list. Run the best candidates through a verification step before outreach, and stay within the sending policies of whatever tool runs the campaign.
Questions, answered.
Neither. The permutations run entirely in your browser, and the one network call is the optional domain check, which asks a same-site API to read public DNS records. No account, no payment.