# Domain Inspector — WHOIS/RDAP, DNS & SSL (`hipersoft/domain-inspector`) Actor

Inspect any list of domains: registrar, registration/expiry dates and status via RDAP; DNS records (A, AAAA, MX, NS, TXT, CNAME); and SSL certificate issuer and expiry. Bulk-ready, no setup. Great for domain portfolios, security audits and lead research.

- **URL**: https://apify.com/hipersoft/domain-inspector.md
- **Developed by:** [Hipersoft](https://apify.com/hipersoft) (community)
- **Categories:** Developer tools, Automation
- **Features:** Limited permissions, Multi-tenant, Server interface
- **Stats:** 4 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.0008 / domain inspected

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Inspector — WHOIS/RDAP, DNS & SSL Lookup

Everything about a domain in one row. Give the Domain Inspector a list of domains and it returns each one's **registrar, registration & expiry dates, status codes and nameservers, full DNS records, and SSL certificate details** as clean **JSON, CSV, Excel or XML**.

![Domain Inspector input — domain list with RDAP, DNS and SSL toggles in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/domain-inspector-input.png?v=2)

### What does the Domain Inspector do?

The Domain Inspector takes a list of domains (or URLs) and returns a single structured record per domain combining registration lifecycle data, live DNS records and TLS certificate details. Toggle each data source on or off and inspect thousands of domains in one run — ideal for portfolio monitoring, expiry alerting and security audits.

### Features

- 🗂️ **Registration data** — registrar, creation/updated/expiry dates, EPP status codes and nameservers
- 🌐 **Live DNS** — A, AAAA, MX, NS, TXT and CNAME records resolved at run time
- 🔒 **SSL certificate** — issuer, subject, validity window, days to expiry and trust status
- ⚙️ **Toggle sources** — enable only RDAP, DNS or SSL as needed
- 📦 **Bulk** — inspect many domains in parallel, each time-capped so one slow lookup can't stall a run

### What you get

![Domain Inspector output example — per-domain registrar, DNS and SSL details as structured JSON](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/domain-inspector-output.png?v=5)

One row per domain:

```json
{
  "input": "google.com",
  "domain": "google.com",
  "registrableDomain": "google.com",
  "registrar": "MarkMonitor Inc.",
  "createdDate": "1997-09-15T04:00:00Z",
  "updatedDate": "2024-08-01T04:00:00Z",
  "expiryDate": "2028-09-14T04:00:00Z",
  "statuses": ["clientTransferProhibited"],
  "nameservers": ["ns1.google.com", "ns2.google.com"],
  "dns": { "a": ["142.250.72.14"], "mx": ["smtp.google.com"], "ns": ["ns1.google.com"], "txt": ["v=spf1..."] },
  "ssl": { "issuer": "Google Trust Services", "validTo": "2026-09-01T00:00:00.000Z", "daysToExpiry": 52, "authorized": true },
  "error": null
}
```

#### Output schema

| Field | Type | Description |
| --- | --- | --- |
| `input` | string | The exact domain or URL you supplied |
| `domain` | string | Normalized hostname that was inspected |
| `registrableDomain` | string | The eTLD+1 used for the registry lookup |
| `error` | string | Error message for this row, or null if it succeeded |
| `ssl` | object | SSL certificate details: issuer, subject, validFrom, validTo, daysToExpiry, authorized |
| `dns` | object | Resolved DNS records: a, aaaa, mx, ns, txt, cname |
| `rdapError` | string | Error message from the registration lookup, if any |
| `registrar` | string | Registrar name from the registration record |
| `createdDate` | string (ISO date) | Domain registration date |
| `updatedDate` | string (ISO date) | Last registration update date |
| `expiryDate` | string (ISO date) | Registration expiry date |
| `statuses` | array | EPP status codes, e.g. `clientTransferProhibited` |
| `nameservers` | array | Authoritative nameservers from the registry |

### Input

```json
{
  "domains": ["google.com", "example.co.uk", "apify.com"],
  "includeRdap": true,
  "includeDns": true,
  "includeSsl": true
}
```

| Field | Type | Description |
| --- | --- | --- |
| `domains` | array | Domains (or URLs — the host is used), one per line. |
| `includeRdap` | boolean | Include registrar, dates, statuses and nameservers (default on). |
| `includeDns` | boolean | Include live DNS records (default on). |
| `includeSsl` | boolean | Include SSL certificate details (default on). |
| `maxConcurrency` | integer | Domains inspected in parallel. |
| `proxyConfiguration` | object | Optional proxy settings. |

### Use cases

- **Portfolio monitoring** — track registrar, expiry and nameservers across a domain estate.
- **Expiry & SSL alerting** — flag domains or certificates nearing expiry.
- **Security audits** — review DNS records, status codes and certificate trust in bulk.
- **Due diligence** — verify ownership signals and infrastructure for a list of domains.
- **Lead enrichment** — append registration and DNS data to a prospect list.

### How to inspect domains

1. Add the Domain Inspector to your Apify account.
2. Paste your **domains** (one per line — URLs are accepted too).
3. Toggle **includeRdap**, **includeDns** and **includeSsl** as needed.
4. Click **Run**.
5. **Export** the dataset as JSON, CSV, Excel or XML, or pull it via the Apify API.

### Need more web-diagnostics data?

- [Bulk URL Status Checker](https://apify.com/hipersoft/bulk-url-checker) — check thousands of links for status, redirects and SSL.
- [Website Contact Scraper](https://apify.com/hipersoft/website-contact-scraper) — extract emails, phones and social links from websites.
- [Bulk Image Downloader](https://apify.com/hipersoft/bulk-image-downloader) — fetch and store images at scale from a URL list.

### FAQ

**How many domains can I inspect per run?**
There's no fixed cap. `maxConcurrency` controls how many domains are looked up in parallel, and each domain is time-capped so one slow lookup can't stall a bulk run.

**How does billing work?**
You pay only per domain you get, so small runs stay cheap. See the **Pricing** tab for current rates.

**What's the output format?**
A dataset with one row per domain — registrar, lifecycle dates, statuses, nameservers, DNS records and SSL details — exportable as JSON, CSV, Excel or XML.

**Can I choose which data to collect?**
Yes. Toggle `includeRdap`, `includeDns` and `includeSsl` to pick which sources to query, and use `maxConcurrency` to tune throughput.

**Is this only public data?**
Yes. It collects only publicly available registration, DNS and certificate data.

**Can I connect this to other tools?**
The Domain Inspector can be connected with almost any cloud service or web app thanks to [integrations on the Apify platform](https://apify.com/integrations). It works with [Make](https://apify.com/integrations/make), [Zapier](https://apify.com/integrations/zapier), [Slack](https://docs.apify.com/platform/integrations/slack), [Airbyte](https://docs.apify.com/platform/integrations/airbyte), [GitHub](https://docs.apify.com/platform/integrations/github), [Google Drive](https://docs.apify.com/platform/integrations/drive) and [many more](https://apify.com/integrations), plus the [Apify API](https://docs.apify.com/api/v2), JavaScript/Python clients and MCP. Or use [webhooks](https://docs.apify.com/platform/integrations/webhooks) to trigger an action whenever a run finishes.

### Related Actors

- [Bulk URL Status Checker](https://apify.com/hipersoft/bulk-url-checker)
- [Website Contact Scraper](https://apify.com/hipersoft/website-contact-scraper)
- [Bulk Image Downloader](https://apify.com/hipersoft/bulk-image-downloader)
- [Email Verifier](https://apify.com/hipersoft/email-verifier)

### Notes

Original clean-room implementation. Registration data comes from RDAP (the modern WHOIS); a few TLDs expose limited fields. Collects only publicly available registration, DNS and certificate data; you are responsible for compliance with the relevant terms.

# Actor input Schema

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

Domains to inspect (e.g. "google.com", "example.co.uk"). URLs are accepted too — the host is used. One per line.

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

Look up registrar, creation/expiry dates, status and nameservers via RDAP.

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

Resolve A, AAAA, MX, NS, TXT and CNAME records.

## `includeSsl` (type: `boolean`):

Fetch the TLS certificate issuer, validity and days-to-expiry (https).

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

How many domains to inspect in parallel.

## `proxyConfiguration` (type: `object`):

Proxy configuration. Leave the default — it is tuned for reliable results.

## Actor input object example

```json
{
  "domains": [
    "google.com",
    "apify.com"
  ],
  "includeRdap": true,
  "includeDns": true,
  "includeSsl": true,
  "maxConcurrency": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

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

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

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

```

## MCP server setup

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

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/qua6VHO79mZCgENiZ/builds/9sUxn5CZGlwpKISLj/openapi.json