Website Email & Phone Finder

Pricing

Rating

Developer

Actor stats

Categories

Share

👁 Website Email & Phone Finder Actor

Find business emails and phone numbers for any list of domains. Built for sales teams, recruiters, and marketers who need to enrich website lists with real contact info at scale.

Submit your domains, get back structured contact data per domain, including the original input URL preserved for easy mapping in your workflow.

Key features

• Email extraction from publicly available data (e.g. c******@company.com, s****@business.org)
• Phone number extraction in international E.164 format where possible
• Source links included with every result so you can verify where the data came from
• Original input URL preserved as inputUrl in the output, making 1:1 row matching trivial in Zapier, n8n, Make, or your own scripts
• Smart filtering removes duplicates and skips noise like noreply@ and no-reply@
• Bulk processing for hundreds or thousands of domains in a single run
• Flexible input accepts bare domains, full URLs, or URLs with paths and query strings

Use cases

1. Sales prospecting: turn a target account list into a working contact list
2. Lead generation: enrich domain lists with email and phone data for outreach
3. Recruitment: find HR or careers contacts at sourcing targets
4. Marketing: build niche contact lists for cold email or partnerships
5. CRM enrichment: fill in missing data on existing accounts in HubSpot, Salesforce, Pipedrive
6. Business development: locate decision-maker contacts for partnership outreach
7. Competitive research: map the contact networks of competitors and adjacent companies
8. Event outreach: gather attendee or sponsor contacts for webinars and conferences

Input

You can pass any of the following formats. The actor cleans them automatically:

• Bare domain: example.com
• With protocol: https://example.com
• With subdomain: https://www.example.com
• With path or query string: https://example.com/contact?ref=abc

Example input

{
"domains":[
"example.com",
"https://company.org/contact",
"https://www.business.net/about"
]
}

Output

Each result row in the dataset contains the following fields:

Example output

[
{
"inputUrl":"https://example.com/contact",
"domain":"example.com",
"emails":[
"c******@example.com",
"s******@example.com"
],
"phoneNumbers":[
"+155*****567"
],
"links":[
"https://example.com/contact",
"https://example.com/about"
]
},
{
"inputUrl":"company.org",
"domain":"company.org",
"emails":[
"h****@company.org"
],
"phoneNumbers":[],
"links":[
"https://company.org/team"
]
}
]

Tabular view

Pricing

Pay-per-result: $20 per 1,000 results. You only pay for domains where contact info is actually found.

Free plan

On the Apify Free plan, the actor processes 1 domain per run and returns partially masked emails and phone numbers (e.g. c******@example.com, +155*****567) so you can verify the actor works before upgrading.

Upgrade your plan to unlock all domains and full unmasked results.

How it works

1. Reads your list of input domains and URLs
2. Normalizes each entry to a base domain
3. Looks up publicly available contact information associated with each domain
4. Extracts emails and phone numbers from the collected data
5. Validates and deduplicates contacts, filters out noise
6. Returns results to the Apify dataset with the original input URL preserved

Frequently asked questions

Why are some domains returning no contacts?

Not every website has publicly available contact info. Domains with strong privacy controls or minimal web presence may return empty results.

Are the phone numbers verified?

Phone numbers are extracted from publicly available data and normalized. They are not actively dialed for verification, so we recommend validating before use in critical workflows.

Can I use this with Zapier, Make, or n8n?

Yes. Use the standard Apify integration in any of these platforms. The inputUrl field is included in every result specifically to make 1:1 matching with your input rows easy in automated workflows.

What about GDPR and data privacy?

This actor only collects contact info that is already publicly available. You are responsible for ensuring your use of this data complies with GDPR, CAN-SPAM, and any other regulations in your jurisdiction.

Can I target specific subdomains or paths?

The actor normalizes inputs to the base domain for lookup, but content from subdomains can still appear in results. Pass the full URL if you want to preserve it in the inputUrl output field.

Support

If you run into any issues, have suggestions, or need help integrating this actor into your workflow, please open a ticket in the Issues tab on the actor page. Our team monitors it actively and responds promptly.