# Email Domain Verifier — stop bounces before you send (`apexfaucetdotxyz/email-domain-verifier`) Actor

Check which domains can actually receive email, and who hosts their mail. DNS-based, fast, and honest about what it can and cannot know.

- **URL**: https://apify.com/apexfaucetdotxyz/email-domain-verifier.md
- **Developed by:** [Martin Raum](https://apify.com/apexfaucetdotxyz) (community)
- **Categories:** Lead generation, Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## 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 Domain Verifier — stop bounces before you send

Paste domains or email addresses. Get back which ones can actually receive mail,
and who hosts it.

### Why this matters

Sending to a domain with no MX record is a **guaranteed bounce**, and a high
bounce rate is what gets your sending domain blacklisted. One DNS lookup per
domain prevents that. On a real test, an accountancy firm with 41 named staff
published **no MX record at all** — every address inferred for it would have
bounced.

### What you get

| field | meaning |
|---|---|
| `acceptsMail` | the domain publishes MX records and can receive mail |
| `mailProvider` | Google Workspace, Microsoft 365, Proofpoint, Mimecast… |
| `mxHosts` | the actual mail servers, by priority |
| `reason` | why not, when it can't: no MX published, or the domain doesn't resolve |

Knowing the provider is useful on its own — a Google or Microsoft domain behaves
predictably, and a catch-all provider means address-level verification is
impossible for anyone, at any price.

### What it does not do

**It does not claim a specific mailbox exists.** That would need SMTP probing,
which is intrusive, gets your infrastructure blacklisted, and is defeated by
catch-all servers anyway. This tells you whether the *domain* accepts mail —
which is the honest, useful half of the question. Any product promising
"verified" addresses from a scrape alone is overstating what it can know.

### Pairs with

Run it over the output of **Email Pattern Finder** or any lead list before your
first send. It's DNS-only, so it's fast and cheap even on thousands of domains.

# Actor input Schema

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

Paste domains (acme.com) or full email addresses (sarah@acme.com) — addresses are reduced to their domain automatically, and duplicates are removed. Feed it straight from a CRM export or the output of any lead scraper.

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

How many DNS lookups to run at once. Higher is faster; 10 is comfortable for most lists.

## Actor input object example

```json
{
  "domains": [
    "coapt.co.uk",
    "perrysaccountants.co.uk",
    "sarah@gmail.com"
  ],
  "concurrency": 10
}
```

# Actor output Schema

## `dataset` (type: `string`):

Which domains accept mail and which will bounce.

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

Browse the results as a table.

# 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 = {
    "domains": [
        "coapt.co.uk",
        "perrysaccountants.co.uk",
        "sarah@gmail.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apexfaucetdotxyz/email-domain-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 = { "domains": [
        "coapt.co.uk",
        "perrysaccountants.co.uk",
        "sarah@gmail.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("apexfaucetdotxyz/email-domain-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 '{
  "domains": [
    "coapt.co.uk",
    "perrysaccountants.co.uk",
    "sarah@gmail.com"
  ]
}' |
apify call apexfaucetdotxyz/email-domain-verifier --silent --output-dataset

```

## MCP server setup

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