# Email Validation & Disposable Email Detector (`mayno/email-risk-scorer`) Actor

Detect disposable emails, score email risk, and protect your signup flow. Block fake signups from Mailinator, Guerrilla Mail, and 500+ temporary email providers.

- **URL**: https://apify.com/mayno/email-risk-scorer.md
- **Developed by:** [Amine Feriani](https://apify.com/mayno) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 9 total users, 1 monthly users, 100.0% runs succeeded, 3 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Risk Scorer & Disposable Email Detector

**Protect your signup flow from fake accounts, disposable emails, and fraudulent registrations. Clean your email marketing lists before campaigns.**

This actor analyzes email addresses and returns a comprehensive risk assessment, helping you block temporary emails, identify free providers, validate MX records, and detect role-based addresses — all in real-time.

***

### 🎯 What It Does

Every SaaS product, e-commerce platform, or community site faces the same problem: **fake signups from disposable emails**. Someone creates a throwaway account with `user123@guerrillamail.com`, abuses your free trial, and disappears.

This actor solves that by analyzing each email and returning:

- ✅ **Disposable email detection** — Blocks 500+ temporary email providers (Mailinator, Guerrilla Mail, 10MinuteMail, etc.)
- ✅ **Free provider detection** — Identifies Gmail, Yahoo, Outlook, and 100+ other free email services
- ✅ **Business email validation** — Confirms legitimate company domains with valid MX records
- ✅ **MX record verification** — Checks if the domain can actually receive emails
- ✅ **Email provider identification** — Detects Google Workspace, Microsoft 365, Zoho, and more
- ✅ **Role-based email detection** — Flags generic addresses like `info@`, `admin@`, `noreply@`
- ✅ **Risk level scoring** — Returns `low`, `medium`, or `high` risk classification

***

### 🚀 Use Cases

#### SaaS & Freemium Products

Block fake signups during free trial registration. Once integrated into your signup flow, this actor runs on every new user registration — protecting your product from abuse.

#### E-Commerce & Marketplaces

Detect throwaway emails at checkout to reduce fraud, chargebacks, and fake orders.

#### Email Marketing & Lead Generation

Clean your email lists before sending campaigns. Remove disposable emails to protect your sender reputation and improve deliverability.

#### Community Platforms & Forums

Prevent spam accounts from flooding your platform with fake registrations.

#### CRM & Lead Scoring

Score leads based on email quality. A lead with a disposable email address is worthless — filter them out before they enter your pipeline.

***

### 📋 Input

The actor accepts a simple JSON input with a list of email addresses:

```json
{
  "emails": [
    "test@mailinator.com",
    "ceo@stripe.com",
    "user@gmail.com",
    "admin@company.com"
  ]
}
```

**Input Parameters:**

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `emails` | array | Yes | List of email addresses to analyze (max 10,000 per run) |

***

### 📤 Output

For each email, you get a comprehensive risk assessment:

```json
{
  "email": "test@mailinator.com",
  "isValid": true,
  "isDisposable": true,
  "isFreeProvider": false,
  "isBusinessEmail": false,
  "isRoleBasedEmail": false,
  "domain": "mailinator.com",
  "hasMXRecord": true,
  "mxProvider": "mail.mailinator.com",
  "riskLevel": "high",
  "reasons": [
    "Disposable/temporary email provider"
  ]
}
```

**Output Fields:**

| Field | Type | Description |
|-------|------|-------------|
| `email` | string | The analyzed email address (normalized to lowercase) |
| `isValid` | boolean | Whether the email has valid syntax |
| `isDisposable` | boolean | Whether the domain is a known disposable/temporary email provider |
| `isFreeProvider` | boolean | Whether the domain is a free email service (Gmail, Yahoo, etc.) |
| `isBusinessEmail` | boolean | Whether it's a legitimate business email (valid MX + not disposable/free) |
| `isRoleBasedEmail` | boolean | Whether it uses a generic prefix like `info@`, `admin@`, `support@` |
| `domain` | string | The email domain (e.g., `mailinator.com`) |
| `hasMXRecord` | boolean | Whether the domain has valid MX (mail exchange) records |
| `mxProvider` | string | The email provider identified from MX records (e.g., "Google Workspace") |
| `riskLevel` | string | Overall risk assessment: `low`, `medium`, or `high` |
| `reasons` | array | List of reasons explaining the risk classification |

***

### 🎓 How Risk Levels Work

The actor evaluates multiple signals and assigns one of three risk levels:

#### 🟢 **Low Risk** (Safe to accept)

- Valid business email with MX records
- Examples: `ceo@stripe.com`, `hello@notion.so`
- Free providers like Gmail/Yahoo with valid syntax

#### 🟡 **Medium Risk** (Review manually)

- Missing MX records
- Role-based emails on otherwise valid domains
- Example: `team@startup-without-mx-setup.com`

#### 🔴 **High Risk** (Block or flag)

- Disposable/temporary email providers
- Invalid email syntax
- No MX records + other red flags
- Examples: `user@mailinator.com`, `fake@guerrillamail.com`

### 📧 Optional: Email List Cleaning

Need to clean an email marketing list before a campaign? Enable the **"Return clean list only"** option to get a filtered CSV of valid emails ready for import.

**How it works:**

1. Check ☑ "Return clean list only" in the input
2. Configure filters (exclude disposable, require MX records, etc.)
3. Run the actor
4. Download `clean_emails.csv` from the outputs
5. Import to Mailchimp, SendGrid, or your ESP

**Available filters:**

- Exclude disposable emails (Mailinator, Guerrilla Mail, etc.)
- Exclude free providers (Gmail, Yahoo - useful for B2B)
- Exclude role-based emails (info@, admin@, support@)
- Require valid MX records

You get both the full risk analysis AND a clean export ready for your email platform.

# Actor input Schema

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

List of email addresses to analyze for risk. Maximum 10,000 emails per run.

## `returnCleanListOnly` (type: `boolean`):

Enable to filter out invalid emails and export a clean list (TXT + CSV). Perfect for cleaning email marketing lists before campaigns.

## `excludeDisposable` (type: `boolean`):

Remove Mailinator, Guerrilla Mail, and 500+ other temporary providers (only applies when 'Return clean list only' is enabled)

## `excludeFreeProviders` (type: `boolean`):

Remove Gmail, Yahoo, Hotmail - useful for B2B list cleaning (only applies when 'Return clean list only' is enabled)

## `excludeRoleBased` (type: `boolean`):

Remove info@, admin@, support@, noreply@ addresses (only applies when 'Return clean list only' is enabled)

## `requireMXRecords` (type: `boolean`):

Remove emails from domains without mail servers (only applies when 'Return clean list only' is enabled)

## Actor input object example

```json
{
  "emails": [
    "test@mailinator.com",
    "ceo@stripe.com",
    "user@gmail.com"
  ],
  "returnCleanListOnly": false,
  "excludeDisposable": true,
  "excludeFreeProviders": false,
  "excludeRoleBased": false,
  "requireMXRecords": true
}
```

# Actor output Schema

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

Complete email risk analysis for all processed emails

## `cleanListTxt` (type: `string`):

Filtered valid emails, one per line - available when 'Return clean list only' is enabled

## `cleanListCsv` (type: `string`):

Filtered valid emails as CSV - available when 'Return clean list only' is enabled

# 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": [
        "test@mailinator.com",
        "ceo@stripe.com",
        "user@gmail.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mayno/email-risk-scorer").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": [
        "test@mailinator.com",
        "ceo@stripe.com",
        "user@gmail.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mayno/email-risk-scorer").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": [
    "test@mailinator.com",
    "ceo@stripe.com",
    "user@gmail.com"
  ]
}' |
apify call mayno/email-risk-scorer --silent --output-dataset

```

## MCP server setup

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

```

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/rxNdNOuj1P5jcphoC/builds/aK7f5H8mds41NPBFg/openapi.json