Most companies build work addresses from one of a handful of patterns, and first.last@ is the most common by a wide margin. You can work out a company’s pattern from two or three real addresses, but a pattern is an inference, not proof. Every address you build from it still needs to be verified before it goes into a campaign, because wrong guesses become bounces, and bounces damage the sending domain you depend on.
This guide covers the formats you will meet, how common each one is, how to find a specific company’s rule, what to do when a company uses more than one, and how to check addresses before you send.
Key Takeaways
- One format dominates: first.last@ accounts for 47.7% of B2B addresses in one 2026 analysis, followed by flast@ at 26.8% and first@ at 8.1%.
- Larger companies are more predictable. Small teams and startups are the least consistent and the most likely to use first@ or aliases.
- Two matching named addresses on the company’s own domain are enough to trust a pattern. One address is only a hint, and shared inboxes like info@ do not count.
- A guessed address is a hypothesis. Test one or a small sample first, verify, and only then build the full list.
- Commercial email to business addresses falls under US CAN-SPAM rules too, so a guessed address still needs a clear opt-out and honest headers.
Table of Contents
- What a company email format actually is
- The most common company email formats
- How to find a company’s email format
- When a company uses more than one format
- Why guessing blind hurts you
- How to verify a guessed address
- Rules to keep in mind before you send
- Doing this at scale
- Send to verified addresses with PlusVibe
- Our view on email patterns
- FAQ
- Sources
What a company email format actually is
A company email format (also called an email pattern) is the rule a business uses to build each employee’s address from their name. Everything after the @ is the company’s domain. Everything before it is the local part, and the format decides what goes there: full first name, last name, initials, a separator, or some mix.
Two consequences follow from that.
First, there is no universal rule. The internet mail standard treats the local part as meaningful only to the receiving domain, so nobody outside the company can read the rule from a single address. The pattern belongs to whoever administers that mail server, and it is typically set once and applied to each new hire.
Second, a format is not the same as a role address. The internet standard for common mailbox names (RFC 2142) reserves names such as info, sales, marketing and support for functions rather than people. A press release that lists a spokesperson next to press@ does not tell you the spokesperson’s personal address. Keep these out of your pattern research.
The most common company email formats
Here is how the main formats look for a fictional employee, Jane Smith, at example.com, along with their share of B2B addresses in Allegrow’s 2026 analysis.
| Format | Example | Share of B2B addresses |
|---|---|---|
| first.last@ | jane.smith@example.com | 47.7% |
| flast@ | jsmith@example.com | 26.8% |
| first@ | jane@example.com | 8.1% |
| firstlast@ | janesmith@example.com | 2.3% |
| first_last@ | jane_smith@example.com | 2.3% |
| f.last@ | j.smith@example.com | 2.1% |
| last@ | smith@example.com | 1.2% |
The exact shares differ from one dataset to the next, because every dataset samples different companies. Treat them as a ranking of likelihood, not as exact odds. In every dataset the order at the top is the same: first.last@ first, then flast@ and first@ in some order.
There are a few more variations worth knowing:
- Reversed order, such as smith.jane@, is rare but real, especially in some regional or legacy setups.
- f.last@ (j.smith@) is the form you meet more often in European organizations.
- Tie-breakers appear when two people share a name: a middle initial (jane.a.smith@), a number (jane.smith2@) or a shortened variant (janes@).
Why company size changes the odds
The bigger the company, the more rigid the format. In the same Allegrow analysis, first.last@ reaches 74.2% of addresses at companies with 10,000 or more employees, while the informal first@ peaks at around 17% in very small teams. A large IT department automates account creation and applies one rule. A five-person startup often lets people pick their own handle, or sets up short aliases for the founders.
That is why a guess works best at mid-size and large companies and worst at tiny ones. If you want more context on email conventions across company types, from startups to large tech enterprises, it helps to see how the choice follows the way each team is organized.
How to find a company’s email format
The method that holds up is simple: collect real addresses, find the shared shape, and test it.
Step 1: Confirm the mail domain
Check that the domain you are building addresses on is the one the company actually uses for mail. Many companies use a different domain for email than for their website, or run several domains after acquisitions or rebrands. A domain with no mail records at all cannot receive email, so it is worth a quick check before you go further. This is the first spot where a mistake costs you: an address built on the wrong domain bounces every time.
Step 2: Collect two or three named addresses
Look for addresses of real, named employees published by the company itself. The best places, roughly in order of payoff:
- The company’s own website. Search Google for the domain in quotes with the site operator, for example “@company.com” site:company.com.
- PDFs, such as reports, whitepapers, and event programs (add filetype:pdf to the search).
- Press releases and media contact blocks.
- Speaker and conference pages, podcast notes and webinar listings.
- Open-source repositories and academic papers, where authors often list their work addresses.
- Your own inbox and CRM, where past replies and signatures already contain real addresses.
Exclude role mailboxes (info@, sales@, support@, press@) as discussed above. They tell you nothing about how people are named.
Step 3: Read the rule they share
Two matching addresses on the company’s own domain are enough to trust the rule. If you find jane.smith@ and omar.khan@, the format is first.last@. If you find only one, treat it as a hint. A single published address may be an alias, an early-hire exception or a name-clash variant.
Three or more addresses from different teams and different years give you a format you can build a list on.
Step 4: Generate the address for your prospect
Take the prospect’s name as it appears on their LinkedIn profile or the company’s team page, apply the rule, and write it in lowercase. Watch for these traps:
- Nicknames. Robert may be rob@ or robert@. Use the form the company’s published addresses suggest, usually the legal first name.
- Hyphens, apostrophes and accents. Many companies strip them, while some keep a hyphen. Look for an existing address with the same feature.
- Two-part surnames. Check whether the company drops the space (vanderberg) or keeps a separator.
- Common names. John Smith at a 5,000-person company may be john.smith2@. A generated address might also reach a different person with the same name, which is worse than a bounce.
Step 5: Test before you build the list
Generate the address for a small sample of 10 to 20 people at the company or across a few companies using the same format. Verify them (see below). Only extend the pattern if the deliverable hit rate is strong.
When a company uses more than one format
It happens often. After an acquisition, a rename or a regional rollout, a company may run two or three formats side by side. Large companies in particular tend to have legacy staff on an older pattern (flast@, say) and newer hires on first.last@.
When the evidence conflicts:
- Match the address you found to the person’s unit, region and hire date. A recent hire in the main business likely follows the current rule. A person from an acquired company may still have the old one.
- Where you cannot tell, build one address per candidate rule and verify both. Do not send to both unverified.
- Remember aliases. Google Workspace allows up to 30 aliases per user and Microsoft up to 400, so a short published address like jane@ can sit on top of a real jane.smith@. Both reach the same person, but only one is the format.
Why guessing blind hurts you
Guessing without verification is the cheapest way to damage a sending domain. Inbox providers such as Gmail and Outlook watch bounce patterns across your whole sending domain, not campaign by campaign. A string of invalid addresses tells them your domain writes to people who do not exist.
Data quality is the reason this matters. In a study of 134,653 verified B2B emails by Listar, only 64.8% were confirmed valid and deliverable, 23.7% were invalid and 11.4% were inconclusive, largely because of catch-all domains. The same study treats a bounce rate under 2 to 3% as healthy before sender reputation starts to suffer. A list built from unverified guesses can sit well past that line from the first send.

