# Bulk Domain Email Finder — All Verified Emails at a Company (`qualifyops/domain-email-finder-verified`) Actor

Domain email finder: enter a company domain, get every verified deliverable email — published contacts plus role mailboxes (info@, sales@, contact@) — SMTP-checked, catch-all excluded, no bounces. Build B2B lead lists for cold email and sales prospecting. Pay only per verified email found.

- **URL**: https://apify.com/qualifyops/domain-email-finder-verified.md
- **Developed by:** [QualifyOps](https://apify.com/qualifyops) (community)
- **Categories:** Lead generation, Business
- **Stats:** 4 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 verified email founds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Domain Email Finder — Verified Company Emails

**You give:** company domains — `stripe.com`, `https://shopify.com/about`, anything; URLs are normalized.
**You get:** every **verified, deliverable email address** publicly reachable at each domain — addresses the company publishes on its own site, plus common role mailboxes (`info@`, `contact@`, `sales@`, …), each one confirmed by a live SMTP deliverability check.
**You pay:** **only per verified email found — $0.008.** Domains where nothing verifies are **free**.

No name needed. No LinkedIn, no protected sources. This is the domain-level sibling of [Email Finder + Verifier](https://apify.com/qualifyops/email-finder-verified) (which finds one specific person's email from a name + domain).

***

#### Why "verified" is the whole point

A list of `info@company.com` guesses is worthless if half of them bounce — your sender reputation eats the damage. Every `FOUND` row here has been through:

> site scan / role candidates → syntax → MX record → **live SMTP mailbox check** → catch-all detection → confidence score

Only an address a real mail server **accepts**, that is **not catch-all**, at **confidence ≥ 0.80**, is returned and billed. Everything else is a free `NOT_FOUND` with the honest reason.

#### How it works

1. **Normalize** each domain (strip `https://`, `www.`, paths).
2. **MX pre-filter (free):** domains with no mail server return `NOT_FOUND` immediately — no charge.
3. **Site scan** (`siteScan`, on by default): fetch the homepage, `/contact` and `/about`; addresses the company actually publishes are tested **first** — those are real, not guesses. Off-domain addresses (e.g. a published gmail) are excluded.
4. **Role mailboxes** (`includeRoleEmails`, on by default): `info@`, `contact@`, `hello@`, `sales@`, `support@`, `hi@`, `office@`, `team@`, `admin@`, `enquiries@`.
5. **One batched deliverability check:** all candidates across all domains go to a proven Apify Store validator with real SMTP egress in a single call.
6. **Emit winners:** each deliverable, non-catch-all, confident address becomes one `FOUND` row (up to `maxEmailsPerDomain`). **You are charged only for FOUND rows.**

#### What each row gives you

| Column | Meaning |
|---|---|
| `action` | **FOUND** (verified deliverable) or **NOT\_FOUND** (with reason) |
| `domain` | The normalized company domain |
| `verified_email` | The deliverable address — only on FOUND |
| `source` | `published` (found on the company site) or `role` (standard mailbox) |
| `confidence` | 0–1 deliverability confidence |
| `reason` | On NOT\_FOUND: `no_mx` / `catch_all_domain` / `all_rejected` / `verifier_unavailable` |

#### Honest by design

Public business-contact data only — published pages and standard business mailboxes; nothing gated, scraped from social networks, or guessed silently. Catch-all domains are excluded rather than sold as verified. You are responsible for compliant outreach in your jurisdiction (CAN-SPAM / GDPR / local law: identify yourself, honour unsubscribes). B2B research tool, not a licence to spam.

#### Use with

- **[Email Finder + Verifier](https://apify.com/qualifyops/email-finder-verified)** — when you need one specific person (name + domain → their verified email).
- **Free [Email Pattern Finder](https://qualifyops.pages.dev/tools/email-pattern-finder)** — work out a company's likely email format before you buy anything.

# Actor input Schema

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

Company domains or website URLs, e.g. \["stripe.com", "https://shopify.com"]. Full URLs are normalized.

## `includeRoleEmails` (type: `boolean`):

Also test common business mailboxes (info@, contact@, sales@, …). Off = only addresses published on the company site.

## `siteScan` (type: `boolean`):

Fetch the homepage, /contact and /about and promote addresses the company actually publishes.

## `maxEmailsPerDomain` (type: `integer`):

Stop after this many verified emails per domain (caps your spend). Start small.

## `verifierActorId` (type: `string`):

Store validator used for the SMTP check. Default is a proven high-volume validator.

## `requestTimeoutSecs` (type: `integer`):

How long to wait for each company web page during the site scan.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "stripe.com"
  ],
  "includeRoleEmails": true,
  "siteScan": true,
  "maxEmailsPerDomain": 3,
  "verifierActorId": "michael.g/email-verifier-validator",
  "requestTimeoutSecs": 10
}
```

# 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": [
        "apify.com",
        "stripe.com"
    ],
    "maxEmailsPerDomain": 3,
    "requestTimeoutSecs": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("qualifyops/domain-email-finder-verified").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": [
        "apify.com",
        "stripe.com",
    ],
    "maxEmailsPerDomain": 3,
    "requestTimeoutSecs": 10,
}

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

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "apify.com",
    "stripe.com"
  ],
  "maxEmailsPerDomain": 3,
  "requestTimeoutSecs": 10
}' |
apify call qualifyops/domain-email-finder-verified --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=qualifyops/domain-email-finder-verified",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/sNs8eFmf5onbtYJQA/builds/V8MDfE5mgrVKREZ1w/openapi.json