# Email Verifier (`tomba-io/email-verifier`) Actor

Verify email addresses effortlessly by clicking the verification icon. Enhance communication accuracy

- **URL**: https://apify.com/tomba-io/email-verifier.md
- **Developed by:** [Tomba io](https://apify.com/tomba-io) (community)
- **Categories:** Lead generation, SEO tools, Open source
- **Stats:** 51 total users, 4 monthly users, 0.0% runs succeeded, 2 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Tomba Email Verifier Actor

[![Actor](https://img.shields.io/badge/Apify-Actor-blue)](https://apify.com/actors)
[![Tomba API](https://img.shields.io/badge/Tomba-API-green)](https://tomba.io)
[![Rate Limit](https://img.shields.io/badge/Rate%20Limit-150%2Fmin-orange)](https://tomba.io/api)

A powerful Apify Actor that **verifies the validity of any professional email address with the most complete email checker** using the **Tomba Email Verifier API**. Perfect for email marketing, lead generation, and data quality assurance by ensuring your email lists contain only valid, deliverable addresses.

### Key Features

- **Complete Email Verification**: Comprehensive validity checks for professional email addresses
- **Deliverability Testing**: Real-time SMTP validation and mailbox verification
- **Risk Assessment**: Identify disposable, webmail, and risky email addresses
- **Bulk Processing**: Verify hundreds of emails efficiently with rate limiting
- **Rate Limited**: Respects Tomba's 150 requests per minute limit
- **Rich Verification Data**: Detailed verification scores and technical checks
- **Built-in Error Handling**: Robust processing with comprehensive error reporting

### How it works

The Actor leverages Tomba's powerful Email Verifier API to perform comprehensive email validation:

#### Process Flow

1. **Authentication**: Connects to Tomba API using your credentials
2. **Input Processing**: Accepts array of email addresses to verify
3. **Email Verification**: Uses Tomba's `emailVerifier` method for each email
4. **Validation Checks**: Performs regex, SMTP, MX record, and deliverability tests
5. **Rate Limiting**: Automatically handles 150 requests/minute limit
6. **Data Storage**: Saves detailed verification results to Apify dataset

#### What You Get

For each verified email, you'll receive:

- **Verification Result**: Valid, invalid, risky, or unknown status
- **Confidence Score**: 0-100 score indicating verification confidence
- **Technical Checks**: Regex validation, MX records, SMTP server status
- **Risk Factors**: Disposable email detection, webmail identification
- **Deliverability**: Accept-all domain detection, block status
- **Quality Metrics**: Gibberish detection and comprehensive analysis

### Quick Start

#### Prerequisites

1. **Tomba Account**: Sign up at [Tomba.io](https://app.tomba.io/api) to get your API credentials

#### Getting Your API Keys

1. Visit [Tomba API Dashboard](https://app.tomba.io/api)
2. Copy your **API Key** (starts with `ta_`)
3. Copy your **Secret Key** (starts with `ts_`)

### Input Configuration

#### Required Parameters

| Parameter        | Type     | Description                        |
| ---------------- | -------- | ---------------------------------- |
| `tombaApiKey`    | `string` | Your Tomba API key (ta\_xxxx)       |
| `tombaApiSecret` | `string` | Your Tomba secret key (ts\_xxxx)    |
| `emails`         | `array`  | Array of email addresses to verify |

#### Optional Parameters

| Parameter    | Type     | Default | Description                         |
| ------------ | -------- | ------- | ----------------------------------- |
| `maxResults` | `number` | `50`    | Maximum number of results to return |

#### Example Input

```json
{
    "tombaApiKey": "ta_xxxxxxxxxxxxxxxxxxxx",
    "tombaApiSecret": "ts_xxxxxxxxxxxxxxxxxxxx",
    "emails": ["john.doe@company.com", "sales@example.org", "support@startup.io", "invalid@fakeemail.xyz"],
    "maxResults": 100
}
```

#### Best Practices

- **Email Quality**: Use properly formatted email addresses for best results
- **Rate Limits**: The Actor automatically handles Tomba's 150 requests/minute limit
- **Batch Size**: Process 50-100 emails at a time for optimal performance
- **Data Cleaning**: Pre-filter obvious invalid formats to save API credits

### Output Data Structure

The Actor returns comprehensive verification information for each email:

```json
{
    "email": {
        "email": "b.mohamed@tomba.io",
        "result": "deliverable",
        "status": "valid",
        "score": 99,
        "smtp_provider": "Google Workspace",
        "mx": {
            "records": [
                "aspmx.l.google.com",
                "alt2.aspmx.l.google.com",
                "alt1.aspmx.l.google.com",
                "alt4.aspmx.l.google.com",
                "alt3.aspmx.l.google.com"
            ]
        },
        "mx_check": true,
        "smtp_server": true,
        "smtp_check": true,
        "accept_all": false,
        "greylisted": false,
        "block": true,
        "gibberish": false,
        "disposable": false,
        "webmail": false,
        "regex": true,
        "whois": {
            "registrar_name": "namecheap, inc.",
            "referral_url": "https://www.namecheap.com/",
            "created_date": "2020-07-07T20:54:07+02:00"
        }
    },
    "sources": [
        {
            "uri": "https://github.com/tomba-io/generic-emails/blob/084fc1a63d3cdaf9a34f255bedc2baea49a8e8b9/src/lib/validation/hash.ts",
            "website_url": "github.com",
            "extracted_on": "2021-02-08T20:09:54+01:00",
            "last_seen_on": "2021-02-08T22:43:40+01:00",
            "still_on_page": true
        }
    ],
    "input": "b.mohamed@tomba.io"
}
```

#### Data Fields Explained

##### Email Verification Object

- **email**: The verified email address
- **result**: Deliverability status (deliverable, undeliverable, risky, unknown)
- **status**: Validation status (valid, invalid, risky, unknown)
- **score**: Confidence level from 0-100 (higher is better)
- **smtp\_provider**: Email provider name (e.g., "Google Workspace", "Microsoft Exchange")

##### Technical Validation

- **regex**: Whether email passes basic format validation
- **gibberish**: Whether email appears to be random/meaningless
- **disposable**: Whether email is from a temporary email service
- **webmail**: Whether email is from Gmail, Yahoo, etc.
- **mx\_check**: Whether MX records check passed
- **smtp\_server**: Whether SMTP server is reachable
- **smtp\_check**: Whether SMTP validation was successful
- **accept\_all**: Whether domain accepts all email addresses
- **greylisted**: Whether the email is greylisted
- **block**: Whether email is on a blocklist

##### Additional Data

- **mx**: Object containing MX record servers array
- **whois**: Domain registration information (registrar, creation date, etc.)
- **sources**: Array of sources where the email was found online
- **input**: Original input email address for reference

### Use Cases

#### Email Marketing

- **List Cleaning**: Remove invalid emails before campaigns
- **Bounce Reduction**: Prevent hard bounces and protect sender reputation
- **Quality Assurance**: Ensure high deliverability rates

#### Lead Generation

- **Lead Qualification**: Verify contact information quality
- **Data Validation**: Clean imported lead lists
- **CRM Integration**: Maintain clean contact databases

#### Data Quality

- **Database Maintenance**: Regular cleanup of email databases
- **Import Validation**: Verify emails during data import
- **Compliance**: Ensure GDPR/CAN-SPAM compliance with valid contacts

#### Risk Management

- **Fraud Prevention**: Identify disposable and risky email addresses
- **User Registration**: Validate emails during account creation
- **Security**: Block known problematic email domains

### Verification Views

The Actor provides specialized data views:

#### Overview View

Quick summary showing email, result, score, and key flags

#### Valid Emails View

Filtered view showing only successfully verified emails

#### Invalid Emails View

Focus on failed verifications with error details

#### Verification Errors View

Troubleshoot processing issues and API errors

### Resources & Documentation

#### API Documentation

- [Tomba API Docs](https://tomba.io/api) - Complete API reference
- [Email Verifier Endpoint](https://docs.tomba.io/api/verifier#email-verifier) - Specific verification documentation
- [Authentication Guide](https://app.tomba.io/api) - Get your API keys
- [Pricing & Limits](https://tomba.io/pricing) - Understand rate limits and costs

#### Rate Limiting

- Tomba limits to **150 requests per minute**
- Actor automatically handles rate limiting with delays
- Large email lists may take time to complete

#### Cost Considerations

- Each email verification = 1 Tomba API request
- Monitor your Tomba usage dashboard
- Consider Tomba's pricing tiers for volume usage

#### Best Practices

- **Pre-filtering**: Remove obvious invalid formats before verification
- **Batch Processing**: Group verifications for efficiency
- **Result Interpretation**: Use score and multiple flags for decision making
- **Regular Cleaning**: Periodically re-verify older email lists

### FAQ

#### General Questions

**Q: What does email verification do?**
A: Email verification checks if an email address is valid, deliverable, and safe to send to. It validates syntax, domain existence, mailbox availability, and identifies risky addresses.

**Q: How accurate is email verification?**
A: Tomba's verification is highly accurate (95%+) for most standard email providers. Results include confidence scores and detailed status information to help you make informed decisions.

**Q: What's the difference between syntax and deliverability checking?**
A: Syntax checking validates the email format (user@domain.com), while deliverability checking contacts the mail server to verify the mailbox actually exists and can receive mail.

#### Verification Results

**Q: What do the different verification statuses mean?**
A:

- **Valid**: Email exists and can receive mail
- **Invalid**: Email doesn't exist or can't receive mail
- **Risky**: Email might bounce or be problematic
- **Unknown**: Verification couldn't be completed

**Q: What is a verification score?**
A: Scores range 0-100 indicating confidence level. 90+ is high confidence, 70-89 is moderate, below 70 suggests caution. Use scores along with status for best results.

**Q: What are catch-all domains?**
A: Catch-all domains accept emails to any address at that domain, even non-existent ones. They're marked as "risky" because you can't verify if the specific mailbox exists.

**Q: How should I handle "risky" emails?**
A: Risky emails might include catch-all domains, role accounts, or temporary emails. Consider your use case - they might be fine for newsletters but problematic for transactional emails.

#### Technical Questions

**Q: How many emails can I verify at once?**
A: You can submit up to 1000 emails per run. For optimal performance, process 50-200 emails per batch.

**Q: What are the rate limits?**
A: The Actor automatically handles Tomba's rate limits. Large batches will be processed with appropriate delays to stay within limits.

**Q: Can I verify emails in real-time?**
A: Yes, but for real-time use cases, consider the API response time (typically 1-3 seconds per email). Batch processing is more efficient for large lists.

**Q: Do you store or cache verification results?**
A: Tomba may cache results temporarily for performance. The Actor doesn't store your email lists - data is processed and returned through Apify's secure infrastructure.

#### Email List Management

**Q: How often should I re-verify emails?**
A: Re-verify emails every 3-6 months, as email validity changes over time. High-bounce lists may need more frequent verification.

**Q: Should I remove all risky emails?**
A: Not necessarily. Review risky emails case-by-case. Some might be legitimate business emails that are just hard to verify due to server configurations.

**Q: What about role-based emails (info@, sales@)?**
A: Role emails are flagged as "role-based" but may still be valid for business communications. Consider your specific use case.

**Q: How do I handle large email lists?**
A: Break large lists into smaller batches (200-500 emails). Monitor your API quota and consider Tomba's higher-tier plans for volume processing.

#### Privacy & Compliance

**Q: Is email verification GDPR compliant?**
A: Yes, verification only checks deliverability without accessing email content. However, ensure you have permission to verify the email addresses you're checking.

**Q: Do you notify email owners during verification?**
A: No, verification is done through server-level checks that don't send actual emails or notify the email owners.

**Q: Can I verify international email addresses?**
A: Yes, Tomba supports verification for email addresses worldwide, including international domains and various country-specific providers.

### Keywords

email verification, email validation, email checker, deliverability, bounce detection, email quality, contact validation, email hygiene, email list cleaning, invalid emails, verification service, email testing

### Support

If you need any help, have questions, or encounter any issues while using Tomba.io, please don't hesitate to reach out to our support team. You can contact us via:

- **Email**: support@tomba.io
- **Live chat**: Available on the Tomba.io website during business hours

### Contributing

We welcome contributions to improve this actor. Please feel free to submit issues, feature requests, or pull requests to help make this tool even better for the community.

### About Tomba

Founded in 2020, Tomba prides itself on being the most reliable, accurate, and in-depth source of email address data available anywhere. We process terabytes of data to produce our Email finder API.

![Tomba Logo](https://tomba.io/logo.png)

# Actor input Schema

## `tombaApiKey` (type: `string`):

Your Tomba API key (starts with 'ta\_'). Get it from https://app.tomba.io/api

## `tombaApiSecret` (type: `string`):

Your Tomba API secret (starts with 'ts\_'). Get it from https://app.tomba.io/api

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

List of email addresses to verify for validity and deliverability

## `maxResults` (type: `integer`):

Maximum number of emails to process (default: 50, max: 1000)

## Actor input object example

```json
{
  "tombaApiKey": "ta_xxxxxxxxxxxxxxxxxxxx",
  "tombaApiSecret": "ts_xxxxxxxxxxxxxxxxxxxx",
  "emails": [
    "john@example.com",
    "jane@company.com",
    "test@domain.org"
  ],
  "maxResults": 50
}
```

# Actor output Schema

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

Email verification with deliverability status and quality scores

# 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 = {
    "tombaApiKey": "ta_xxxxxxxxxxxxxxxxxxxx",
    "tombaApiSecret": "ts_xxxxxxxxxxxxxxxxxxxx",
    "emails": [
        "john@stripe.com",
        "support@tomba.io"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tomba-io/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 = {
    "tombaApiKey": "ta_xxxxxxxxxxxxxxxxxxxx",
    "tombaApiSecret": "ts_xxxxxxxxxxxxxxxxxxxx",
    "emails": [
        "john@stripe.com",
        "support@tomba.io",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("tomba-io/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 '{
  "tombaApiKey": "ta_xxxxxxxxxxxxxxxxxxxx",
  "tombaApiSecret": "ts_xxxxxxxxxxxxxxxxxxxx",
  "emails": [
    "john@stripe.com",
    "support@tomba.io"
  ]
}' |
apify call tomba-io/email-verifier --silent --output-dataset

```

## MCP server setup

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