Normalize the company website
A website URL is reduced to its company domain and checked before the job begins. Social-profile URLs and domains that cannot support email are not treated as ordinary company sites.
Email Find Tools
Enter a company domain to discover email addresses published across its public website. Control the result limit, include or exclude role accounts, and receive verification with every returned address.
Search a company domain without naming a person first. BillionVerify expands across public company pages until it reaches your limit or exhausts the available site evidence.
Your selected limit sets the maximum charge before the search begins.
Company Search is a domain-based email finder for the moment when you know the organization but not the right person. It reviews public pages on the company website, collects published addresses, attributes names when the page evidence supports them, verifies the final set, and returns no more than the limit you selected.
The tool can include named professional addresses and role-based mailboxes such as info, sales, support, careers, or press. Those two address types serve different workflows, so the result labels role accounts and records how a person name was obtained rather than presenting every email as a confirmed individual contact.
This page uses the customer-facing name Company Search. The underlying product is also called Domain Search because the required input is a company domain. It is not a company database, employee directory, LinkedIn finder, or guarantee that every employee email exists somewhere on the public web.
The search stays bounded by the company website, your role-account choice, and the maximum number of emails you are willing to receive.
A website URL is reduced to its company domain and checked before the job begins. Social-profile URLs and domains that cannot support email are not treated as ordinary company sites.
The search starts with existing evidence, then expands through public pages when needed. It collects visible and structured email signals without asking you to choose an internal crawl depth.
Each candidate is labeled as personal or role-based, paired with a name when supported, and verified before it enters the returned set. Verification is included in the company-search price.
The search returns from 1 to 200 emails, based on the maximum you choose. It stops when the limit is reached or public sources are exhausted and reports when additional discovered results were truncated.
The output separates the address itself from attribution and verification so teams can decide how each contact should be used.
The result contains the bounded set of addresses that passed the product’s final filtering and verification process, not every email-shaped string encountered on the site.
Named work emails are separated from shared mailboxes such as sales or support. You can exclude role accounts before the search so they do not consume the selected result limit.
When a contact name is available, the result identifies whether it came from structured data, nearby page text, inference, or an email-pattern guess. Pattern-inferred names should be reviewed before personalization.
The response distinguishes returned count from total found before filtering, reports whether the result was limited, and preserves verification status, reason, and deliverability fields.
A company website can publish useful contacts, but the page evidence behind each address determines how confidently it can be attributed and personalized.
Use the organization’s own website rather than a marketplace profile, social page, shortened URL, or parent company unless that is the entity you intend to research. The normalized domain defines the public source boundary for the search.
Select a maximum from 1 to 200 before submitting. At 5 credits per returned email, the limit is both a result boundary and a clear maximum charge.
Role accounts can be the correct destination for support, partnerships, careers, media, privacy, or procurement questions. They are less useful when the workflow requires a named decision-maker or personalized one-to-one outreach.
The include-role setting applies before billing. Excluding those addresses prevents them from consuming the result limit or the 5-credit returned-email charge.
A name printed beside an email on a team page is stronger attribution than a name inferred from the local part. The result preserves this difference through methods such as structured data, proximity, inference, and pattern.
Do not turn a pattern-inferred label into a personalized greeting without review. A shared mailbox, alias, inherited page, or common name can create an incorrect attribution even when the email itself is deliverable.
If you select one named person, Email Finder can search for that person’s best work address. If you already have a complete address, Email Verifier can focus on deliverability and risk. If many companies and people are already structured in rows, Bulk Email Finder can process the list as one job.
Company Search should remain an organization-level discovery step. It does not prove employment, title freshness, account ownership, consent, or that an address is the best destination for a particular message.
Use Company Search when organization-level discovery should happen before person-level targeting.
See which named and role-based contacts the company publishes before deciding whether an account deserves deeper manual research.
Locate public partnership, press, sales, support, or general contact mailboxes when the function matters more than a specific employee.
Review discovered addresses, attributed names, roles, and source methods to understand which public contact routes exist at an organization.
Use public company evidence to identify relevant people, then switch to Email Finder when one specific person needs a best-match work address.
The tools share verification infrastructure but begin with different known facts and deliver different result shapes.
| Tool | You provide | You receive | Use it when |
|---|---|---|---|
| Email Verifier | One complete email address | SMTP deliverability and risk signals | An address is known and needs verification before use |
| Email Finder | One person’s name and company domain | One verified best-match work email | A specific person is known but the address is missing |
| Bulk Email Finder | CSV rows with names and domains | Enriched CSV with one match per person | A structured list contains many named contacts |
| Company Search | Company domain, result limit, role-account choice | Verified public company addresses with attribution | The company is known but the relevant people or mailboxes are not |
Public discovery provides useful contact evidence, but several conclusions remain outside the tool’s technical scope.
Company Search returns addresses supported by public company evidence and verification. Employees whose addresses are not published or inferable may not appear.
A page can be stale, an address can be retained after a role change, and an attributed name can be inferred. Review freshness before relying on identity details.
Deliverability and attribution are separate. Role accounts, aliases, catch-all domains, and forwarding addresses can receive mail without proving that one person controls the inbox.
A company publishing an address does not remove the need for relevance, suppression checks, consent analysis, and the sender’s own regional contact rules.
These standards explain the technical structures Company Search relies on when interpreting public organization data and email delivery signals.
Defines SMTP delivery and mail exchanger lookup behavior used during final address verification.
Defines the mailbox address structure used when extracting and normalizing company email addresses.
Documents structured organization properties, URLs, contact points, and other data a company may publish on its website.
Documents structured person properties that can support stronger public name-to-email attribution.
Once the domain search is complete, choose the next tool based on whether you have a named person, a known email, or a list.
Search for one named person’s best work email at the company.
Process many named people and company domains in a CSV.
Inspect SMTP deliverability and risk when a complete address is already known.
Understand shared function mailboxes such as info, sales, support, and billing before using them in a workflow.
Enter the company’s official domain, choose a maximum result count, and decide whether to include role accounts. BillionVerify searches public company pages, attributes names where supported, verifies the final set, and returns up to your limit.
Yes. Company Search is the customer-facing page name, while Domain Search describes the product’s required input. Both refer to searching one company domain for a bounded set of verified public email addresses.
The search costs 5 credits for each returned email, up to the maximum you select. If no verified addresses are returned, the search costs zero. Included verification is not charged again.
Yes. Turn off role-based addresses before submitting. The filter applies before billing, so excluded role accounts do not consume your result limit or returned-email credits.
No. It discovers addresses supported by public company sources and the product’s evidence process. It is not a private employee directory and cannot guarantee coverage of people whose emails are not published or reliably inferable.
It explains how a person name was connected to an address: structured data, nearby page text, inference, or an email-pattern guess. Pattern-inferred names are weaker and should be reviewed before personalization.
The result stops at the maximum you selected and reports that the available set was truncated. It also distinguishes returned count from the total found before filtering when that information is available.
Control the result count, decide whether role accounts belong, and keep attribution strength visible in every returned contact.
5 credits per returned email · Verification included · No returned emails means no charge