# Domain Lead Qualifier – WHOIS + DNS Email-Readiness Score (`emastra/domain-intelligence`) Actor

Upload a list of domains → get age, registrar, MX/SPF/DMARC status, TLS info, hosting org, and a green/red “email-ready lead score.” Perfect for SDRs, lead-gen agencies, list vendors, and growth teams who don’t want to waste time emailing dead domains.

- **URL**: https://apify.com/emastra/domain-intelligence.md
- **Developed by:** [Emiliano Mastragostino](https://apify.com/emastra) (community)
- **Categories:** Lead generation, Automation, Other
- **Features:** Limited permissions
- **Stats:** 18 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 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.
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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 🧭 Domain Lead Qualifier – Email Readiness & WHOIS Intelligence API (Bulk Enrichment)

*Upload domains → get age, registrar, DNS auth & email-sendability score. Built for SDRs, lead-gen agencies & list vendors.*

**Domain Lead Qualifier** helps SDR teams and growth operators qualify domains *before outreach* using email readiness and deliverability signals, WHOIS/RDAP registration data, TLS status, and hosting intelligence. Run it from the Apify Console or automate it via API to score domains at scale and avoid low-quality or risky leads.

### ⭐ Key Features

- 🎯 **Bulk domain enrichment for lead qualification** — one result per domain
- 📬 **Email readiness & deliverability checks** — MX, SPF, DMARC + disposable detection
- 🧾 **WHOIS / RDAP intelligence** — domain age, registrar, expiry (with fallback)
- 🔒 **TLS validation** — certificate status and days to expiration
- 🌐 **Hosting context** — resolved IP, ASN, hosting organization
- 🧮 **Email-readiness score (0–100)** — 🟢 high / 🟡 medium / 🔴 low, fully configurable

### 💡 Why use this Actor?

- **Avoid bad leads** — filter domains with no MX, disposable email, or weak auth
- **Protect deliverability** — catch SPF/DMARC gaps *before* campaigns go out
- **Audit lead vendors** — objectively score purchased lists at scale
- **Save SDR time** — prioritize outreach to high-scoring domains only

### 📥 Input

Configure the Actor from the **Input tab**. Only `domains` is required — everything else is optional.

#### `domains` (required)

Domains to enrich and qualify.

- URLs are automatically normalized to domains

#### `concurrency` (optional)

Controls how many domains are processed in parallel.

- Default: **10**
- Higher values are faster but use more memory

#### `scoring` (optional)

Customizes how the **email_score (0–100)** is calculated.

- If omitted, the Actor uses a production-ready default scoring model
- Use this only if you want to change how domains are ranked

#### Minimal example (most users)

```json
{
    "domains": ["example.com", "google.com"]
}
```

> ✅ Uses **default concurrency and default scoring**.
> This is enough for most SDR, lead-gen, and list QA workflows.

#### Full example (explicit defaults shown)

The example below shows **all default values**.
You do **not** need to include this unless you want to override something.

```json
{
    "domains": ["example.com", "google.com"],
    "concurrency": 10,
    "scoring": {
        "weights": {
            "mx": 30,
            "spf": 15,
            "dmarc": 10,
            "domainAge": 25,
            "tls": 15,
            "notDisposable": 5
        },
        "thresholds": {
            "high": 70,
            "medium": 40
        }
    }
}
```

> 💡 **Partial overrides are supported.**
> You can change only `thresholds.high` (for example) and keep all default weights.

### 📤 Output

Each input domain produces one result object in the default dataset.

```json
{
    "domain": "example.com",
    "has_mx": true,
    "has_spf": true,
    "has_dmarc": true,
    "tls_valid": true,
    "is_disposable": false,
    "email_score": 100,
    "email_score_label": "high",
    "email_score_emoji": "🟢",
    "resolved_ip": "104.18.27.120",
    "domain_registered_at": "1995-08-14",
    "expires_at": "2026-08-13",
    "registrar": "RESERVED-Internet Assigned Numbers Authority",
    "domain_age_days": 11101,
    "tls_expires_in_days": 71,
    "hosting_cms": "unknown",
    "asn": 13335,
    "hosting_org": "Cloudflare"
}
```

**Key fields to watch**

- `email_score`, `email_score_label`, `email_score_emoji` — primary qualification signals
- `has_mx`, `is_disposable` — fast exclusion filters
- `domain_age_days`, `expires_at`, `registrar` — trust and risk indicators
- `tls_valid`, `tls_expires_in_days` — maintenance and security signals

> Per-domain lookup failures don’t crash the run. Partial results may include `*_error` fields.

### 🧠 Tips & Best Practices

- **Interpret the score**
  - 🟢 *High*: safe for outreach
  - 🟡 *Medium*: review or enrich further
  - 🔴 *Low*: exclude from cold email

- **Fast exclusion rules**
  - `has_mx = false`
  - `is_disposable = true`
  - `email_score_label = "low"`

- **When to customize scoring**
  - Don’t customize for general B2B qualification or list QA
  - Customize if you target very new startups, need strict compliance, or want higher auth requirements

- **Performance tuning**
  - Start with `concurrency = 10`
  - Increase only if runs are slow and memory usage is low
  - Reduce concurrency first if you see timeouts

### 🔌 Integrations

This Actor fits naturally into automated lead-qualification workflows:

- **Actor-to-Actor**: Trigger this Actor from another Actor or Task, or pass its dataset to a downstream Actor for filtering, enrichment, or export.
- **Automation tools**: Run it from Zapier, Make, n8n, or similar platforms using the same JSON input as in Apify Console.
- **Data pipelines**: Connect the output dataset to integration-ready Actors to upload results to databases, spreadsheets, or internal systems.

See Apify’s integration docs for setup details.

### 🚀 Get Started

Upload a list of domains and get email-readiness scores fast.
Ideal for SDR teams, lead-gen agencies, and anyone qualifying leads before outreach.

### 🛟 Support

This Actor is actively maintained. Need help or want to customize it?

- 📬 [Contact the developer](https://apify.com/emastra)
- 🐞 [Report a bug](https://console.apify.com/actors/Apoqa4BqhD2UAIpxU/issues)
- ✨ [Request a feature](https://apify.com/emastra)

# Actor input Schema

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

List of domains to enrich. Add one domain per line, or use bulk edit. URLs will be automatically stripped to domain only.

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

Maximum number of domains to process in parallel. Higher values are faster but use more memory. Recommended: 10 for 1GB, 15-20 for 2GB+ memory.

## `scoring` (type: `object`):

Customize how email scores are calculated. Weights determine point values for each signal (default sum = 100). Thresholds determine score cutoffs for high/medium/low labels.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "google.com",
    "github.com"
  ],
  "concurrency": 10,
  "scoring": {
    "weights": {
      "mx": 30,
      "spf": 15,
      "dmarc": 10,
      "domainAge": 25,
      "tls": 15,
      "notDisposable": 5
    },
    "thresholds": {
      "high": 70,
      "medium": 40
    }
  }
}
```

# Actor output Schema

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

No description

## `results` (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 = {
    "domains": [
        "example.com",
        "google.com"
    ],
    "scoring": {
        "weights": {
            "mx": 30,
            "spf": 15,
            "dmarc": 10,
            "domainAge": 25,
            "tls": 15,
            "notDisposable": 5
        },
        "thresholds": {
            "high": 70,
            "medium": 40
        }
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("emastra/domain-intelligence").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": [
        "example.com",
        "google.com",
    ],
    "scoring": {
        "weights": {
            "mx": 30,
            "spf": 15,
            "dmarc": 10,
            "domainAge": 25,
            "tls": 15,
            "notDisposable": 5,
        },
        "thresholds": {
            "high": 70,
            "medium": 40,
        },
    },
}

# Run the Actor and wait for it to finish
run = client.actor("emastra/domain-intelligence").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": [
    "example.com",
    "google.com"
  ],
  "scoring": {
    "weights": {
      "mx": 30,
      "spf": 15,
      "dmarc": 10,
      "domainAge": 25,
      "tls": 15,
      "notDisposable": 5
    },
    "thresholds": {
      "high": 70,
      "medium": 40
    }
  }
}' |
apify call emastra/domain-intelligence --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,emastra/domain-intelligence"
        }
    }
}
```

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/Apoqa4BqhD2UAIpxU/builds/zLpiuY6J4I1CnSKTI/openapi.json