# Email Verifier — syntax + MX + disposable/role heuristics (`vhsgreed/email-verifier-fresh`) Actor

Bulk email verification and list cleaning: syntax, DNS MX, disposable-domain and role-account detection, optional SMTP RCPT probe with catch-all detection, 0-100 deliverability score. Pay per decisive result, $0.125 per 1,000. No third-party validation service, no email retention.

- **URL**: https://apify.com/vhsgreed/email-verifier-fresh.md
- **Developed by:** [Karl Sundström](https://apify.com/vhsgreed) (community)
- **Categories:**
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.10 / 1,000 email verifieds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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: deliverability, catch-all and risk score

Bulk email verification for list cleaning before a campaign: syntax check, DNS MX lookup, disposable-domain and role-account detection, an optional SMTP RCPT probe with catch-all detection, and a 0-100 deliverability score per address. No third-party validation services in the chain. No email retention: addresses exist only for the duration of the run.

### Pricing

You are charged per decisive result, not per address scanned. Unknown and catch-all-uncertain outcomes are free.

| Item | Price |
| --- | --- |
| Run start | $0.002 |
| Decisive result (valid, invalid or disposable) | $0.00125 ($1.25 per 1,000) |
| Unknown or catch-all-uncertain result | $0 |
| Max spend per run | $5 |

### Comparison

| Feature | Email Verifier (this actor) | BounceVerify | Email Verifier & Validator | Million Verifier wrapper |
| --- | --- | --- | --- | --- |
| Price | $1.25 / 1k decisive results | $0.89 / 1k emails | $1 / 1k emails | $1 / 1k decisive results |
| Pay per uncertain result | No (unknown results are free) | Yes | Yes | No (decisive only) |
| Catch-all detection | Yes (random-mailbox probe) | Yes | Yes | Yes |
| Risk score (0-100) | Yes | No | No | No |
| Disposable-domain detection | Yes | Yes | Yes | Yes |
| Role-account detection | Yes | Yes | Yes | Yes |
| SMTP RCPT probe | Optional, runs in your run | Service-side | Service-side | Third-party service |
| Third-party verification service in the chain | None | None | None | Million Verifier |
| Email retention | Not retained | Per provider policy | Per provider policy | Retained by Million Verifier |
| Per-run spend cap | $5 | Per-provider billing | Per-provider billing | Per-provider billing |

This actor runs its own DNS and SMTP logic inside your Apify run. Addresses are not sent to any verification service and are not stored after the run.

### What data you get

| Field | Description |
| --- | --- |
| email | The address checked (lowercased, trimmed) |
| status | good, risky, bad or unknown |
| score | 0-100 deliverability score |
| valid | Derived boolean (syntax + MX pass, nothing invalidates) |
| syntaxValid | Syntax-level result |
| mxFound | DNS MX record present |
| disposable | Disposable-domain heuristic hit |
| roleAccount | Role-account heuristic hit (info@, admin@, ...) |
| freeProvider | Known consumer mailbox provider |
| catchAll | True when the domain accepts any mailbox (probe mode) |
| smtpResult | valid, risky, unknown, invalid or null (probe mode) |
| technicalReason | SMTP reply code with plain-text DSN meaning |
| didYouMean | Suggested correction for a likely domain typo |
| reason | Human-readable summary of the verdict |

### How to use

1. Add the actor to your Apify account and click Run.
2. Paste addresses into `emails`. Duplicates are removed automatically and you are charged once per unique address.
3. Optionally enable `smtpProbe` for mailbox-level checks.
4. Export results as JSON, CSV or Excel.

### Input

```json
{
  "emails": ["karl@example.se", "info@example.org"],
  "smtpProbe": false
}
```

### Limitations

These are plain facts about how the checks behave:

- Datacenter IPs receive greylisting; some servers return unknown rather than a verdict. The actor reports unknown and does not charge for it.
- On catch-all (accept-all) domains a 250 reply does not prove the mailbox exists. Such results are marked catchAll=true and reported as risky, and are not charged.
- The disposable-domain list is a static snapshot of the most common disposable providers, not an exhaustive one. disposable=true is reliable; disposable=false does not guarantee a non-disposable domain.
- Some servers block or rate-limit port 25 probes from datacenter ranges. When the probe cannot connect, the actor reports smtpResult=null with a reason and falls back to DNS-layer checks.
- Without the probe, the verdict rests on syntax, MX and heuristics. It does not confirm the mailbox exists.
- did\_you\_mean suggestions come from a small list of common providers plus domains observed in the run, using a levenshtein distance of 2 or less.

# Actor input Schema

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

Email addresses to verify. Duplicates are removed automatically; you are charged once per unique address.

## `smtpProbe` (type: `boolean`):

Attempt an outbound port-25 SMTP RCPT TO probe, including a random non-existent mailbox per domain to detect catch-all (accept-all) servers. Datacenter IPs receive greylisting; some servers return unknown rather than a verdict.

## Actor input object example

```json
{
  "smtpProbe": false
}
```

# Actor output Schema

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

Dataset of per-email results. Fields: email, status, score, valid, syntaxValid, mxFound, disposable, roleAccount, freeProvider, catchAll, smtpResult, technicalReason, didYouMean, reason.

## `runStats` (type: `string`):

Key-value store entry OUTPUT\_STATS: counts of good/risky/bad/unknown, duplicates dropped, SMTP probe and catch-all outcome for this run.

## `runView` (type: `string`):

Inspect this run, its logs and storages in Apify Console.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("vhsgreed/email-verifier-fresh").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("vhsgreed/email-verifier-fresh").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 '{}' |
apify call vhsgreed/email-verifier-fresh --silent --output-dataset

```

## MCP server setup

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

```

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/3yOJY8ZRZ0dkYA2oN/builds/5Gipp93fwbnN6y4aA/openapi.json