How to verify a guessed address
Verification checks whether the mailbox exists without sending a message. The verifier connects to the domain’s mail server, proposes the address and reads the response. A positive reply means the server accepts the mailbox, while a rejection code means it does not exist.
This works well on most domains, with one big exception: catch-all domains accept every address, real or not, so a pass tells you nothing about the person. Catch-all handling is the hard part of the job, and results depend on how a verifier treats those addresses. Treat them as risky, segment them out of your main sequence and send to them in small, monitored batches, or find a confirmed address through another source.
A practical routine:
- Verify at the point of building the list, not after you have loaded it into a campaign.
- Keep only deliverable results. Remove invalid, disposable and syntax-error addresses and set aside accept-all and unknown results.
- Re-verify older lists. Addresses go stale as people change jobs, so lists that are a month or more old deserve another pass.
- Watch bounces after sending and suppress any domain or source that keeps producing them.
Our own guides go deeper on how to verify an email address and on handling catch-all emails in B2B, and the email verification glossary entry explains each result status.
Rules to keep in mind before you send
A guessed address that verifies is still an address of a real person, and sending to it is regulated. In the US, the FTC’s CAN-SPAM guide for business states that the law makes no exception for business-to-business email. It covers all commercial messages, not only bulk mail. In practice that means accurate header information, a subject line that is not deceptive, a clear identification of the message as an ad, a valid physical postal address and a working way to opt out that you honor promptly.
If your list includes recipients in the EU or UK, the rules differ and generally lean more on legitimate interest and documentation, so check them with a lawyer before you send to those contacts. Keep a note of where each address came from and how you built it, so you can delete it if someone asks.
Doing this at scale
Pattern guessing is fine for a handful of prospects. At agency or high-volume scale, the work shifts from guessing to a system: find the pattern once per company, apply it to every contact there, verify in bulk, and keep every failed address away from your campaigns.
That is where the tools you use make a difference. Enrichment and verification in the same workflow as your sequences mean the list is checked before a single email goes out. Our lead enrichment glossary page explains how that step works, and our guide to scaling cold email without burning your domains covers what to protect once volume grows.
Send to verified addresses with PlusVibe
PlusVibe is a cold email platform built for deliverability at high volume, and it includes lead enrichment and email verification alongside multi-step sequences, a unified reply inbox and seed tests that show where your emails land at Gmail, Outlook and other providers. You can also collect prospects from LinkedIn and the web with the Chrome extension. Plans start at $37/month, Business is $77/month for 150,000 emails, and Agency starts at $497/month for 500,000+ emails, with no fee per connected mailbox.
Start the 14-day free trial, no credit card needed, from the PlusVibe plans page.
If you only want to check a few addresses first, the free email verification tool is the quickest place to begin.
Our view on email patterns
Pattern guessing is a research skill, and it deserves the same discipline as any other research. You collect evidence, you form a hypothesis, and you test it before you rely on it.
What we see as the real risk is not the guess itself but what happens next. A bad guess becomes a bounce, and bounces build up across a sending domain. We built PlusVibe around the idea that the inbox is decided before you hit send: private infrastructure, a private warm-up pool and seed tests that show where your real emails land.
That is why we pair outreach with verification. Receipts over vibes: verify the address, send relevant and honest emails, respect the opt-out, and measure placement. Cold outreach is honest work when it follows that code.
Yaro
FAQ
What is the most common company email format?
First.last@ (jane.smith@company.com) is the most common. One 2026 analysis puts it at 47.7% of B2B addresses, with flast@ at 26.8% and first@ at 8.1%. Larger companies follow it more consistently than small ones.
How do I guess someone’s email address when I know the company’s pattern?
Apply the pattern to the person’s name as the company writes it, in lowercase, then verify the result. Check nicknames, hyphens and common-name collisions first. Test a small sample before building a full list.
Can I trust one address I found to define the format?
No. One address is a hint, since it may be an alias or an exception. Two matching named addresses on the company’s domain make a format you can trust, and three or more from different teams make it solid.
Are info@ and sales@ addresses useful for finding the format?
No. These are role mailboxes reserved for functions, so they say nothing about how employees are named. Use addresses of named people instead.
Do I need to verify addresses if the pattern looks right?
Yes. A correct pattern can still produce a wrong address because of duplicates, nicknames or departures. Verification keeps bounces low and protects your sending domain.
Sources
- Allegrow: most common B2B business email address formats
- Listar: B2B email data quality study
- RFC 2142: Mailbox Names for Common Services, Roles and Functions
- FTC: CAN-SPAM Act compliance guide for business


.jpeg)

























































