# Company Email Finder & Verifier (`antishock/company-email-finder-verifier`) Actor

Find real, published contact emails on a company's own website (homepage, imprint, contact, team, careers pages). Classifies each email as generic or personal, checks MX validity and flags disposable domains. Specialised inside the E-Mail/Leads market, not tied to a location lookup.

- **URL**: https://apify.com/antishock/company-email-finder-verifier.md
- **Developed by:** [Ryan Zinburg](https://apify.com/antishock) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 result exporteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Company Email Finder & Verifier - Find Real Contact Emails by Domain

Give this actor one or more company **domains** and it crawls the homepage plus linked
imprint/contact/team/career pages to find real, published email addresses - deduplicated,
classified as generic (info@, support@, sales@ ...) or personal, and checked for a valid
mail server (MX record) and known disposable domains.

### What you get per email

| Field | Example |
|---|---|
| `domain` | example.com |
| `email` | info@example.com |
| `emailType` | generic or personal |
| `onDomain` | true |
| `sourceUrl` | https://example.com/contact |
| `mxValid` | true |
| `isDisposable` | false |
| `scrapedAt` | ISO timestamp |

### Input

- **domains** - list of company domains or URLs, e.g. `["example.com", "https://other.org"]`
- **maxPagesPerDomain** - homepage plus up to this many linked contact-style pages (default 6)
- **verifyMx** - check that the email's domain has a working mail server (default on)
- **includeGenericAddresses** - include info@/support@-style addresses, not just named contacts (default on)
- **includeOffDomainEmails** - by default only emails on the company's own domain are kept, since
  pages often embed third-party widgets (chat, ads, analytics) with their own example addresses.
  Turn this on to also see off-domain matches, flagged with `onDomain: false`.

### Example input

```json
{
  "domains": ["example.com", "another-company.de"],
  "maxPagesPerDomain": 6,
  "verifyMx": true
}
```

### Use cases

- **Sales and lead generation** - find a way in before cold outreach
- **Recruiting** - locate a company's HR or careers contact
- **Journalism and research** - find a press contact fast
- **Partnership and vendor outreach** - find the right department
- **Data enrichment** - add verified contact emails to an existing company list
- **Link building and PR** - find who to pitch at a target site

### Why this needs scraping, not a free API

There is no public API that returns "the contact email of company X". Contact details live
scattered across each company's own website - homepage footer, imprint, team page, careers
page - in whatever format that company chose, sometimes deliberately obfuscated
("info (at) example dot com") to dodge simple crawlers. Finding and normalising that requires
visiting the actual pages, not querying a structured endpoint.

### Notes

- This only reports emails that are actually published somewhere on the site - it never
  invents or guesses personal addresses.
- `mxValid: false` usually means a typo or a domain that no longer receives mail.
- SMTP-level deliverability (does the specific mailbox exist) is out of scope: the Apify
  platform blocks outbound port 25, so no actor running here can verify that reliably. Use
  the separate `email-verifier` actor if you need per-address verification you can feed in
  yourself from a reachable server.

# Actor input Schema

## `domains` (type: `array`):

Company domains or URLs to search for published contact emails.

## `maxPagesPerDomain` (type: `integer`):

Homepage plus up to this many linked contact-style pages.

## `verifyMx` (type: `boolean`):

Check that each email's domain has a working mail server.

## `includeGenericAddresses` (type: `boolean`):

Include info@/support@/sales@-style addresses, not just named contacts.

## `includeOffDomainEmails` (type: `boolean`):

Also keep emails whose domain does not match the scanned company (usually third-party widgets, not leads). Off by default.

## Actor input object example

```json
{
  "domains": [
    "mozilla.org",
    "eff.org"
  ],
  "maxPagesPerDomain": 6,
  "verifyMx": true,
  "includeGenericAddresses": true,
  "includeOffDomainEmails": false
}
```

# Actor output Schema

## `results` (type: `string`):

Scraped records in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        "mozilla.org",
        "eff.org"
    ],
    "maxPagesPerDomain": 6,
    "verifyMx": true,
    "includeGenericAddresses": true,
    "includeOffDomainEmails": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("antishock/company-email-finder-verifier").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "domains": [
        "mozilla.org",
        "eff.org",
    ],
    "maxPagesPerDomain": 6,
    "verifyMx": True,
    "includeGenericAddresses": True,
    "includeOffDomainEmails": False,
}

# Run the Actor and wait for it to finish
run = client.actor("antishock/company-email-finder-verifier").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    "mozilla.org",
    "eff.org"
  ],
  "maxPagesPerDomain": 6,
  "verifyMx": true,
  "includeGenericAddresses": true,
  "includeOffDomainEmails": false
}' |
apify call antishock/company-email-finder-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,antishock/company-email-finder-verifier"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lWaPcdgdYhByxeKzM/builds/Pz3THo2aJ2ena6amy/openapi.json