# Domain Intelligence: WHOIS/RDAP, DNS, SSL & Security Headers (`arthursbuisness/domain-intelligence-rdap-dns-ssl-headers`) Actor

- **URL**: https://apify.com/arthursbuisness/domain-intelligence-rdap-dns-ssl-headers.md
- **Developed by:** [Arthur](https://apify.com/arthursbuisness) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 analysed domains

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?

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: WHOIS/RDAP, DNS, SSL & Security Headers

One run, one row per domain, everything you normally collect from four different tools: **registration data** (registrar, creation/expiry dates, status codes, nameservers), **DNS** (A/AAAA/NS/MX/TXT/CAA with parsed SPF, DMARC and DKIM), **HTTPS reachability** with the full redirect chain and a security-header score, the **TLS certificate** (issuer, expiry, days left, SANs, chain verification) and an **availability heuristic** for unregistered names. Built for domain portfolio monitoring, lead enrichment, due diligence, security audits and expiring-domain hunting.

All data comes from public, official sources over plain HTTPS: RDAP (the successor of WHOIS, served by the registries themselves via the IANA bootstrap at rdap.org), DNS-over-HTTPS (Google DNS with Cloudflare fallback) and a direct request to the site. No login, no proxies, no third-party API keys.

### What you get

| group | fields |
|---|---|
| identity | `domain`, `domain_ascii` (punycode), `valid`, `checked_at` |
| registration (RDAP) | `registered`, `registrar`, `registrar_iana_id`, `registrar_url`, `created`, `updated`, `expires`, `days_to_expiry`, `age_days`, `status[]` (EPP codes such as `client transfer prohibited`), `registrant`, `registrant_org`, `registrant_country` (only where the registry publishes them), `abuse_email`, `rdap_source` |
| DNS | `nameservers[]`, `a[]`, `aaaa[]`, `ns[]`, `mx[]` (priority + host), `mx_present`, `null_mx`, `txt[]`, `caa[]`, `dnssec`, `nxdomain` |
| email auth | `spf_present`, `spf_record`, `spf_all` (`-all`/`~all`/…), `dmarc_present`, `dmarc_policy` (`none`/`quarantine`/`reject`), `dmarc_record`, `dkim_present`, `dkim_selectors_found[]` (active keys only) |
| SaaS hints | `service_hints[]` — providers revealed by verification TXT records and SPF includes (Google Workspace, Microsoft 365, SendGrid, HubSpot, Stripe, Shopify, Atlassian, Salesforce, Zendesk, Mailchimp, Amazon SES …) |
| HTTP | `https_ok`, `http_status`, `final_url`, `redirect_chain[]`, `redirects`, `http_to_https`, `server`, `powered_by`, `title`, `response_ms`, `security_headers{}` (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP, CORP, X-XSS-Protection), `security_score` (0–100), `security_grade` (A–F) |
| TLS | `tls_ok`, `tls_verify` (openssl chain result), `tls_issuer`, `tls_subject`, `tls_not_before`, `tls_not_after`, `tls_days_left`, `tls_sans[]`, `tls_san_count`, `tls_protocol` |
| availability | `available` (`true` / `false` / `null` = unknown) + `availability_note` explaining the evidence |
| diagnostics | `sections_failed[]`, `error` (only when both RDAP and DNS failed — such rows are **not billed**) |

#### Availability heuristic

`available: true` only when the registry's RDAP server has **no object** for the name **and** DNS returns NXDOMAIN. If RDAP is not offered for the TLD (some ccTLDs) the field is `null` with a note. Always confirm at a registrar before relying on it.

### Input

| field | default | meaning |
|---|---|---|
| `domains` | — | domain names (URLs / emails accepted, host part is used, `www.` stripped, duplicates skipped) |
| `includeRdap` / `includeDns` / `includeHttp` / `includeTls` | true | switch sections off to speed up runs |
| `dkimSelectors` | 15 common selectors | which `<selector>._domainkey` names to probe |
| `concurrency` | 5 | domains processed in parallel (1–10) |
| `timeoutSecs` | 15 | per request |
| `maxItems` | 1000 | cost cap |

Example input:

```json
{ "domains": ["github.com", "shopify.com", "example.com", "this-domain-should-not-exist-98765.com"] }
```

Example row (abridged):

```json
{"domain":"github.com","registered":true,"registrar":"MarkMonitor Inc.","created":"2007-10-09T18:20:50Z","expires":"2026-10-09T18:20:50Z","days_to_expiry":42,
 "status":["client delete prohibited","client transfer prohibited","client update prohibited"],"nameservers":["dns1.p08.nsone.net","…"],
 "mx_present":true,"spf_all":"~all","dmarc_policy":"quarantine","dkim_selectors_found":["google","selector1","k1","s1"],
 "service_hints":["Atlassian","DocuSign","Google Workspace/Search Console","Microsoft 365","Salesforce","Stripe","Zendesk"],
 "https_ok":true,"final_url":"https://github.com/","server":"github.com","security_score":90,"security_grade":"A",
 "tls_ok":true,"tls_issuer":"Sectigo Limited — Sectigo Public Server Authentication CA DV E36","tls_days_left":34,"available":false}
```

### Pricing

Pay per event: **$0.002 per domain** ($2 per 1,000). Charged only for rows successfully written to the dataset; rows whose RDAP *and* DNS lookups both failed are stored with an `error` and are free. A full four-section check takes 1–4 seconds per domain; 1,000 domains ≈ 5–8 minutes at 256 MB.

### Limitations (honest list)

- **RDAP coverage**: all gTLDs (.com, .net, .org, .io, .app …) and most ccTLDs answer RDAP. A few ccTLDs (e.g. .de, .ch, .it) do not offer RDAP or return no registrant/date details; those rows have `rdap_ok: false` or partial registration data, and `available` becomes `null` when the domain is also NXDOMAIN. Registrant names are redacted by most registries since GDPR.
- **Expiry date** is missing for registries that do not publish it (e.g. `.nl`).
- **DKIM** can only be found for the selectors probed (defaults cover the major providers; add your own).
- **Security score** rates response headers of the final page only; it is not a penetration test.
- **TLS** is checked on port 443 only; no mail-server (SMTP) checks are performed.
- The site fetch is a plain GET without JavaScript; bot-protected sites may return 403 (recorded as such).

Not affiliated with ICANN, any registry or registrar; this actor reads public protocol data only.

# Actor input Schema

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

Domain names to analyse, one per line. URLs and email addresses are accepted (the host part is used); 'www.' is stripped.

## `includeRdap` (type: `boolean`):

Registrar, creation/expiry/update dates, EPP status codes, nameservers, registrant (where the registry publishes it) via the public RDAP protocol (rdap.org bootstrap).

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

Resolved over DNS-over-HTTPS (Google DNS, Cloudflare fallback). Includes DNSSEC flag, null-MX detection and SaaS hints from verification TXT records.

## `includeHttp` (type: `boolean`):

GET https://domain/ (falls back to http://), follows up to 8 redirects, records status, final URL, server header, page title, HSTS/CSP/X-Frame-Options/etc. and a 0–100 security-header score.

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

Issuer, subject, validity window, days left, SANs, protocol and chain verification result (openssl on port 443).

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

Selectors checked at <selector>.\_domainkey.<domain>. Default covers Google, Microsoft 365, Mailchimp/Mandrill, Amazon SES, Fastmail, Zoho, Proton, Mailjet, Campaign Monitor.

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

1–10. Each domain already runs its four sections in parallel.

## `timeoutSecs` (type: `integer`):

Applies to each DNS, RDAP, HTTP and TLS request.

## `maxItems` (type: `integer`):

Stop after this many domains (cost control).

## Actor input object example

```json
{
  "domains": [
    "github.com",
    "shopify.com",
    "example.com",
    "this-domain-should-not-exist-98765.com"
  ],
  "includeRdap": true,
  "includeDns": true,
  "includeHttp": true,
  "includeTls": true,
  "dkimSelectors": [
    "google",
    "selector1",
    "selector2",
    "k1",
    "default",
    "dkim",
    "mail",
    "s1",
    "mandrill",
    "amazonses",
    "fm1",
    "zmail",
    "protonmail",
    "mailjet",
    "cm"
  ],
  "concurrency": 5,
  "timeoutSecs": 15,
  "maxItems": 1000
}
```

# Actor output Schema

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

All items as JSON

## `resultsCsv` (type: `string`):

Same dataset as CSV — open in Excel/Sheets

# 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": [
        "github.com",
        "shopify.com",
        "example.com",
        "this-domain-should-not-exist-98765.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("arthursbuisness/domain-intelligence-rdap-dns-ssl-headers").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": [
        "github.com",
        "shopify.com",
        "example.com",
        "this-domain-should-not-exist-98765.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("arthursbuisness/domain-intelligence-rdap-dns-ssl-headers").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": [
    "github.com",
    "shopify.com",
    "example.com",
    "this-domain-should-not-exist-98765.com"
  ]
}' |
apify call arthursbuisness/domain-intelligence-rdap-dns-ssl-headers --silent --output-dataset

```

## MCP server setup

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

```

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/wTO4FBnokoAM9A0tE/builds/54nd6u8lYWR6Dclc6/openapi.json