# Domain WHOIS, DNS and SSL Expiry Lookup (RDAP) (`pistachio_implementation/domain-whois-dns-ssl-lookup`) Actor

Bulk domain lookup from official sources. Registrar, creation date, age and expiry date via RDAP, the modern WHOIS; A, MX, NS, TXT, SPF and DMARC records; and the SSL certificate issuer and days to expiry. $1.50 per 1,000 domains.

- **URL**: https://apify.com/pistachio\_implementation/domain-whois-dns-ssl-lookup.md
- **Developed by:** [Hay Equipos](https://apify.com/pistachio_implementation) (community)
- **Categories:** Developer tools, SEO tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 domain looked ups

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 WHOIS, DNS and SSL Expiry Lookup (RDAP)

Give it a list of domains or URLs. For each one you get the registrar, the date the domain was registered, its age, its expiry date, its DNS records (A, AAAA, MX, NS, TXT, CAA, SPF, DMARC) and its SSL certificate (issuer, expiry date, days left, trusted or not). One row per domain, one clean schema.

Everything comes from official public sources: the registry's RDAP service (the modern, structured replacement for WHOIS, found through the IANA bootstrap file), public DNS, and a TLS handshake with the site. No website is scraped.

**Price: $1.50 per 1,000 domains**, all three checks included. Domains that return nothing are free.

### Good for

- **Renewal and expiry monitoring:** domains and certificates expiring in the next 30 days, across a whole portfolio.
- **Lead qualification:** domain age and whether a company domain accepts email, before you enrich or contact.
- **Fraud and trust checks:** a domain registered last week with no DMARC is a red flag.
- **Email deliverability audits:** SPF, DMARC policy and MX provider for your own and your clients' domains.
- **Security reviews:** certificate issuer, expired or untrusted certificates, CAA records.

### Input

```json
{
  "domains": ["apify.com", "https://www.bbc.co.uk/news", "wikipedia.org"],
  "whois": true,
  "dns": true,
  "ssl": true
}
```

URLs and subdomains are fine. The registrable domain is worked out with the public suffix list, so `https://www.bbc.co.uk/news` is looked up as `bbc.co.uk` for WHOIS and DNS, while the SSL check uses the exact host `www.bbc.co.uk`. Turn off any check you do not need.

### Output example

```json
{
  "input": "wikipedia.org",
  "domain": "wikipedia.org",
  "success": true,
  "rdapStatus": "ok",
  "isRegistered": true,
  "registrar": "MarkMonitor Inc.",
  "registrarIanaId": "292",
  "createdAt": "2001-01-13T00:12:14.754Z",
  "expiresAt": "2027-01-13T00:12:14.000Z",
  "domainAgeDays": 9388,
  "daysUntilExpiry": 107,
  "statuses": ["client delete prohibited", "client transfer prohibited", "client update prohibited"],
  "nameservers": ["ns0.wikimedia.org", "ns1.wikimedia.org", "ns2.wikimedia.org"],
  "dnssec": false,
  "aRecords": ["208.80.154.224"],
  "mxRecords": ["10 mx-in1001.wikimedia.org", "10 mx-in2001.wikimedia.org"],
  "spfRecord": "v=spf1 include:_cidrs.wikimedia.org ~all",
  "dmarcPolicy": "reject",
  "hasWebsite": true,
  "acceptsEmail": true,
  "sslStatus": "ok",
  "sslValid": true,
  "sslIssuer": "Let's Encrypt",
  "sslSanCount": 41,
  "tlsProtocol": "TLSv1.3",
  "sslValidTo": "2026-11-03T19:15:40.000Z",
  "sslDaysUntilExpiry": 37
}
```

Other fields: `updatedAt`, `registrarAbuseEmail`, `aaaaRecords`, `nsRecords`, `txtRecords`, `dmarcRecord`, `caaIssuers`, `sslSubject`, `sslValidFrom`, `sslSans` (up to 20 names the certificate covers), `sslSanCount`, `tlsProtocol`, `sslError` (for example `CERT_HAS_EXPIRED`), `rdapSource` and `errors`.

**Unregistered domains** come back with `rdapStatus: "not_found"` and `isRegistered: false`, which also makes this a bulk availability check.

### Pricing

Pay per event: **$0.0015 per domain looked up ($1.50 per 1,000)**, with WHOIS, DNS and SSL included. No start fee and no platform usage on top. A domain is charged when at least one source returned facts about it. Invalid input and domains where every source failed are pushed as free error rows.

### Limits

- **No registrant data.** Owner names, emails, phones and addresses are never collected, even where a registry still shows them. Registrar, dates, status and name servers only.
- **Some country registries have no RDAP service**, for example .de and a few other ccTLDs. For those, `rdapStatus` is `no_rdap_server` and the WHOIS fields are empty; DNS and SSL still work and the row is still one charge. The IANA bootstrap file decides which registries are covered, and it grows every year.
- For .com and .net the actor also reads the registrar's RDAP record when the registry points to it, to fill dates the registry leaves out.
- Registries rate limit RDAP. The actor keeps to about one request per 0.7 seconds per registry and retries politely, so 1,000 .com domains take roughly 12 to 25 minutes. Mixed TLD lists run faster.
- The SSL check connects to port 443 of the host you give. Sites without HTTPS show `sslStatus: "error"`.
- Up to 20,000 domains per run.

### FAQ

**Is RDAP the same as WHOIS?** It is its replacement. ICANN required every generic TLD registry and registrar to run RDAP, and the old port 43 WHOIS is being retired for them. RDAP returns structured JSON, so dates and registrars come back clean instead of parsed from free text.

**Why is `domainAgeDays` empty for some domains?** A few registries do not publish the creation date. The actor never guesses.

**Can I monitor expiry every week?** Yes. Schedule the actor in Apify with your domain list and filter the dataset on `daysUntilExpiry` or `sslDaysUntilExpiry`.

**Can an AI agent use it?** Yes. One input array, one row per domain, the same fields every time.

# Actor input Schema

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

Domains to look up, one per line. Full URLs and subdomains work: https://shop.example.co.uk/page is looked up as example.co.uk, and the SSL check uses shop.example.co.uk.

## `domainsText` (type: `string`):

Optional. Domains separated by spaces, commas or new lines.

## `whois` (type: `boolean`):

Registrar, creation, update and expiry dates, domain age, status codes, name servers and DNSSEC from the registry's RDAP service. Registrant contact details are never collected.

## `dns` (type: `boolean`):

A, AAAA, MX, NS, TXT, CAA, SPF and DMARC.

## `ssl` (type: `boolean`):

Issuer, validity dates, days until expiry, whether the chain is trusted, and the names the certificate covers.

## `maxDomains` (type: `integer`):

Stop after this many domains (up to 20,000 per run).

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "https://www.bbc.co.uk/news",
    "wikipedia.org"
  ],
  "whois": true,
  "dns": true,
  "ssl": true,
  "maxDomains": 5000
}
```

# Actor output Schema

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

All rows the run saved to the default 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": [
        "apify.com",
        "https://www.bbc.co.uk/news",
        "wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pistachio_implementation/domain-whois-dns-ssl-lookup").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": [
        "apify.com",
        "https://www.bbc.co.uk/news",
        "wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("pistachio_implementation/domain-whois-dns-ssl-lookup").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": [
    "apify.com",
    "https://www.bbc.co.uk/news",
    "wikipedia.org"
  ]
}' |
apify call pistachio_implementation/domain-whois-dns-ssl-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pistachio_implementation/domain-whois-dns-ssl-lookup"
        }
    }
}
```

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/zCOF5tit4HDD9ljmE/builds/lDgy53XHO3xOzf37B/openapi.json