# Domain Intelligence: Age, Registrar, Expiry, DNS & Email Setup (`leadgenguy/domain-intelligence`) Actor

Bulk-check domains from official RDAP data and DNS: registration date, age, registrar, expiry, nameservers, mail provider, SPF/DMARC, parked and new-domain signals. $1 per 1,000.

- **URL**: https://apify.com/leadgenguy/domain-intelligence.md
- **Developed by:** [Mokssh jaiin](https://apify.com/leadgenguy) (community)
- **Categories:** Lead generation, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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?

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 Intelligence: Age, Registrar, Expiry, DNS & Email Setup — $1 per 1,000

Turn a list of domains into **facts and signals**: when each domain was registered and how old it is, who the registrar is, when it expires, which nameservers and DNS provider it uses, which **email provider** the company uses (Google, Microsoft 365, Zoho...), whether **SPF and DMARC** are set, and whether the site is live, parked or for sale. Data comes straight from **official RDAP registries and public DNS**, so it is stable and legal.

### Why use it

- **Lead scoring:** a domain registered 3 months ago is a brand-new company; one with Google Workspace and no DMARC is a prospect for email-security tools.
- **Expiring and expired domains:** find domains that expire in the next 60 days.
- **Available names:** `not_registered` flags domains you could register.
- **Cheap:** $1 per 1,000 domains.

### Signals

`new_domain` (under 1 year), `very_new_domain` (under 90 days), `expiring_soon`, `expired`, `not_registered`, `looks_parked`, `no_dns_service`, `weak_email_authentication`.

### Pricing

| Event | Price |
|---|---|
| Domain analyzed | $1 per 1,000 ($0.001 each) |
| Actor start | $0.00005 |

Domains whose registry could not be reached are returned with `rdapAvailable: false` and are **not charged**. Domains filtered out by "only these signals" are not charged either. Free Apify accounts are limited to **50 domains per run**.

### Input

```json
{ "domains": ["stripe.com", "https://www.apify.com/pricing", "someone@bbc.co.uk"], "checkWebsite": true, "onlySignals": ["new_domain", "expiring_soon"] }
```

### Output

```json
{
  "domain": "apify.com", "registered": true,
  "registration": { "registeredOn": "2009-04-10", "ageDays": 6344, "expiresOn": "2027-04-10", "daysToExpiry": 176, "registrar": "Amazon Registrar, Inc.", "dnssec": false, "nameservers": ["ns-1.awsdns-01.org"] },
  "dns": { "hasWebsiteIp": true, "mail": { "hasMailServer": true, "provider": "google", "spf": true, "dmarc": true }, "dnsProvider": "aws" },
  "website": { "reachable": true, "title": "Apify: Full-stack web scraping platform", "looksParked": false },
  "signals": [], "rdapAvailable": true
}
```

### Honest limits

- Some country-code TLDs do not offer RDAP. You still get the DNS and website data; registration fields are empty.
- Registrant names and emails are hidden by privacy rules for most domains, so this Actor does not return owners.
- Registries rate-limit: very large lists take time.

### Feedback and reviews

Found a bug, or need a signal added? Open an issue on this Actor's **Issues** tab and it will be looked at quickly. If this Actor saved you time, a short and honest review helps other people find it. Thank you!

### Legal

Uses public RDAP and DNS data only.

# Actor input Schema

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

Domains, URLs or email addresses (the domain is taken from them). Subdomains are reduced to the registered domain. Up to 50,000 per run (free Apify plans: 50 per run).

## `checkWebsite` (type: `boolean`):

Loads the homepage to read its title and detect parked or for-sale pages. Turn off for faster, DNS-only checks.

## `onlySignals` (type: `array`):

Return only domains with at least one of these signals. Filtered-out domains are not charged.

## Actor input object example

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

# Actor output Schema

## `jobs` (type: `string`):

All scraped jobs as a dataset.

# 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": [
        "stripe.com",
        "apify.com",
        "bbc.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadgenguy/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": [
        "stripe.com",
        "apify.com",
        "bbc.co.uk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("leadgenguy/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": [
    "stripe.com",
    "apify.com",
    "bbc.co.uk"
  ]
}' |
apify call leadgenguy/domain-intelligence --silent --output-dataset

```

## MCP server setup

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