# Lead Contact Verifier — Emails + Deliverability Check (`0xgollum/lead-contact-verifier`) Actor

Give it any list of website URLs (Maps scraper, LinkedIn export, CSV) and get back every email found, tagged with an MX-record deliverability check and an address-type signal (named contact vs generic info@ vs personal Gmail) - plus LinkedIn/X/Instagram/Facebook links.

- **URL**: https://apify.com/0xgollum/lead-contact-verifier.md
- **Developed by:** [0xGollum](https://apify.com/0xgollum) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 checked contact rows

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/platform/actors/running/actors-in-store#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

## Lead Contact Verifier

Stop paying for a list of "leads" you can't tell apart from a list of dead links.

Give this actor any list of website URLs — pulled from a Google Maps scraper, a LinkedIn export, a CSV you already have — and it comes back with every email address it can find on each site, tagged with two honest signals: **can this domain even receive mail** (MX record present), and **is this a named contact, a generic role account, or a personal free-mail address** (not actually the company's own domain). Plus whatever LinkedIn/X/Instagram/Facebook links are on the page.

### Why not just scrape emails?

Most email scrapers stop at the regex match. That leaves you with `info@` addresses mixed in with real named contacts, and zero way to tell a working domain from a dead one without sending anything and hoping it doesn't bounce.

### What you get (one row per email found)

```json
{
  "input_url": "https://acme-plumbing.com",
  "domain": "acme-plumbing.com",
  "checked_at": "2026-08-11",
  "email": "jane@acme-plumbing.com",
  "source": "mailto",
  "deliverability": "mx_confirmed",
  "address_type": "corporate_personal",
  "linkedin": "https://linkedin.com/company/acme-plumbing",
  "x_twitter": null,
  "instagram": null,
  "facebook": "https://facebook.com/acmeplumbing"
}
```

- `source`: `mailto` (the address was wired into a clickable mailto: link — high confidence, a real business has no reason to fake this) or `text` (the address only appeared as plain text — usually a real contact too, but this is also where fictional example addresses in marketing/product copy show up; found live testing this actor against stripe.com, which surfaces a made-up customer email in a product mockup on some page variants). Treat `text` as "worth a glance," `mailto` as "trust it."
- `deliverability`: `mx_confirmed` (the domain has a real mail server — as far as any check can tell you without sending) or `no_mx_record` (the domain provably cannot receive mail — drop this one)
- `address_type`: `corporate_personal` (a named address on the company's own domain — highest value), `role_or_generic` (info@, contact@, support@ — still usable, just not a person), or `personal_free_provider` (gmail.com/yahoo.com etc — a real person, but not the company's own domain)

If a site has no email at all, you still get one row for it (`email: null`) so your input list is always fully accounted for in the output — no silent drops.

### Input

- `urls` (required): list of website URLs or bare domains
- `extra_paths` (optional, default `/contact`, `/contact-us`, `/about`, `/about-us`): pages tried if the homepage has no email — stops as soon as one is found
- `request_timeout_secs` (optional, default 15)

### Known limitation — read before you buy

**No live SMTP verification.** A real mailbox check (connecting to the mail server and asking if a specific address exists) needs outbound port 25, which is blocked on most cloud infrastructure — including, as far as this actor's testing could confirm, typical hosted run environments — specifically to stop spam. `mx_confirmed` is the strongest signal obtainable without it: it proves the domain *can* receive mail, not that this exact mailbox does. Treat `no_mx_record` as a hard "don't bother"; treat `mx_confirmed` as "worth trying," not as a guarantee.

**Marketing copy can contain fictional example emails.** Product mockups and docs sometimes show a made-up customer address as plain text (not a real contact). This is exactly why every row carries a `source` field — `mailto` addresses are wired into an actual link and safe to trust; `text` matches are usually real too but occasionally this kind of noise, so treat them as lower confidence.

**Larger companies often don't publish an email at all.** Enterprise and SaaS sites increasingly route everything through a contact form instead of a plain-text address (confirmed testing this actor against several real company sites). This actor works best on the kind of small/local business that a Google Maps lead list is usually made of — plumbers, clinics, agencies, shops — where a direct email in the footer is still the norm, not on Fortune-500 sites.

### Pricing

Pay per result ($0.02/row) — no charge for input URLs that produce nothing.

# Actor input Schema

## `urls` (type: `array`):

Websites to check - full URLs or bare domains. Works with the output of any lead source (Google Maps scraper, LinkedIn export, CSV list, ...), not just one platform.

## `extra_paths` (type: `array`):

If no email is found on the homepage, these paths are tried in order (stops as soon as an email is found).

## `request_timeout_secs` (type: `integer`):

HTTP request timeout per page fetched.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com",
    "https://stripe.com"
  ],
  "extra_paths": [
    "/contact",
    "/contact-us",
    "/about",
    "/about-us"
  ],
  "request_timeout_secs": 15
}
```

# 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 = {
    "urls": [
        "https://apify.com",
        "https://stripe.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("0xgollum/lead-contact-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 = { "urls": [
        "https://apify.com",
        "https://stripe.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("0xgollum/lead-contact-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 '{
  "urls": [
    "https://apify.com",
    "https://stripe.com"
  ]
}' |
apify call 0xgollum/lead-contact-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,0xgollum/lead-contact-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/aZAfllN16Cen3sCUd/builds/dqJqq0AGdzLS9SQxC/openapi.json