# Email Verifier — Bulk Syntax, MX & Disposable Check (`hipersoft/email-verifier`) Actor

Bulk-verify email addresses without sending mail: syntax, MX/domain deliverability, disposable and role-address detection. Clean your list before outreach or CRM import.

- **URL**: https://apify.com/hipersoft/email-verifier.md
- **Developed by:** [hiper soft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.001 / email verified

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 — Bulk Syntax, MX & Disposable Check

**Clean your email list before you send.** Verify addresses in bulk — syntax, mail-server (MX) deliverability, disposable/throwaway domains and role inboxes — without ever sending an email. No account, no API key.

### What it does

Give it a list of emails and get one clear row back per address:

- **Syntax check** — catches typos and malformed addresses.
- **MX / domain check** — confirms the domain actually has a mail server that can receive mail.
- **Disposable detection** — flags temporary/throwaway domains (mailinator, 10minutemail, yopmail, …).
- **Role-address detection** — flags `info@`, `admin@`, `support@`, `sales@`, `noreply@` and other shared, non-personal inboxes.
- **Best-effort mailbox probe** — an optional deliverability signal (see FAQ).
- **`valid` verdict + reason** — every row explains itself, so you can set your own cut-off.

### Use cases

- **Verify before you email** — strip bounces and throwaway addresses out of a cold-outreach list to protect sender reputation.
- **Clean before CRM import** — validate contacts before they hit HubSpot, Salesforce or your database.
- **Signup hygiene** — flag disposable emails at registration.
- **Automate it in n8n / Make / Zapier** — drop verification into a workflow: scrape or collect leads, verify the list, then only email or import the good ones.

### Input

```json
{
  "emails": ["hello@apify.com", "info@gmail.com", "sales@mailinator.com", "bad@@nope"],
  "smtpCheck": false,
  "concurrency": 10
}
```

| Field | Type | Description |
|---|---|---|
| `emails` | array | Addresses to verify (one per line). No mail is sent. |
| `smtpCheck` | boolean | Attempt a best-effort SMTP deliverability probe (off by default — see FAQ). |
| `concurrency` | integer | How many addresses to verify in parallel (1–30). |

### Output

One record per email:

```json
{
  "email": "info@gmail.com",
  "valid": true,
  "syntaxOk": true,
  "domain": "gmail.com",
  "mxFound": true,
  "mxHost": "gmail-smtp-in.l.google.com",
  "disposable": false,
  "role": true,
  "smtpChecked": false,
  "deliverable": null,
  "reason": "Domain can receive mail; role address (shared inbox, not a person).",
  "ok": true
}
```

#### Output schema

| Field | Type | Description |
|---|---|---|
| `email` | string | The address you submitted. |
| `valid` | boolean | Overall verdict: good syntax, a real mail server, and not a disposable domain. |
| `syntaxOk` | boolean | Whether the address is well-formed. |
| `domain` | string | Domain part of the address. |
| `mxFound` | boolean | Whether the domain has a mail server (MX / A record). |
| `mxHost` | string | Primary mail host, when found. |
| `disposable` | boolean | Whether the domain is a known throwaway/temporary provider. |
| `role` | boolean | Whether it's a shared role inbox (info@, support@, …) rather than a person. |
| `smtpChecked` | boolean | Whether the best-effort mailbox probe actually ran. |
| `deliverable` | boolean | Best-effort mailbox result (`null` when not checked or inconclusive). |
| `reason` | string | Human-readable explanation of the verdict. |
| `ok` | boolean | Whether this address was processed without error. |

### FAQ

**Do you send any email?** No. Verification is done from address format and public DNS records — nothing lands in anyone's inbox.

**What is the SMTP probe?** An optional, best-effort deliverability signal. Most cloud networks block the outbound port it needs, so it often can't run — when that happens `smtpChecked` stays `false` and you still get the full syntax / MX / disposable / role verdict, which already removes the large majority of bad addresses.

**Can I automate it?** Yes — via [integrations on the Apify platform](https://apify.com/integrations) (n8n, Make, Zapier, and more) and the [Apify API](https://docs.apify.com/api/v2). Verify a freshly scraped list before you email it or push it into your CRM.

### Notes

Original clean-room implementation.

# Actor input Schema

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

Email addresses to verify. One per line. No mail is sent.

## `smtpCheck` (type: `boolean`):

Attempt a live SMTP RCPT probe for a deliverability signal. Best-effort only: many networks (including most cloud platforms) block outbound port 25, in which case the address still gets a full syntax/MX/disposable/role verdict and smtpChecked stays false. Off by default.

## `concurrency` (type: `integer`):

How many emails to verify in parallel (1–30). Higher is faster for large lists.

## Actor input object example

```json
{
  "emails": [
    "hello@apify.com",
    "info@gmail.com",
    "sales@mailinator.com",
    "test@nonexistentdomain-xyz-9999.tld",
    "bad@@nope"
  ],
  "smtpCheck": false,
  "concurrency": 10
}
```

# Actor output Schema

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

The verification results as dataset items.

# 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": [
        "hello@apify.com",
        "info@gmail.com",
        "sales@mailinator.com",
        "test@nonexistentdomain-xyz-9999.tld",
        "bad@@nope"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/email-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 = { "emails": [
        "hello@apify.com",
        "info@gmail.com",
        "sales@mailinator.com",
        "test@nonexistentdomain-xyz-9999.tld",
        "bad@@nope",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/email-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 '{
  "emails": [
    "hello@apify.com",
    "info@gmail.com",
    "sales@mailinator.com",
    "test@nonexistentdomain-xyz-9999.tld",
    "bad@@nope"
  ]
}' |
apify call hipersoft/email-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/email-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/clZM3mvdp5AkcUd8M/builds/xK4SfCm7gkiXdbvfY/openapi.json