# Email Verifier & Finder - Validate + Find Emails (`piposlab/email-verifier-finder`) Actor

Verify email deliverability (syntax, MX, role, disposable) and find likely emails from a name and domain. Bulk, fast, no API key.

- **URL**: https://apify.com/piposlab/email-verifier-finder.md
- **Developed by:** [Alejandro Bufarini](https://apify.com/piposlab) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 8 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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?

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

## Email Verifier & Finder - Validate + Find Emails

Two jobs in one actor, with no API key:

1. **Verify** a list of emails - checks syntax, looks up the domain's MX records, and flags role accounts (info@, sales@) and disposable domains. Returns a clear status: `valid`, `risky`, or `invalid`, with the reason.
2. **Find** likely emails from a person's name and company domain - generates and ranks the common patterns (`jane.doe@`, `jdoe@`, `jane@`...) and confirms the domain accepts mail.
3. **Discover** published emails on a company's website (homepage, /contact, /about).

### Modes & input

| Mode | Input | Returns |
|------|-------|---------|
| `verify` | `emails: ["a@x.com", ...]` | status, syntaxValid, mxFound, isRoleAccount, isDisposable, reason, confidence |
| `find` | `people: [{fullName, domain}]` | bestGuess, ranked candidates, mxFound |
| `discover` | `domains: ["x.com", ...]` | emailsFound\[], count |

### Output (verify example)

```json
{
  "email": "jane.doe@example.com",
  "status": "valid",
  "syntaxValid": true,
  "domain": "example.com",
  "mxFound": true,
  "mxHost": "aspmx.l.google.com",
  "isRoleAccount": false,
  "isDisposable": false,
  "confidence": "high",
  "reason": "mx_ok"
}
```

### How verification works (honest)

This actor validates at the **DNS / MX + heuristic** level: syntax, whether the domain can receive mail, and whether the address is a role or disposable account. It does **not** open an SMTP mailbox handshake (outbound port 25 is blocked on cloud infrastructure, and aggressive SMTP probing gets sender IPs blacklisted). That makes it fast, reliable, and safe for bulk lists. Treat `valid` as "deliverable domain, well-formed address", not "mailbox confirmed to exist".

Clean for lead-gen pipelines: feed it the output of a scraper and get a deduplicated, status-tagged email list.

# Actor input Schema

## `mode` (type: `string`):

What to do.

## `emails` (type: `array`):

List of email addresses to validate.

## `people` (type: `array`):

Objects like {"fullName":"Jane Doe","domain":"example.com"} to generate likely emails for.

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

Domains to scan for published contact emails (homepage, /contact, /about).

## `maxItems` (type: `integer`):

Cap on records processed.

## Actor input object example

```json
{
  "mode": "verify",
  "emails": [
    "jane.doe@example.com"
  ],
  "people": [
    {
      "fullName": "Jane Doe",
      "domain": "example.com"
    }
  ],
  "maxItems": 1000
}
```

# 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 = {
    "emails": [
        "jane.doe@example.com"
    ],
    "people": [
        {
            "fullName": "Jane Doe",
            "domain": "example.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("piposlab/email-verifier-finder").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 = {
    "emails": ["jane.doe@example.com"],
    "people": [{
            "fullName": "Jane Doe",
            "domain": "example.com",
        }],
}

# Run the Actor and wait for it to finish
run = client.actor("piposlab/email-verifier-finder").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 '{
  "emails": [
    "jane.doe@example.com"
  ],
  "people": [
    {
      "fullName": "Jane Doe",
      "domain": "example.com"
    }
  ]
}' |
apify call piposlab/email-verifier-finder --silent --output-dataset

```

## MCP server setup

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

```

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/JS77PmWbRQ4dEe8AJ/builds/VgcczwH4T0OAr0h5V/openapi.json