# Domain Intel: WHOIS/RDAP, DNS, SPF/DMARC, SSL & Tech Stack (`reynolds/domain-intel`) Actor

Domain lookup in one call: WHOIS-style RDAP registration, DNS records, SPF/DMARC/DKIM email-security grade, live SSL/TLS certificate, website tech stack and optional subdomains. Bulk or as an MCP tool for AI agents. $0.005 per domain.

- **URL**: https://apify.com/reynolds/domain-intel.md
- **Developed by:** [Reece Reynolds](https://apify.com/reynolds) (community)
- **Categories:** Developer tools, SEO tools, MCP servers
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 domain analyseds

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 Intel: WHOIS/RDAP, DNS, SPF/DMARC, SSL & Tech Stack API

**Domain lookup API for AI agents and data pipelines:** WHOIS-style registration data via RDAP, all DNS records, an SPF/DMARC/DKIM email-security grade, the live SSL/TLS certificate, the website's tech stack and optional subdomains, in one JSON result per domain. Use it as an MCP tool in Claude or Cursor, or in bulk from the API, n8n, Make or Zapier.

**One domain in, one clean JSON profile out.** Registration, DNS, email-security grade, live TLS certificate and the website's tech stack in a few seconds, plus optional certificate-transparency history with subdomains. Public sources only. Built for AI agents, lead-enrichment pipelines, security triage and vendor checks.

**Price: $0.005 per domain** (pay per event). No start fee. Invalid domains, unregistered or non-resolving domains, and lookups where every check fails are free. Duplicates in one run are billed once.

Pricing examples: 100 domains = $0.50, 1,000 domains = $5, 10,000 domains = $50. An agent checking one domain pays half a cent. Apify's free plan includes monthly platform credit, enough for hundreds of lookups.

### What you get per domain

| Section | What is in it | Source |
|---|---|---|
| `registration` | Registrar (name, IANA ID, abuse contact), created / updated / expiry dates, domain age, days to expiry, status codes, nameservers, DNSSEC delegation | RDAP (the official successor to WHOIS), via the IANA bootstrap registry |
| `dns` | A, AAAA, CNAME, NS, MX, TXT, CAA, SOA, DNSSEC validation flag | DNS over HTTPS (Cloudflare, Google fallback) |
| `emailSecurity` | SPF (qualifier, includes, lookup count, issues), DMARC (policy, pct, reporting), DKIM keys on 20 common selectors, MTA-STS policy, TLS-RPT, BIMI, a 0-100 score and an A-F grade | DNS + the domain's MTA-STS policy file |
| `tls` | Live certificate: issuer, validity, days left, SANs, key type, fingerprint, chain, trust and hostname match, negotiated TLS version | Direct TLS handshake on port 443 |
| `certificateTransparency` (optional, off by default) | Total certificates, first seen, last issued, issuer mix, discovered subdomains, wildcards, newest certificates | crt.sh (Cert Spotter fallback) |
| `techStack` | CDN, hosting, web server, CMS, framework, analytics, ads, chat, payments, consent and monitoring tools, plus mail provider, email senders, DNS host and SaaS verified on the domain. Each with a category, a 0-100 confidence and the signals that matched. Page title, security headers | One GET of the homepage (headers, cookies, script/link URLs, HTML), DNS (MX, SPF, TXT, NS, CNAME), robots.txt and security.txt. No browser |
| `summary` | Flat one-line view: registrar, dates, DNS and mail provider, email grade, DMARC policy, TLS issuer and expiry, subdomain count, technologies | Derived |

Each section has `ok`, `ms` and either `data` or `error`, so one slow or broken source never sinks the rest.

### Privacy

Registrant, admin, technical and billing contacts are **never returned**, even when a registry publishes them. Only the registrar (a business) is kept, plus a flag saying whether the registry redacted registrant data. No WHOIS scraping, no logins, no proxies.

### Input

```json
{
  "domains": ["stripe.com", "https://www.bbc.co.uk/news", "ceo@shopify.com"],
  "modules": ["rdap", "dns", "email", "tls", "tech"],
  "includeCertificateHistory": false,
  "dkimSelectors": ["s1024"],
  "ctMaxRecent": 20,
  "ctMaxSubdomains": 200,
  "maxConcurrency": 5
}
```

Only `domains` is required. URLs and email addresses are reduced to their hostname. Leave `modules` empty for all the fast checks.

#### Certificate history is optional

Certificate-transparency history (`certificateTransparency`: total certificates, first seen, issuers, discovered subdomains) is **off by default** because it is much slower: crt.sh can take up to about 60 seconds per domain and is sometimes unavailable. Turn it on with `"includeCertificateHistory": true` (or by listing `ct` in `modules`). The price stays $0.005 per domain either way. Without it a typical domain takes 2-4 seconds.

### Output (trimmed)

```json
{
  "domain": "stripe.com",
  "success": true,
  "summary": {
    "registrar": "SafeNames Ltd.",
    "registeredAt": "1995-09-12T04:00:00Z",
    "domainAgeDays": 11368,
    "dnsProviderHint": "Amazon Route 53",
    "mailProviderHint": "Google Workspace",
    "emailSecurityGrade": "A",
    "dmarcPolicy": "reject",
    "tlsIssuer": "DigiCert, Inc.",
    "tlsDaysToExpiry": 195,
    "ctSubdomains": 73,
    "technologies": ["nginx", "Next.js"]
  },
  "registration": { "ok": true, "ms": 391, "data": { "...": "..." } },
  "emailSecurity": { "ok": true, "ms": 675, "data": { "grade": "A", "score": 85, "spf": {}, "dmarc": {}, "dkim": {}, "mtaSts": {} } }
}
```

### Use with AI agents (MCP)

Through the Apify MCP server, your agent gets this Actor as a tool and can answer questions like "Is acme.com's DMARC set to reject?", "Who hosts this domain and when does its certificate expire?" or "Which of these 20 leads use Google Workspace?".

Add this to Claude Desktop (`claude_desktop_config.json`), Cursor (`.cursor/mcp.json`), VS Code or any client that supports remote MCP servers:

```json
{
  "mcpServers": {
    "domain-intel": {
      "url": "https://mcp.apify.com/?tools=reynolds/domain-intel"
    }
  }
}
```

The client opens an Apify sign-in the first time. To use a token instead, add `"headers": { "Authorization": "Bearer <APIFY_TOKEN>" }`. Claude Code: `claude mcp add --transport http domain-intel "https://mcp.apify.com/?tools=reynolds/domain-intel"`. Local (stdio) clients: `npx -y @apify/actors-mcp-server --tools reynolds/domain-intel` with `APIFY_TOKEN` in the environment.

Pair it with [Company Hiring Signals](https://apify.com/reynolds/company-hiring-signals) for account research: `?tools=reynolds/domain-intel,reynolds/company-hiring-signals`.

### Integrations: API, n8n, Make, Zapier, LangChain

- **REST API** (run and get results in one call):

  ```bash
  curl -X POST "https://api.apify.com/v2/acts/reynolds~domain-intel/run-sync-get-dataset-items" \
    -H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
    -d '{"domains": ["stripe.com", "shopify.com"]}'
  ```

- **n8n**: add the Apify node, choose "Run an Actor and get dataset", Actor `reynolds/domain-intel`, input `{"domains": ["{{ $json.website }}"]}`. Useful for enriching CRM leads or alerting on certificates close to expiry.

- **Make** and **Zapier**: use the Apify app's "Run an Actor" action with the same Actor and input, then map `summary` fields into your sheet or CRM.

- **LangChain** (Python):

  ```python
  from langchain_apify import ApifyActorsTool
  domain_tool = ApifyActorsTool("reynolds/domain-intel")
  ```

### Good to know

- **Speed**: with the defaults a domain takes about 2-4 seconds. Certificate history (opt-in) depends on crt.sh, a free community service that can take 30-60 seconds for big domains or be briefly down; we then fall back to Cert Spotter (partial: currently unexpired certificates, first page only) and mark the result `partial`. To be a good citizen we send crt.sh one request at a time, so in large runs most domains get the Cert Spotter view. Leave it off unless you need it.
- **DKIM**: DNS cannot list DKIM keys, so we probe 20 common selectors. "None found" does not prove DKIM is off. Add selectors you know in `dkimSelectors`.
- **RDAP coverage**: all gTLDs, every ccTLD in the IANA RDAP registry, plus .de, .io, .co, .me, .us, .ch, .sh and .ac via their registries' own RDAP servers. Some ccTLDs (for example .it, .es, .se, .jp, .eu) have no public RDAP server; for those `registration` fails with a clear error and the other sections still run.
- **Tech stack** is a light fingerprint from the homepage only (no crawling, no JavaScript execution), so client-side-only tools can be missed.

### FAQ

**Is this a WHOIS lookup?** It uses RDAP, the official, structured successor to WHOIS run by the same registries. You get registrar, dates, status and nameservers, without personal contact data.

**Can I check SPF, DKIM and DMARC in bulk?** Yes. Send up to thousands of domains in `domains`; each gets an `emailSecurity` section with a 0-100 score and an A-F grade.

**Does it find subdomains?** Yes, when you turn on `includeCertificateHistory`. Subdomains come from certificate-transparency logs (crt.sh, with Cert Spotter as fallback).

**How fast is it?** About 2-4 seconds per domain with the defaults, with several domains processed in parallel.

**What if one check fails?** The others still run. Each section has its own `ok` flag and `error`. If every check fails, you are not charged.

### Use cases

Lead enrichment (company age, mail provider, stack), email deliverability and spoofing audits, vendor and phishing-domain triage, attack-surface discovery via CT subdomains, certificate expiry monitoring, and agent tool calls that need "tell me about this domain" in one step.

### Support

Open an issue on the Actor's Issues tab. Responses within 2 working days.

# Actor input Schema

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

Domains to analyse. URLs and email addresses are accepted and reduced to their hostname. Duplicates are removed and billed once.

## `modules` (type: `array`):

Which checks to run. Leave empty for the defaults: everything except certificate history. Price is the same either way. Output keys per module: rdap -> registration, dns -> dns, email -> emailSecurity, tls -> tls, ct -> certificateTransparency, tech -> techStack. Each has ok, data, error, ms and source.

## `includeCertificateHistory` (type: `boolean`):

Adds certificate-transparency history: total certificates, first seen, issuers, discovered subdomains. Off by default because crt.sh can take up to ~60 seconds per domain and is sometimes unavailable. Same price per domain. Output: adds certificateTransparency and summary.ctCertificates, ctSubdomains and ctFirstSeen.

## `dkimSelectors` (type: `array`):

DKIM keys cannot be listed from DNS. 20 common selectors are always probed; add any you know (e.g. from an email header) here.

## `ctMaxRecent` (type: `integer`):

How many of the newest CT-logged certificates to include in full.

## `ctMaxSubdomains` (type: `integer`):

Cap on subdomain names returned from certificate transparency (the total count is always reported).

## `maxConcurrency` (type: `integer`):

Domains processed in parallel. Certificate-transparency lookups are always serialised to respect crt.sh limits.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "bbc.co.uk",
    "shopify.com"
  ],
  "modules": [],
  "includeCertificateHistory": false,
  "dkimSelectors": [],
  "ctMaxRecent": 20,
  "ctMaxSubdomains": 200,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

All dataset items, one per domain. Opens the Overview view in Console.

## `emailSecurity` (type: `string`):

SPF, DMARC, DKIM and MTA-STS details with the A-F grade per domain.

## `infrastructure` (type: `string`):

Registrar, domain age, DNSSEC, nameservers, mail provider and TLS certificate per domain.

# 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",
        "bbc.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("reynolds/domain-intel").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",
        "bbc.co.uk",
    ] }

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

```

## MCP server setup

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

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/MZ4FOVNOSf3beP327/builds/qAjjA5wmk0BLvp7z6/openapi.json