# Domain Intelligence (WHOIS RDAP, DNS, SPF, DMARC, TLS) (`northpine-studio/domain-intel`) Actor

Bulk domain lookup: registrar, creation/expiry dates, nameservers (RDAP), DNS records, mail provider, SPF/DMARC/DKIM/MTA-STS checks, TLS certificate expiry, and an email-authentication score. No API keys.

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

## Pricing

$2.00 / 1,000 domain analyzeds

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: WHOIS (RDAP), DNS, SPF, DMARC and TLS in one run

Paste a list of domains and get one structured row per domain: who registered it and when, where it
expires, its DNS records, which mail provider it uses, whether SPF / DMARC / DKIM / MTA-STS are set up,
how long its TLS certificate has left, and a 0-100 **email-authentication score**. No API keys, no
proxies, no browser. It uses open protocols only (RDAP, DNS, a TLS handshake).

### What you get per domain

- **Registration (RDAP):** registrar and IANA ID, created / updated / expires dates, domain age in days,
  days to expiry, EPP status codes, nameservers, DNSSEC flag. Registrant contact details are **not**
  returned (they are redacted by most registries and we do not collect them).
- **DNS:** A, AAAA, MX (sorted by priority), NS, TXT, CAA.
- **Email setup:** mail provider detected from MX (Google Workspace, Microsoft 365, Proofpoint, Zoho, ...),
  SPF record with parsed policy and DNS-lookup count, DMARC record with policy / pct / rua, DKIM selectors
  found at common names, MTA-STS, TLS-RPT, BIMI.
- **Email-authentication score (0-100):** transparent weights plus plain-English notes such as
  "DMARC p=none (monitor only)". It measures DNS hygiene, not deliverability or reputation.
- **TLS certificate:** issuer, subject, valid from / to, days remaining, subject alternative names,
  negotiated protocol, and whether the chain validated.

### Use cases

Monitoring your own domain portfolio and expiries, checking your own or your clients' SPF/DMARC/CAA
setup, security and compliance sweeps, vendor due diligence, and spotting freshly registered domains.
Do not use the output to build marketing or solicitation lists (see "Registry terms" below).

### Input

| Field | Meaning |
|---|---|
| `domains` | Domains, URLs or emails; the domain is extracted (lowercased, scheme/path/user part and a leading `www.` removed), then de-duplicated, so you are billed once per distinct domain |
| `includeRegistration`, `includeDns`, `includeEmailAuth`, `includeTls` | Switch sections off for speed |
| `concurrency` | 1-10 domains in parallel (default 5) |

Example input: `{ "domains": ["github.com", "https://www.apify.com/pricing", "bbc.co.uk"] }`

### Pricing

Pay per event: **$0.002 per domain analysed**. Invalid inputs are not charged and are not written to the dataset (they are listed in the run log and in the `INVALID_INPUTS` key-value record). Domains where nothing at all is found (unregistered, no DNS, no TLS) are also not charged and not output. The run stops cleanly when your max-charge limit is reached.
You also pay normal Apify platform usage (typically a fraction of a cent per domain).

### Notes and limits

- RDAP servers are queried directly via the IANA bootstrap file with a descriptive User-Agent, a 10 s
  timeout, up to 3 retries with backoff (honouring Retry-After) and a minimum 300 ms gap per registry host. If a
  registry still refuses, the row carries `registrationError` while DNS/TLS sections still return.
- Maximum 500 distinct domains per run (extras are dropped and logged); split larger lists into several runs.
- Internationalised (unicode) domain names are not supported; pass the punycode (`xn--`) form. Unicode input is reported as invalid.
- DNS uses the resolver of the machine the Actor runs on; an empty DNS section can mean a resolver failure as well as "no records".
- Not every TLD publishes RDAP data (some ccTLDs have no RDAP server): you get `registrationError`.
- DKIM can only be found by guessing selector names; "none found" does not prove DKIM is absent.
- This Actor does not log in anywhere, bypass anything, or send email.

### Registry terms (please read)

Registration data comes from public RDAP servers, which publish their own terms. For example, Verisign
(.com/.net) states in its RDAP terms of service that the data may not be used to "allow, enable, or
otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via
e-mail, telephone, or facsimile", nor to "enable high volume, automated, electronic processes" that send
queries to registry or registrar systems (full text:
https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml).
Other registries have their own terms. You are responsible for using the output within them. This Actor
keeps load low (batch cap, per-host spacing) and does not collect registrant contact data, but it cannot
make a use that the terms forbid acceptable. Turn off "Registration (RDAP)" if you only need DNS/TLS data.

Built by Northpine Studio. Questions or a missing field? Open an issue on the Actor page.

# Actor input Schema

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

Domains, URLs or emails (the domain is extracted). One result per unique domain; max 500 distinct domains per run. Nothing found = not charged.

## `includeRegistration` (type: `boolean`):

Registrar, created/expires dates, status, nameservers, DNSSEC.

## `includeDns` (type: `boolean`):

A, AAAA, MX, NS, TXT, CAA.

## `includeEmailAuth` (type: `boolean`):

Mail provider, SPF, DMARC, DKIM (common selectors), MTA-STS, BIMI, readiness score.

## `includeTls` (type: `boolean`):

Issuer, validity dates, days remaining, SANs.

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

Domains processed in parallel (1-10).

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "apify.com"
  ],
  "includeRegistration": true,
  "includeDns": true,
  "includeEmailAuth": true,
  "includeTls": true,
  "concurrency": 5
}
```

# Actor output Schema

## `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",
        "apify.com"
    ]
};

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

# Run the Actor and wait for it to finish
run = client.actor("northpine-studio/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": [
    "example.com",
    "apify.com"
  ]
}' |
apify call northpine-studio/domain-intel --silent --output-dataset

```

## MCP server setup

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