How to Find a Company's Email Format (Pattern) by Domain

To find a company’s email format, look at addresses the company has published (press pages, support pages, documentation), compare patterns, then confirm with an email pattern tool that reports the format, mail server and catch-all status for the domain. The goal is the pattern, such as first.last, not a guessed individual address you have never validated.

Why the pattern matters

Most organisations assign addresses by a consistent rule. If you know that [email protected] follows {first}.{last}, you know how colleagues’ addresses are likely built. But a pattern is a hypothesis. Staff with common names, nicknames, hyphens or duplicates often break it, and some companies use different rules for different teams.

Pattern	Example for Jane Doe
{first}.{last}	[email protected]
{first}{last}	[email protected]
{f}{last}	[email protected]
{first}	[email protected]
{first}_{last}	[email protected]
{last}.{first}	[email protected]

Manual ways to find the pattern

1. Public contact pages. Press, investor relations and support pages sometimes list named addresses.
2. Documents. PDFs, security reports and conference programmes often carry names and emails.
3. The company’s own policies. A privacy policy usually gives a role address such as privacy@, which is generic, but confirms the domain.
4. Public technical contacts. Some documentation sites list maintainers with addresses.

Always stick to material the company published itself. Do not scrape or buy lists of personal addresses unless you have a lawful basis.

What an email pattern tool returns

BusinessMCP’s company lookup page describes an email pattern tool that returns the company’s address format, such as {first}.{last}, together with the MX record and catch-all status. Its API reference lists response fields including pattern, confidence, validated, example, accepts_mail, catch_all and mail_checked_at, and says validated reflects whether a live mailbox check confirmed the pattern. It is priced at $0.01 per call, charged only when a pattern is known, per the data API page.

The BusinessMCP data API page covers it alongside company lookup. The reference states the endpoint returns company-level data only, with no person returned. That is a useful property: you get the rule, and it is up to you, with a lawful basis, to decide whether and how to use it.

Key takeaway: a pattern with a confidence score and a catch-all flag is more useful than a bare guess, because the flags tell you how far to trust it.

Reading the fields

• accepts_mail. Whether the domain’s mail setup accepts mail at all. If not, the domain is not a valid target.
• catch_all. If true, the server accepts anything, so you cannot confirm a specific mailbox exists by testing. Treat any guess as unverified.
• validated. Whether a live mailbox check supported the pattern. Higher assurance, but not a guarantee for every employee.
• confidence. A score from the tool. Use it to rank, not as a probability you can quote.
• mail_checked_at. When the check ran. Mail setups change.

From pattern to address

Suppose the pattern is {first}.{last} and you have been given a contact’s name by the person themselves, say at an event. Building first.last@domain is a reasonable guess. Then:

1. Check the domain is not catch-all, or accept that you cannot verify.
2. Send a first message that is relevant, short and easy to decline.
3. Watch for bounces and learn from them; a bounce is a signal the pattern is wrong for that person.
4. Do not keep trying variants. Repeated attempts at guessed addresses look like spam and harm your sending reputation.

For deliverability checks on your own domain rather than theirs, BusinessMCP also lists an email deliverability checker among its free tools.

Compliance points

Outreach rules are about the recipient and your practices, not just the tool. In the US, the FTC’s CAN-SPAM guidance covers commercial email requirements such as accurate headers and an opt-out. In the EU and UK, email marketing to individuals is governed by consent rules, with different treatment for corporate subscribers depending on the country. Role addresses are not exempt from every rule. This is general information, not legal advice. Take advice before you run a campaign in a given jurisdiction.

BusinessMCP’s pages add its own boundary: the people tools are separate, require accepted terms, and exclude people in the EU, EEA, UK, Switzerland and certain US states. That is a vendor policy; your own legal obligations are a separate matter.

Common mistakes

• Assuming one pattern applies to everyone in a large firm.
• Treating a catch-all domain’s acceptance as proof a mailbox exists.
• Sending to a big batch of unverified guesses.
• Ignoring unsubscribe and identification requirements.
• Using the pattern to reach people who clearly do not want contact.

Where this fits

The pattern is one small piece of prospecting. You still need to decide who is worth contacting, which comes from firmographic fit and a clear process; see company lookup for sales prospecting. Start from a verified domain with a company lookup by domain, and take it from there.

A short worked example

Imagine you want to write to someone at a mid-sized software company after meeting them at a conference, where they gave you their name and said you could follow up. You run the company’s domain through a pattern tool. It returns {first}.{last} with a validated flag and no catch-all. You build the address, send a short, relevant note that identifies you and explains why you are writing, and include a simple way to decline. If it bounces, you look for a published address or ask for the correct one rather than cycling through variants.

Now imagine the same exercise with a company whose domain is catch-all. The tool returns a pattern but warns that mailbox checks prove nothing. You have no way to confirm the address before sending, so the right step is to find the person through another route, such as a mutual contact or a contact form, instead of hoping.

Alternatives to guessing

• Contact forms. Slower, but they reach someone who is expecting them.
• Role addresses. sales@ or partnerships@ reach a team, not a person, and are often the intended channel for business enquiries.
• Warm introductions. Still the highest-response route for important accounts.
• Social platforms. A direct message on a professional network sidesteps email guessing altogether, subject to that platform’s rules.

Each has a cost in speed. In return you avoid bounces, reputation damage and awkward replies from people who never gave you their address.