Glossary · Emails and phones

What is a company email format?

The short answer

A company email format is the rule a company uses to turn employees' names into addresses, such as {first}.{last}@company.com. Each domain has a usual format, but it is a habit, not a law: exceptions, aliases and name changes mean that an address built from the format stays a guess until it is verified.

Updated
Read
3 min
Written by
Antoine Blitz
On this page8 sections
  1. Real data
  2. What are the most common company email formats?
  3. How do you find a company’s email format?
  4. Does every employee follow the company email format?
  5. Why is a guessed email address risky?
  6. How do you get a verified address instead of a guess?
  7. Related terms
  8. Questions people ask

Real data

The formats behind verified addresses at three companies

Eight US sales profiles at each of Gong, HubSpot and Stripe, sent one by one to Find Work Email on November 10, 2026. Each group counts the verified addresses that came back on the company's own domain, by the format they follow; no address and no name is shown.

Returned by the BlitzAPI API on

POST/v2/enrichment/email

gong.io: 8 verified addresses

{first}.{last}
8

The MX records of gong.io point to Proofpoint, a security gateway in front of the mailboxes.

POST/v2/enrichment/email

hubspot.com: 7 verified addresses

{f}{last}
5
{first}.{last}
1
{first}
1

The {first} address came back with a second address on the same domain, in {f}{last}. One more profile returned an address on another organization's domain and is left out. MX: Google.

POST/v2/enrichment/email

stripe.com: 4 verified addresses

{first}{l}
2
{first}
1
{first}{last}, with a last name not on the profile
1

Profiles that returned no verified address, or only one at an earlier employer, are left out. MX: Google.

What are the most common company email formats?

The most common company email formats combine the first name, the last name and the company domain in a few fixed ways. Here they are for Maya Chen at acme.com:

Format Example
{first}.{last} maya.chen@acme.com
{f}{last} mchen@acme.com
{first} maya@acme.com
{first}{l} mayac@acme.com
{first}{last} mayachen@acme.com
{first}_{last} maya_chen@acme.com
{last}.{first} chen.maya@acme.com

A company usually picks its format once, when it sets up its mail, and keeps it as long as it can. A company that starts with first names alone may switch when a second Maya joins, and that is one way a domain ends up with two formats.

How do you find a company’s email format?

You find a company’s email format by comparing addresses you know are real at that domain with the names of the people who own them. The method takes three steps:

  1. Collect a few verified addresses at the domain: from email signatures, the company’s site, press releases, or an enrichment API that returns verified work emails.
  2. Match each one to its owner’s name and write down the format it follows.
  3. Keep the majority, and the exceptions. The majority tells you the usual rule; the exceptions tell you how often a built address will miss.

The guide to finding emails by domain shows how to start from the domain and reach the right people at the company before any address is involved.

Does every employee follow the company email format?

Employees do not all follow the company email format, even at companies with a clear habit. In the real data above, all eight addresses at gong.io follow one format, but hubspot.com mixes three and stripe.com shows three different ones in four addresses, including a last name that does not match the profile, possibly a name change.

Verified addresses at gong.io, hubspot.com and stripe.com

  • 15Follow the most common format found at their domain
  • 4Follow another format
Out of 19 verified addresses at three domains, 4 do not follow the most common format found at their domain in this sample; for 3 of them, an address built from that format would have missed.

Exceptions come from ordinary events: a second employee with the same first name, a short alias, a nickname, a marriage, an acquired company that kept its old style. None of them shows in the format.

Why is a guessed email address risky?

A guessed email address is risky because nothing proves that it exists until a mail server or a verified source says so. On a domain that rejects unknown mailboxes, a check before sending can catch a wrong guess, though some servers limit or block such checks.

On a catch-all domain, the server accepts every address, so a guess passes the check whether the person exists or not. The message is then sent and lands in a catch-all mailbox, is dropped, or bounces later, and each email bounce costs the sender some reputation with the receiving servers.

Check yourselfAt acme.com, known addresses follow {first}.{last}. You build maya.chen@acme.com, and the mail server accepts it when you check. Is the address real?
Show the answer key
  1. Yes: the format matches and the server said yesOn an ordinary domain, an accepted address is a good sign. On a catch-all domain the server says yes to every address, so the answer proves nothing.
  2. Not necessarily: if the domain is catch-all, the server accepts any addressA catch-all server accepts mail for any name at the domain. The address could belong to nobody, or Maya could use another format.
  3. No: an address built from a format never worksBuilt addresses often work. The problem is that the format alone cannot tell you which ones do.

How do you get a verified address instead of a guess?

You get a verified address instead of a guess by looking it up from the person, not building it from the domain. BlitzAPI’s Find Work Email endpoint takes a LinkedIn profile URL and returns the person’s verified work email, or found: false with no record counted when it holds none; it does not assemble an address from the company’s format.

To start from a company rather than a person, Employee Finder lists its employees by function, level and country, and each profile it returns can go to Find Work Email in turn. That is the chain behind the real data on this page.

Sources and method

Written by
Antoine Blitz, Founder, BlitzAPI
Published
API calls run on

The calls ran on November 10, 2026 through the BlitzAPI MCP server, which calls the same endpoints; they are shown here as the equivalent REST requests. The profile URL in the second request is a placeholder: no person is named on this page.

Formats are read against the name on each profile. {f} and {l} stand for an initial; with a two-part last name, the format is read on the part the address uses.

Eight profiles per company is a small sample: it shows how formats behave, not the share of each format at these companies.

Questions people ask

How can I find a company's email address?

It depends on the address you need. A general contact address, such as info@ or hello@, is usually on the company's contact page. A specific employee's address follows the company email format, but a built address is a guess: look for one the person published, or use an enrichment service that returns verified addresses only.

What is an email permutator?

An email permutator is a tool that lists every address a name could have at a domain: maya.chen@, mchen@, maya@, chenm@ and so on. It saves typing, not uncertainty: each candidate still has to be checked, and on a catch-all domain the mail server accepts all of them, so the check proves nothing.

Can a company change its email format?

Yes. A company can adopt a new format for new hires, add aliases for existing staff, or move everyone to a new domain after a rebrand or an acquisition. Old addresses often keep working for a while as aliases, which is one reason a single company can show two or three formats at once.

With BlitzAPI

Put it to work

For builders

The calls behind the real data on this page, as REST requests. Send them with your API key, from any language or workflow tool.

List the US sales profiles at one company (Gong here; the same request runs for HubSpot and Stripe)

curl -X POST https://api.blitz-api.ai/v2/search/employee-finder \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_linkedin_url": "https://www.linkedin.com/company/gong-io",
    "country_code": ["US"],
    "job_function": ["Sales & Business Development"],
    "max_results": 8
  }'

API reference

Find the verified work email of each profile (one call per profile; the profile URL is a placeholder)

curl -X POST https://api.blitz-api.ai/v2/enrichment/email \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "person_linkedin_url": "https://www.linkedin.com/in/PROFILE_FROM_THE_LIST"
  }'

API reference

Data shouldn't be
the problem

Grab. Connect. Build.