Domain → Page → Contacts · the email comes after the person
How to find emails by domain without getting the wrong people
The short answer
To find emails by domain without getting the wrong people, don't ask for every address filed under that domain. Resolve the domain to the company's LinkedIn page, list the people whose current job is attached to it, keep the ones you need, then find each person's work email. The email then comes back with the company page it belongs to.
On this page6 sections
Type a domain into an email finder and you get a list of addresses. Searching email by domain feels like the shortest path to the people at a company. But a domain search can only return what a database has filed under that domain, and filing people under a domain is exactly where contact data goes wrong, as the guide on how to find employees of a company from its domain explains.
This page applies the same reasoning to emails: what happens when you search emails by domain, why some of those addresses bounce or reach the wrong people, and the order that avoids both.
What does a search for emails by domain really return?
Every address the database has attached to that domain, whoever the person behind it is. That includes the people who work there now, but also three other kinds of rows:
- People from another company. Any LinkedIn company page can write any domain in its website field. Sabena, a Belgian airline that stopped flying in 2001, gives a microsoft.com page as its website, so its former pilots can be filed under microsoft.com.
- People who left. Someone who founded their own company keeps being filed under their old employer’s domain, now with a title of Founder or CEO.
- Addresses nobody ever had. When a tool builds an address from a name and the domain’s email pattern, it builds one for every row, including the rows that never worked there.
- a•••••••@microsoft.comWrong companyAirline Pilot · SabenaListed under microsoft.com because the Sabena page gives that domain. An address built from the name and the domain’s pattern: it never existed.
- c•••••@loreal.comFormer employeeFounder & CEO · her own companyLeft L’Oréal years ago and still filed under its domain. The address was closed when she left.
- s•••••••@figma.comWorks thereDirector, Enterprise Sales · FigmaA current job on the Figma page. The address belongs to that job.
None of this shows in the list. The three addresses look alike: same domain, same format, same confidence.
An email search by domain inherits every mistake of the domain search behind it.
Why do emails found by domain bounce or reach the wrong people?
Because the email was found before anyone checked who the person is. An address at the right domain can still belong to the wrong person: a former employee whose mailbox was closed, a pilot from another company with an address built from a pattern. The first bounces and hurts your sender reputation, as the email bounce page explains. The second may not bounce at all on a catch-all domain, which accepts every address, and then reaches nobody.
The fix is not a better email finder. It is a different order.
How do you find emails by domain, step by step?
Settle the company, then the people, then the emails. Four steps:
- Resolve the domain to its company page. Domain to LinkedIn returns the LinkedIn page the domain matches and lists the other pages that claim the same domain. Check the name against your account before going further.
- List the people who work there now. Employee Finder takes the page and returns the people whose current job is attached to it, filtered by title, level, function or location.
- Keep the people you need. This is where your persona applies: the roles, the seniority, the region.
- Find each person’s work email. Email Enrichment takes the person’s LinkedIn URL and returns their work email, with the company page of the job it belongs to.
- Domainfigma.com
- Domain to LinkedInCompany pageFigma
- Employee FinderPerson, current jobDirector, Enterprise Sales
- Email EnrichmentWork emails•••••••@figma.com
- Company page
- linkedin.com/company/figma
- Email domain
- figma.com
- Mail servers
The email comes back with
- Definition Work email also called business email address
- The address a person gets from their employer, on the company's own domain, rather than a personal address.
PreciselyA work email uses the employer's domain (name@company.com) and is hosted by the company's mail provider; it usually stops working after the person leaves. B2B data providers tell it apart from personal addresses on free providers, and it should be verified before use, because a job change turns it into a bounce.
That last detail matters. Because the email is tied to a job, and the job to a company page, you can check that the address belongs to the account you asked for. A domain search gives you an address and a domain; this gives you an address, a person and a company.
How to find email addresses for a company that uses another domain?
Check which domain it sends email from first: the email domain is not always the website. A company can publish its website on one domain and send email from another. Microsoft’s LinkedIn page lists news.microsoft.com as its website, and its email domain is microsoft.com. A search that takes the website’s domain looks for addresses that don’t exist.
The company page settles this too. From the page, BlitzAPI LinkedIn URL to Domain returns the email domain the company uses for its addresses, which is the domain an email search actually needs. The addresses themselves follow the company’s format:
- Definition Company email format also called email pattern
- The rule a company follows to build its employees' addresses, such as first name, a dot, last name, at the company domain.
PreciselyAn email format, or pattern, is the template a domain uses for its addresses: {first}.{last}@domain, {f}{last}@domain, {first}@domain and so on. It is inferred from verified addresses at the domain. An address built from the pattern is still a guess until it is verified, and a catch-all domain accepts any guess.
A format tells you how an address would be written, not whether the person behind it works there. That is why the person comes first.
For builders
Everything above runs on four endpoints. This part shows the two calls specific to emails, with a real run.
How do you find work emails with the API?
A person's LinkedIn URL in, their work email out, with the company page of the job it belongs to.
Send
person_linkedin_url- The person you found at the second step, from Employee Finder or Waterfall ICP.
Read
found, email- The work email, or found: false.
all_emails[]- Each address with company_linkedin_url and email_domain: the job it belongs to.
mx- The mail servers of the email domain.
A company page in, the domain the company uses for email out.
Send
company_linkedin_url- The page you validated at the first step.
Read
found, email_domain- The email domain, which can differ from the website domain.
Each email or domain found is one record; plans and rate limits are on the BlitzAPI pricing page.
A real run
On November 10, 2026, we took a Director, Enterprise Sales found among Figma’s current employees and asked for the work email. The response, with the address masked:
{
"found": true,
"email": "s•••••••@figma.com",
"all_emails": [
{
"email": "s•••••••@figma.com",
"company_linkedin_url": "https://www.linkedin.com/company/figma",
"email_domain": "figma.com"
}
],
"mx": [{ "priority": 1, "host": "aspmx.l.google.com" }]
}And for Microsoft’s page, the email domain:
{ "found": true, "email_domain": "microsoft.com" }Before you ship
- Find the person before the email: no address for a row you have not tied to a current job at the right company page.
- Check all_emails[].company_linkedin_url against the account before you send.
- Use the email domain from the page, not the website domain, when you need a domain for email.
- Building addresses from a name and a pattern for people you have not checked.
Sources and method
- Written by
- The BlitzAPI team
- Published
- API calls run on
- Find Work Email, BlitzAPI API reference
- LinkedIn URL to Domain, BlitzAPI API reference
- Domain to LinkedIn URL, BlitzAPI API reference
The three addresses in the first diagram are illustrative and masked; the cases behind them come from matching tests run on October 11, 2026, described in the guide on finding employees of a company from its domain.
The BlitzAPI team ran the calls in the second diagram and in the builders section on November 10, 2026, on Figma. The person is described by job title only and the address is masked.