# Email Verifier — Bulk Validator: Domain, Disposable & Typos (`hipersoft/email-verifier`) Actor

Clean email lists in bulk without sending mail: syntax, mail-server (MX) check, disposable and role detection, free-provider flag, typo suggestions, status and score. Verify any scraper dataset. Checks addresses and domains, not individual mailboxes.

- **URL**: https://apify.com/hipersoft/email-verifier.md
- **Developed by:** [Hipersoft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Other
- **Features:** Limited permissions, Multi-tenant, Server interface
- **Stats:** 1 total users, 0 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?

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

## Email Verifier — Bulk Email Validator: Syntax, Domain, Disposable & Typos

**Email Verifier** cleans email lists in bulk without sending any mail. It checks **syntax**, whether the **domain can receive mail (MX)**, **disposable and temporary addresses**, **role inboxes**, **free providers** and **domain typos** such as `gmial.com`, then gives each address a clear **status and score**.

![Email Verifier input — configure the options in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/email-verifier-input.png)

### What does Email Verifier do?

Paste a list of addresses, or point it at a dataset from a lead scraper, and get one row per address that tells you whether to keep it, check it or drop it. Duplicates are skipped so you don't pay for them twice.

**What it does not do:** it doesn't confirm that a specific mailbox exists. It checks the address and its domain. `likely_valid` means the address looks right and the domain accepts mail; a mailbox on that domain can still bounce. If you need a per-mailbox check, use a dedicated mailbox verification tool as a second step, and use this one first to remove obvious bad addresses for less.

### What does each email check tell you?

| Check | Field | Catches |
| --- | --- | --- |
| Syntax | `syntaxOk` | Malformed addresses |
| Mail server | `mxFound`, `mxHost`, `mxRecords` | Domains that can't receive mail |
| Disposable | `disposable` | Temporary inboxes such as mailinator and yopmail |
| Role inbox | `role` | Shared addresses such as info@ and support@ |
| Free provider | `isFreeProvider` | gmail.com, outlook.com and similar, useful for B2B lists |
| Typos | `didYouMean` | gmial.com, hotnail.com and similar |
| Plus addressing | `isPlusAddressed` | name+tag@ variants |
| Domain mail setup | `hasSpf`, `hasDmarc` | Domains with sender policies published, a sign of a maintained mail setup |

### Use cases

- **Clean lead lists** before importing them into a CRM or outreach tool.
- **Lower your bounce rate** by removing dead domains and typos before a campaign.
- **Filter sign-ups** for disposable addresses.
- **Separate B2B from free-mail** addresses in a lead list.
- **Pre-filter before paid mailbox checks** so you only pay for addresses worth checking.

### How to verify an email list

1. Open Email Verifier.
2. Paste addresses under **Emails**, one per line, or enter a dataset ID under **Verify a dataset**.
3. Click **Start**.
4. Filter by `status` and export to JSON, CSV or Excel.

### Input

```json
{
  "emails": ["name+tag@gmail.com", "john@gmial.com", "sales@mailinator.com"],
  "dedupe": true
}
```

| Field | Description |
| --- | --- |
| `emails` | Addresses to verify. |
| `inputDatasetId` | Optional dataset to read addresses from, such as a lead scraper's output. |
| `emailField` | The column in that dataset holding the address (default `email`). |
| `dedupe` | Check each address once (default on). |
| `concurrency` | Addresses checked in parallel, 1 to 30 (default 10). |

### Output

![Email Verifier output — the results as a clean dataset](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/email-verifier-output.png)
One row per address. These rows come from a real run.

```json
{
  "email": "name+tag@gmail.com",
  "valid": true,
  "syntaxOk": true,
  "domain": "gmail.com",
  "mxFound": true,
  "mxHost": "gmail-smtp-in.l.google.com",
  "disposable": false,
  "role": false,
  "smtpChecked": false,
  "deliverable": null,
  "reason": "Valid syntax and domain has a mail server (MX present).",
  "ok": true,
  "status": "likely_valid",
  "score": 80,
  "normalizedEmail": "name+tag@gmail.com",
  "isFreeProvider": true,
  "isPlusAddressed": true,
  "didYouMean": null,
  "mxRecords": [
    "gmail-smtp-in.l.google.com",
    "alt1.gmail-smtp-in.l.google.com",
    "alt2.gmail-smtp-in.l.google.com",
    "alt3.gmail-smtp-in.l.google.com",
    "alt4.gmail-smtp-in.l.google.com"
  ],
  "hasSpf": true,
  "hasDmarc": true,
  "checkedAt": "2026-11-04T12:54:02.510Z"
}
```

A typo with no working domain:

```json
{
  "email": "john@gmial.com",
  "valid": false,
  "syntaxOk": true,
  "domain": "gmial.com",
  "mxFound": false,
  "mxHost": null,
  "disposable": false,
  "role": false,
  "smtpChecked": false,
  "deliverable": null,
  "reason": "Domain has no mail server. Did you mean john@gmail.com?",
  "ok": true,
  "status": "invalid",
  "score": 0,
  "normalizedEmail": "john@gmial.com",
  "isFreeProvider": false,
  "isPlusAddressed": false,
  "didYouMean": "john@gmail.com",
  "mxRecords": [],
  "hasSpf": null,
  "hasDmarc": null,
  "checkedAt": "2026-11-04T12:54:02.510Z"
}
```

#### What the status means

| `status` | Meaning | Suggested action |
| --- | --- | --- |
| `likely_valid` | Good syntax, and the domain accepts mail. Mailbox not confirmed. | Keep |
| `risky` | Disposable domain or likely typo. | Review or drop |
| `invalid` | Bad syntax or no mail server. | Drop |
| `unknown` | The lookup timed out. | Re-run |

`score` runs from 0 to 100. Good addresses start at 70, gain points for published SPF and DMARC records, and lose 15 for role inboxes. Filter on `status` first; the score is only a rough ranking.

#### Output schema

| Field | Type | Description |
| --- | --- | --- |
| `email` | string | The address as you supplied it. |
| `normalizedEmail` | string | Trimmed and lowercased. |
| `status` | string | `likely_valid`, `risky`, `invalid` or `unknown`. |
| `score` | integer | Rough 0 to 100 ranking. |
| `valid` | boolean | Good syntax, mail server found, not disposable. |
| `syntaxOk` | boolean | Passes the syntax check. |
| `domain` | string | Domain part of the address. |
| `mxFound` | boolean | Domain has a mail server. |
| `mxHost` / `mxRecords` | string / array | Primary mail server, and all of them. |
| `disposable` | boolean | Temporary-email domain. |
| `role` | boolean | Shared inbox such as info@. |
| `isFreeProvider` | boolean | Free mail provider. |
| `isPlusAddressed` | boolean | Uses +tag. |
| `didYouMean` | string | Suggested fix for a likely typo. |
| `hasSpf` / `hasDmarc` | boolean | Domain publishes these records. |
| `smtpChecked` / `deliverable` | boolean | Optional check result; usually false and null. |
| `reason` | string | Plain-language explanation. |
| `ok` | boolean | The check itself completed. |
| `checkedAt` | string (ISO date) | When the address was checked. |

### Need email data too?

- [Website Contact Scraper](https://apify.com/hipersoft/website-contact-scraper): find emails and phone numbers on company websites, then verify them here.
- [Google Maps Email Extractor](https://apify.com/hipersoft/google-maps-email-extractor): business emails from Google Maps.

### FAQ

**Does it send emails?**
No. It never sends anything.

**Does it confirm a mailbox exists?**
No. It checks the address and the domain. Treat `likely_valid` as "worth keeping", not as a delivery guarantee.

**How much does it cost?**
You pay per address checked, shown on the **Pricing** tab. Duplicates are skipped. Set a maximum cost per run and it stops cleanly at that limit, storing only what you paid for.

**Can I verify the results of another scraper?**
Yes. Put that run's dataset ID in **Verify a dataset** and set the email column.

**How big can my list be?**
Large lists are fine. Addresses on the same domain share one lookup, so big lists stay fast.

**Can I connect this to other tools?**
Yes, through [integrations on the Apify platform](https://apify.com/integrations): [Make](https://apify.com/integrations/make), [Zapier](https://apify.com/integrations/zapier), [Slack](https://docs.apify.com/platform/integrations/slack), [Airbyte](https://docs.apify.com/platform/integrations/airbyte), [GitHub](https://docs.apify.com/platform/integrations/github), [Google Drive](https://docs.apify.com/platform/integrations/drive) and [many more](https://apify.com/integrations), plus the [Apify API](https://docs.apify.com/api/v2) and [webhooks](https://docs.apify.com/platform/integrations/webhooks).

**Is it legal?**
Only verify addresses you have a right to process, and follow privacy and anti-spam law.

### Feedback

How did it go? Good or bad, a [review](https://console.apify.com/actors/clZM3mvdp5AkcUd8M/reviews) helps other users decide and tells us what to improve. Something broken or missing? Open an [issue](https://apify.com/hipersoft/email-verifier/issues) and we'll look at it.

### Related Actors

- [Website Contact Scraper](https://apify.com/hipersoft/website-contact-scraper)
- [Google Maps Email Extractor](https://apify.com/hipersoft/google-maps-email-extractor)

### Notes

Independent tool. Addresses are processed only to produce your results.

# Actor input Schema

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

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

## `inputDatasetId` (type: `string`):

Optional. Pick a dataset, for example from a lead scraper run. Addresses in the column below are verified too.

## `emailField` (type: `string`):

Which column of the dataset holds the email address.

## `dedupe` (type: `boolean`):

Check each address once, so duplicates aren't charged twice.

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

Optional extra server check. Usually returns no result; leave it off.

## `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"
  ],
  "emailField": "email",
  "dedupe": true,
  "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/INHTStz6PeXlq5MYV/openapi.json