# Domain Intelligence Scraper — WHOIS + DNS Posture — Prime Sieve (`primesieve/domain-intelligence-scraper`) Actor

One run gives you both WHOIS-style registration data and live DNS posture for any domain list: registrar, created/expiry dates, nameservers, DNSSEC, abuse contact, plus A/AAAA/MX/TXT/SPF/DMARC/CAA and privacy-protection flags. No API key, keyless RDAP + DNS-over-HTTPS.

- **URL**: https://apify.com/primesieve/domain-intelligence-scraper.md
- **Developed by:** [Prime Sieve](https://apify.com/primesieve) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event + usage

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Domain Intelligence Scraper — WHOIS + DNS Posture

Get **complete domain registration data AND live DNS posture in one run** — no API key, no proxy, no monthly fee. Built on keyless official **RDAP** (the structured JSON successor to WHOIS) and **DNS-over-HTTPS**.

Built by **Prime Sieve** — the team behind the Remote Signal newsletter: https://remotesignal.substack.com

### What you get per domain

**Registration (RDAP — official IANA/Verisign, not scraped text):**

- Registrar name
- Created / updated / expires dates (ISO 8601)
- **Days until expiry** + `expiry_soon` flag (≤60 days)
- Domain status codes (clientTransferProhibited, etc.)
- Nameservers
- DNSSEC status (signed/unsigned) from RDAP
- **Registrar abuse contact emails**

**DNS posture (DNS-over-HTTPS via dns.google):**

- A / AAAA (IPv4 / IPv6)
- MX (mail servers)
- TXT (SPF, domain-verification tokens)
- NS / SOA / CNAME / CAA
- **SPF record extracted**
- **DMARC record extracted** (separate `_dmarc.` query)
- DS presence (DNSSEC at delegation)
- **Privacy-protection flag** (domain behind Google/Cloudflare/Workplace privacy when a verification TXT is present)

### Why it's different

Most "WHOIS scraper" actors return only raw registrant text. This actor gives you:

1. **Structured RDAP fields** — registrar, dates, nameservers, DNSSEC — not mangled WHOIS text.
2. **DNS posture in the same dataset** — SPF/DMARC/CAA/privacy mean you can actually **run compliance and security scans** (email spoofing risk, DNSSEC coverage, expiry risk) without a second tool.
3. **Bulk-ready** — paste hundreds or thousands of domains; one row per domain.

### Who pays for this

- **Security teams** — phishing-domain watchlists, expired-or-soon-to-expire infrastructure, SPF/DMARC posture audits, DNSSEC coverage checks
- **DevOps / SRE** — DNS change detection, nameserver/registrar tracking across a fleet
- **Domain investors / portfolio managers** — expiry alerts, registrar comparison
- **Compliance / brand protection** — impersonation domains, abuse-contact collection
- **SEO / digital PR** — expired-domain discovery, backlink-domain vetting

### Input

```json
{
  "domains": ["example.com", "google.com", "stripe.com"],
  "includeDns": true,
  "normalizeDomains": true
}
```

- `domains`: array of domains (auto-strips `https://` and `www.`)
- `includeDns`: set false for WHOIS-only (fewer calls, cheaper)
- `normalizeDomains`: validation + normalization

### Sample Output

```json
{
  "domain": "google.com",
  "registrar": "MarkMonitor Inc.",
  "created": "1997-09-15T04:00:00Z",
  "expires": "2028-09-14T04:00:00Z",
  "days_to_expiry": 792,
  "expiry_soon": false,
  "nameservers": ["ns1.google.com", "ns2.google.com"],
  "rdap_dnssec": null,
  "spf": "v=spf1 include:_spf.google.com ~all",
  "dmarc": "v=DMARC1; p=reject; rua=mailto:mailauth-reports@google.com",
  "privacy_protection": false
}
```

### Pricing

Pay per **domain lookup** (`domain-lookup` event). WHOIS (RDAP) is always included; DNS adds two requests per domain. Competitors charge $1–10 per 1K raw WHOIS rows — we ship structured fields plus DNS posture for less, and you pay only for domains we actually resolve.

**No API keys. No proxies. No monthly fees.** Built on the public keyless IANA RDAP ecosystem and dns.google DNS-over-HTTPS.

Example use cases:

- Watchlist of 10K phishing candidates → 10K rows, full posture, one run
- Fleet DNS audit → exports straight to CSV/JSON

### Remote Signal

We built this actor to power our own domain-spoofing watchlist. Get the newsletter with tools, signals and data tips: **https://remotesignal.substack.com**

# Actor input Schema

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

List of domains to look up (e.g. example.com). Bulk lists supported. Auto-normalizes (strips https:// and www).

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

Also resolve DNS (A/AAAA/MX/TXT/NS/SOA/CAA, SPF, DMARC, DS/DNSSEC). Set false for WHOIS-only.

## `normalizeDomains` (type: `boolean`):

Strip http(s):// and www. prefix, lowercase, validate before lookup.

## Actor input object example

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

# Actor output Schema

## `domain` (type: `string`):

Normalized domain (lowercase).

## `registrar` (type: `string`):

Registrar name from RDAP.

## `created` (type: `string`):

ISO registration date.

## `updated` (type: `string`):

ISO last-changed date.

## `expires` (type: `string`):

ISO expiration date.

## `days_to_expiry` (type: `string`):

Integer days until expiration, or null.

## `expiry_soon` (type: `string`):

True when days\_to\_expiry <= 60.

## `statuses` (type: `string`):

RDAP domain status codes.

## `nameservers` (type: `string`):

NS hostnames.

## `rdap_dnssec` (type: `string`):

signed / unsigned / null from secureDNS.delegationSigned.

## `abuse_emails` (type: `string`):

Registrar abuse contact emails.

## `rdap_error` (type: `string`):

HTTP status or error string when RDAP lookup failed.

## `dns_a` (type: `string`):

IPv4 addresses.

## `dns_aaaa` (type: `string`):

IPv6 addresses.

## `dns_mx` (type: `string`):

Mail exchange records.

## `dns_txt` (type: `string`):

TXT records (SPF, verifications).

## `dns_ns` (type: `string`):

NS records from DNS.

## `dns_soa` (type: `string`):

SOA record.

## `dns_cname` (type: `string`):

CNAME record.

## `dns_caa` (type: `string`):

CAA records.

## `dns_has_ds` (type: `string`):

True when DS records present (DNSSEC at delegation).

## `spf` (type: `string`):

SPF TXT record if present.

## `dmarc` (type: `string`):

DMARC TXT record (with v=DMARC1) if present.

## `privacy_protection` (type: `string`):

True when a domain-verification TXT for a known privacy provider is present.

## `dns_error` (type: `string`):

Error string when DNS lookup failed.

# 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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("primesieve/domain-intelligence-scraper").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"] }

# Run the Actor and wait for it to finish
run = client.actor("primesieve/domain-intelligence-scraper").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 call primesieve/domain-intelligence-scraper --silent --output-dataset

```

## MCP server setup

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

```

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/ejfYdr2bbUdSEyXCx/builds/bXBl39FbaYl3knaTQ/openapi.json