# Email Verifier Free to Use (`fetch_cat/email-verifier-free-to-use-scraper`) Actor

Validate email syntax and domain mail readiness in bulk. Export normalized addresses, MX records, validation reasons, and timestamps for lead-list cleaning.

- **URL**: https://apify.com/fetch\_cat/email-verifier-free-to-use-scraper.md
- **Developed by:** [Hanna Nosova](https://apify.com/fetch_cat) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.47 / 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 Free to Use

Clean lead lists before CRM imports and outreach. Submit email addresses in bulk and receive a structured syntax and public domain mail-readiness result for every unique address.

### What you get

- Clear `valid` or `invalid` status with a reason
- Normalized email, local part, Unicode domain, and ASCII domain
- Public MX availability plus ordered mail-exchanger records
- SMTPUTF8 requirement and verification timestamp
- Deduplicated, export-ready JSON, CSV, Excel, or HTML results

### Example input

```json
{
  "emails": ["contact@gmail.com", "not-an-email"],
  "checkDeliverability": true,
  "allowInternationalized": false
}
```

### Example output

```json
{
  "inputEmail": "contact@gmail.com",
  "status": "valid",
  "reason": null,
  "normalizedEmail": "contact@gmail.com",
  "localPart": "contact",
  "domain": "gmail.com",
  "asciiDomain": "gmail.com",
  "syntaxValid": true,
  "hasMx": true,
  "mxRecords": [{"exchange": "gmail-smtp-in.l.google.com", "priority": 5}],
  "requiresSmtpUtf8": false,
  "checkedAt": "2026-09-06T14:22:51.267Z"
}
```

### Use cases

- Clean lead lists before sales outreach
- Reject malformed signup addresses
- Audit CRM email quality
- Separate syntax failures from domains without public mail servers
- Normalize internationalized domains for downstream systems

### Input settings

| Field | Type | Default | Description |
|---|---|---|---|
| `emails` | string\[] | required | 1–10,000 email addresses |
| `checkDeliverability` | boolean | `true` | Resolve public MX records |
| `allowInternationalized` | boolean | `false` | Allow non-ASCII local parts |

### Output fields

| Field | Description |
|---|---|
| `inputEmail` | Original trimmed input |
| `status` | `valid` or `invalid` under the selected checks |
| `reason` | Human-readable failure reason, otherwise null |
| `normalizedEmail` | Normalized address when syntax is valid |
| `localPart` | Text before `@` |
| `domain` | Lowercase Unicode domain |
| `asciiDomain` | DNS-ready ASCII domain |
| `syntaxValid` | Whether address syntax passed |
| `hasMx` | Whether MX records exist; null if DNS checks are disabled |
| `mxRecords` | Ordered MX exchanges and priorities |
| `requiresSmtpUtf8` | Whether the local part requires SMTPUTF8 |
| `checkedAt` | UTC verification timestamp |

### Input recipes

**Fast syntax-only cleanup**

```json
{"emails":["lead@example.com","bad address"],"checkDeliverability":false}
```

**Internationalized addresses**

```json
{"emails":["tèst@example.com"],"allowInternationalized":true}
```

### Who is it for?

- Sales operations teams cleaning lead lists before CRM import
- Growth teams validating form submissions and prospect exports
- Data teams that need deterministic, row-by-row validation reasons
- Developers adding email hygiene to scheduled automations

### Pricing

This Actor charges a small run-start event and one `result` event per saved verification row. See the [live Pricing tab](https://apify.com/fetch_cat/email-verifier-free-to-use-scraper/pricing) for current rates and volume discounts. Duplicate inputs are processed once.

### Tips and limits

- MX records prove that a domain advertises mail infrastructure; they do not prove that a specific mailbox exists.
- This Actor does not perform SMTP handshakes, send messages, or claim catch-all detection.
- DNS changes can alter results over time; use `checkedAt` when auditing snapshots.
- A maximum of 10,000 input addresses is accepted per run.

### API usage

**cURL**

```bash
curl -X POST "https://api.apify.com/v2/acts/fetch_cat~email-verifier-free-to-use-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"emails":["contact@example.com"],"checkDeliverability":true}'
```

**JavaScript**

```javascript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/email-verifier-free-to-use-scraper').call({
  emails: ['contact@example.com'], checkDeliverability: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

**Python**

```python
from apify_client import ApifyClient
import os
client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/email-verifier-free-to-use-scraper').call(
    run_input={'emails': ['contact@example.com'], 'checkDeliverability': True}
)
items = client.dataset(run['defaultDatasetId']).list_items().items
```

### MCP and agents

Connect through Apify MCP at `https://mcp.apify.com?tools=fetch_cat/email-verifier-free-to-use-scraper`.

```bash
claude mcp add apify --transport http \
  "https://mcp.apify.com?tools=fetch_cat/email-verifier-free-to-use-scraper"
```

Equivalent JSON configuration:

```json
{"mcpServers":{"apify":{"type":"http","url":"https://mcp.apify.com?tools=fetch_cat/email-verifier-free-to-use-scraper"}}}
```

Example prompts: “Validate these addresses and explain each rejection” or “Clean this exported lead list and return only rows whose domains publish MX records.”

### FAQ

**Does `valid` guarantee mailbox delivery?** No. It means syntax passed and, when enabled, the domain published MX records.

**Are emails retained by this Actor?** Results are written to your Apify run dataset and follow your Apify storage settings.

**Why is `hasMx` null?** DNS checks were disabled with `checkDeliverability: false`.

### Related Actors

- [Google Maps Scraper](https://apify.com/fetch_cat/google-maps-scraper) for public business leads
- [LinkedIn Jobs Scraper](https://apify.com/fetch_cat/linkedin-jobs-scraper) for recruiting research
- [LinkedIn Company Scraper](https://apify.com/fetch_cat/linkedin-company-scraper) for company enrichment
- [Google Search Results Scraper](https://apify.com/fetch_cat/google-search-results-scraper) for prospect research
- [Website Contact Details Scraper](https://apify.com/fetch_cat/website-contact-details-scraper) for public contact discovery

### Support

Open an issue on the Actor page with a minimal input and run ID. Do not post sensitive address lists publicly.

# Actor input Schema

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

One email address per line (maximum 10,000).

## `checkDeliverability` (type: `boolean`):

Resolve public MX records in addition to checking syntax.

## `allowInternationalized` (type: `boolean`):

Accept non-ASCII characters before the @ sign.

## Actor input object example

```json
{
  "emails": [
    "contact@gmail.com",
    "not-an-email",
    "user@nonexistent-domain-8310.invalid"
  ],
  "checkDeliverability": true,
  "allowInternationalized": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# 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": [
        "contact@gmail.com",
        "not-an-email",
        "user@nonexistent-domain-8310.invalid"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fetch_cat/email-verifier-free-to-use-scraper").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": [
        "contact@gmail.com",
        "not-an-email",
        "user@nonexistent-domain-8310.invalid",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("fetch_cat/email-verifier-free-to-use-scraper").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": [
    "contact@gmail.com",
    "not-an-email",
    "user@nonexistent-domain-8310.invalid"
  ]
}' |
apify call fetch_cat/email-verifier-free-to-use-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/email-verifier-free-to-use-scraper"
        }
    }
}

```

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/YFHBng4XBsbC5SnaO/builds/0fTfFBaAxOM4cYfMl/openapi.json