Short answer
A company email format is the pattern a company uses to build staff addresses, such as first.last@ or flast@ (first initial plus last name). In press releases US public companies filed with the SEC in September and October 2026, first.last was the most common format for named contacts (52% of 264 companies), followed by flast (33%). To find a specific company's format, collect two published addresses from different people at its domain, then verify the address you build.
- first.last@ and flast@ together covered 85% of the 264 public companies in our sample.
- 57% of companies listed only shared inboxes such as ir@ or media@, which say nothing about the format.
- Two published addresses from different people at the same domain settle a company's format; only 3% of companies mixed patterns.
- The standard lets the part before the @ be case-sensitive and caps it at 64 characters.
- For your own company, pick one pattern, set a rule for duplicate names and keep postmaster@ and abuse@.
On this page
- The common company email formats
- Where these numbers come from
- How to find a company's email format, step by step
- When the evidence conflicts
- Names that need care
- The rules for a valid email address
- How to choose your own company's email format
- If you meant the format of a business email
- Worked example: confirming a format before you send
- Self-check
- Common mistakes
- Sources
- Questions people ask
This guide is for two readers: sellers and recruiters who need to work out the address format at a company they're contacting, and founders or IT admins choosing a format for their own company. It gives the common patterns with fresh data from SEC filings, a method for finding any company's format, what to do when the evidence conflicts, the syntax rules from the email standards, and how to choose your own.
The common company email formats
Here's each pattern for a fictional Elena J. Marsh at company.example, with how often it appeared as the main format for named contacts in our sample of US public companies:
| Format | Example | Companies | Share |
|---|---|---|---|
| first.last | elena.marsh@company.example | 138 | 52% |
| flast (first initial + last) | emarsh@company.example | 86 | 33% |
| first | elena@company.example | 10 | 4% |
| first_last | elena_marsh@company.example | 7 | 3% |
| firstlast | elenamarsh@company.example | 5 | 2% |
| first.m.last | elena.j.marsh@company.example | 4 | 2% |
| f.last | e.marsh@company.example | 4 | 2% |
| lastf | marshe@company.example | 4 | 2% |
| Other (firstl, last.first, fmlast, last_first) | elenam@, marsh.elena@ | 6 | 2% |
| Total | 264 |
Shares are rounded, so they add to slightly more than 100%. The two leaders matter most: if you know nothing else about a company, first.last is the best single guess, and it's still wrong about half the time.
Where these numbers come from
We used the SEC's EDGAR full-text search to find press releases attached to 8-K filings (exhibit 99) between 1 September and 29 October 2026 that contained "media contact", "media contacts", "investor contact", "investor relations contact" or "press contact". That returned 1,549 exhibits; we kept the latest one per company, 1,003 in all, and extracted every email address.
- 667 companies listed at least one address on their own domain (we matched each domain to the company's name).
- 379 of those (57%) listed only shared role addresses. The most common were ir@, investors@, media@, investorrelations@ and press@.
- 264 companies listed at least one named person's address that we could match to the name printed beside it. We counted each company once, by its most common pattern. The table above is that count.
- 9 of the 264 (3%) used two different patterns for different people in the same release.
The limits: these are US-listed companies, which skew large, and the addresses belong to investor relations and communications staff, not every employee. Small private companies weren't in the sample. Our name matching skipped 42 named addresses it couldn't match and may misread a few. Treat the shares as a guide to the odds, not a rule for any one company.
How to find a company's email format, step by step
- Confirm the mail domain. The domain a company uses for email isn't always its website domain. An MX lookup tells you whether a domain receives mail; how to find a business email address shows the commands.
- Collect two or more published addresses from different people. Good places: the contacts block at the end of press releases, the company's team and press pages, conference speaker pages, reports and PDFs. For a listed company, search EDGAR full-text search for the domain with its @ sign in quotation marks (for example "@company.example"), which finds filings that contain addresses at that domain.
- Throw out addresses that can't tell you the format. Shared inboxes (ir@, media@, info@) carry no name. Addresses at a PR or investor relations agency's domain show the agency's format, not the client's.
- Compare the patterns. If two named addresses agree, that's the format. If they don't, use the decision table below.
- Build the address from the name the person uses at work, taking care with the edge cases further down.
- Verify it. Run it through an email verification tool. Treat an accept-all result as unconfirmed, because the server accepts every address.
The difference evidence makes is large. Guessing first.last with no evidence matched our sample about half the time. Two matching published addresses fail only when a company mixes patterns, which 3% of companies in our sample did.
When the evidence conflicts
| What you find | What it usually means | What to do |
|---|---|---|
| Two named addresses, same pattern | That's the format | Build the address and verify it |
| Two named addresses, different patterns | Mixed formats: a name clash, an acquired business or a change over time | Prefer the pattern used by people in a similar role or joining recently; verify, and confirm another way if the result is accept-all |
| Only shared inboxes (ir@, info@, media@) | No evidence about personal addresses | Keep looking, or call and ask |
| Named addresses at a different domain | An agency, a subsidiary or an old brand | Check MX on each domain and use only the one the company receives mail on |
| One named address only | A likely format, not a confirmed one | Find a second, or verify and send a single careful email |
| Verifier says accept-all | The server accepts every address, so nothing is confirmed | Send only if the format is confirmed by published addresses, one at a time |
Names that need care
| Situation | Example | What to try first |
|---|---|---|
| A work name that differs from the legal name | Robert who goes by Bob | The name on their company bio or LinkedIn profile |
| Hyphenated surname | Daly-Huerta | The hyphen dropped (dalyhuerta), then kept |
| Apostrophe | O'Connor | Dropped: oconnor |
| Accented letters | José Núñez | Plain letters: jose.nunez |
| Two people with the same name | A second Elena Marsh | A middle initial (elena.j.marsh) or a number |
| Dots in the local part at a Google Workspace company | elena.marsh vs elenamarsh | Treat them as different addresses: Google says dots change work and school addresses, unlike personal Gmail |
The rules for a valid email address
These come from the internet's email standards, RFC 5321 (how mail is sent) and RFC 5322 (how addresses are written):
| Rule | What the standard says |
|---|---|
| Structure | A local part, the @ sign, then a domain |
| Characters in the local part | Letters, digits, dots and a set of symbols (below). Dots can't come first or last or appear twice in a row |
| Local part length | At most 64 octets (characters, for plain ASCII addresses) |
| Domain length | At most 255 octets |
| Whole address | A mail path is capped at 256 octets including the angle brackets around it, which leaves 254 for the address itself |
| Case | Domains aren't case-sensitive. The local part must be treated as case-sensitive by mail software, though the standard says relying on that "impedes interoperability and is discouraged" |
The symbols RFC 5322 allows in an unquoted local part are ! # $ % & ' * + - / = ? ^ _ { } ~, the backtick and the vertical bar. Staff addresses rarely use them: of the 406 named addresses in our sample, 242 used a dot, 9 an underscore, 4 a hyphen and 1 a digit, and none used any other symbol. Copy the local part exactly as published.
How to choose your own company's email format
If you're setting up email for a new company, or tidying an old one:
- Pick one pattern for everyone. first.last is the most common among the public companies we checked and reads clearly. flast is shorter and the second most common. first@ works for a handful of people and stops working at the second Elena.
- Write down the rule for duplicate names now, such as a middle initial and then a number, so the tenth hire doesn't invent a new pattern.
- Add the other common pattern as an alias where your email provider allows it, so guessed addresses still arrive.
- Keep the standard role addresses. RFC 2142 lists common mailbox names, including info, sales, support and marketing for business functions, and postmaster, abuse and security for operations. It says these names must work regardless of case.
- Avoid nicknames, numbers and symbols in staff addresses. They're hard to guess and easy to mistype.
- Use your own domain, not a free mailbox, for anything customers see. A professional email address format is simply your name in the company's pattern at the company's domain.
If you meant the format of a business email
Some people searching "business email format" want the layout of the message rather than the address. A business email has five parts: a specific subject line, a greeting with the person's name, an opening line that says why you're writing, a body of a few short paragraphs, and a sign-off with your name, role and contact details. For sales emails specifically, how to write a cold email covers each part with examples.
Worked example: confirming a format before you send
Illustrative example. The companies, people and addresses are fictional, to show the method.
The seller wants to email Priya Raman, VP of Operations at Calloway Foods (callowayfoods.example), a listed food distributor.
Step 1, domain. An MX lookup on callowayfoods.example returns mail servers.
Step 2, published addresses. An EDGAR full-text search for "@callowayfoods.example" finds an 8-K press release and the annual proxy statement. The press release lists an investor contact at ir@callowayfoods.example and a media contact, Tom Becker, at tbecker@callowayfoods.example. The proxy statement gives the corporate secretary, Ana Ruiz, at aruiz@callowayfoods.example.
Step 3, discard. ir@ is a shared inbox, so it tells you nothing about the format.
Step 4, compare. Two named addresses from two different people, both flast. Format confirmed.
Step 5, build. praman@callowayfoods.example.
Step 6, verify. The verification tool returns valid. Send.
What the base rate would have cost: guessing the most common format, priya.raman@callowayfoods.example, would have bounced. Across a list of 200 companies, guessing first.last everywhere would mean roughly half your emails going to the wrong address, enough to hurt the delivery of the rest. At list scale, Bebop finds the right contacts at each company with their contact details, so you start from the person; verify before any large send, whatever the source.
Self-check
- You've confirmed which domain receives the company's mail.
- The format comes from at least two named, published addresses at that domain, not from a shared inbox or an agency.
- You've handled the name carefully: work name, hyphens, apostrophes, accents.
- The address verified as valid, or it's accept-all with a confirmed format and you're sending one email.
- You're not sending to several guessed variations to see which one works.
Common mistakes
- Using the most common format as a fact. It's a starting guess, right about half the time.
- Learning the format from ir@ or press@. Shared inboxes carry no name.
- Copying an agency's pattern. Press release contacts are often at a PR firm's domain.
- Emailing every permutation. It bounces and, if the email otherwise breaks CAN-SPAM, using addresses generated by combining names and letters into permutations makes the violation aggravated.
- Ignoring dots on Google Workspace. At those companies, elena.marsh@ and elenamarsh@ are different mailboxes.
Next step: if you found the person on LinkedIn, see how to find someone's email on LinkedIn for the routes that keep you within LinkedIn's rules.
Sources
- EDGAR full-text search: 8-K press releases with media or investor contacts, 1 September to 29 October 2026 (Bebop analysis of 1,003 companies), US Securities and Exchange Commission, accessed 30 October 2026
- EDGAR Full Text Search FAQ, US Securities and Exchange Commission, accessed 30 October 2026
- RFC 5321: Simple Mail Transfer Protocol (sections 2.4 and 4.5.3.1), Internet Engineering Task Force (RFC Editor), October 2008
- RFC 5322: Internet Message Format (sections 3.2.3 and 3.4.1), Internet Engineering Task Force (RFC Editor), October 2008
- RFC 2142: Mailbox Names for Common Services, Roles and Functions, Internet Engineering Task Force (RFC Editor), May 1997
- Dots don't matter in Gmail addresses, Google Gmail Help, accessed 30 October 2026
- 15 U.S. Code § 7704(b), Aggravated violations relating to commercial electronic mail, Legal Information Institute, Cornell Law School, accessed 30 October 2026
Written by the Bebop team at Blackpearl Group. Published .
Questions people ask
What is the most common company email format?
first.last, as in elena.marsh@company.example. In press releases US public companies filed with the SEC in September and October 2026, it was the main format for named contacts at 52% of the 264 companies we could check, followed by first initial plus last name (flast@) at 33%. Small private companies may differ, and any one company can use another pattern, so confirm it with published addresses.
How do I find a company's email format?
Find two or more published addresses from different people at the company's mail domain, in press releases, on its team or press pages, in reports or, for listed companies, by searching SEC EDGAR full-text search for the domain in quotes. Ignore shared inboxes such as ir@ and agency addresses. If the named addresses follow the same pattern, that's the format. Verify any address you build from it.
What is a professional email address format?
Your name in your company's pattern at your company's own domain, such as elena.marsh@company.example or emarsh@company.example. Avoid nicknames, numbers and symbols, and don't use a free mailbox for work customers see. If you're choosing a format for a company, first.last is the most common among US public companies and reads clearly; set a rule for duplicate names before you need it.
Are email addresses case-sensitive?
The domain never is. The part before the @ can be: RFC 5321 says mail software must treat it as case-sensitive, so that on some hosts smith and Smith are different users, but it also says exploiting that is discouraged because it causes delivery problems. Copy the local part exactly as published.
How long can an email address be?
The part before the @ can be up to 64 octets and the domain up to 255, according to RFC 5321. The standard also caps a mail path at 256 octets including the angle brackets around the address, which leaves 254 characters for the address itself. Staff addresses are nearly always far shorter, and very long ones are easy to mistype.
What characters are allowed in an email address?
Under RFC 5322, an unquoted local part can contain letters, digits, dots and the symbols ! # $ % & ' * + - / = ? ^ _ { } ~ plus the backtick and vertical bar. Dots can't come first or last or appear twice in a row. The domain uses letters, digits, hyphens and dots. Company staff addresses almost always stick to letters and dots, sometimes with a hyphen or underscore.