How to Find a Company's Email Address Format
Once you know a company's email pattern, you can reach anyone there. Here's how to find the format and use it responsibly.
Overview
Most companies use a single, predictable email pattern — first.last@, flast@, first@, or similar — so once you know the format, you can construct almost anyone's address there. The reliable way to find it is to identify one known address at the company, infer the pattern, build your target's address from it, and then verify. Verification matters because patterns have exceptions (duplicates, legacy addresses, personal aliases).
Work out the pattern from one known address
Find one confirmed address at the company — from a team/about page, a press contact, an email they've sent you, a finder tool, or even a GitHub commit — and read its structure. "jane.doe@acme.com" tells you the format is first.last@acme.com, so your target John Smith is almost certainly john.smith@acme.com. Domain-search tools like Hunter go further and display the most common detected pattern for a domain (with a confidence level), which shortcuts the guessing entirely.
The common formats, roughly in order of popularity: first.last@ (jane.doe@), first@ (jane@), flast@ (jdoe@), firstl@ (janed@), first_last@, and lastf@. Watch for variations: large companies sometimes run more than one format, common names get disambiguated (jdoe vs jadoe), and acquired teams may keep a legacy domain. The pattern is a strong default, not a guarantee for every individual — which is exactly why the next step matters.
- Find one confirmed address and read its structure
- Apply that pattern to your target's name
- Common formats: first.last@, first@, flast@, firstl@
- Use a domain-search tool to detect the format automatically
Build the candidates, then verify
When you're not sure of the format, generate all the likely variations with an email permutator (a tool or spreadsheet that produces first.last@, flast@, first@, etc. for a name + domain), then test which one is real. A pattern-built address is an educated guess until confirmed, so verify every candidate before sending. Be careful with catch-all (accept-all) domains: they accept mail to any address, so acceptance alone doesn't prove a mailbox exists — lean on the verifier's score and your judgment there.
Why this matters: sending to unverified guesses produces bounces, and a high bounce rate is one of the fastest ways to damage your sender reputation. Stay compliant too — business addresses, relevant outreach, honored opt-outs. Mailbase enforces suppression at send time, so a bounced or opted-out address never gets re-mailed.
- Use a permutator to generate candidates, then verify which is real
- Catch-all domains need extra judgment — acceptance ≠ a real mailbox
- Bounces from guesses damage sender reputation
- Business addresses only; stay compliant and honor opt-outs
Common Mistakes
- Sending to found addresses without verifying them first.
- Treating a finder's confidence score as a guarantee.
- Guessing a pattern on a catch-all domain and assuming it lands.
- Harvesting personal addresses instead of business ones for B2B outreach.
Sources & Further Reading
Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.
Related guides
More on company email address format and the surrounding finding emails workflow:
FAQ
How do I find a company's email format?
Find one confirmed address at the company — from a team page, press contact, an email they've sent, or a domain-search tool like Hunter — and read its structure (first.last@, flast@, first@). Apply that pattern to your target's name, then verify the constructed address before sending.
What are the most common email formats?
Roughly in order: first.last@ (jane.doe@), first@ (jane@), flast@ (jdoe@), firstl@ (janed@), and first_last@. Most companies pick one and use it consistently, so identifying one known address usually reveals the format for everyone.
Are company email patterns reliable?
Usually, since most companies use one consistent format, but there are exceptions: large firms may run multiple patterns, common names get disambiguated, and acquired teams keep legacy domains. Treat the pattern as a strong default and always verify the specific address.
What is an email permutator?
A tool or spreadsheet that generates the likely email variations for a name and domain (first.last@, flast@, first@, etc.) so you can test them. It's a guessing aid — you still need to verify which variation actually receives mail before you send to it.