# Domain Intelligence — WHOIS, DNS, SSL & HTTP in one call (`nivlekk/domain-intelligence`) Actor

Full domain report in one run: WHOIS registration & expiry, DNS records, SSL certificate details, and HTTP/redirect status. Clean structured JSON, bulk domains.

- **URL**: https://apify.com/nivlekk/domain-intelligence.md
- **Developed by:** [Kelvin Yayra Kwaku Ganyo](https://apify.com/nivlekk) (community)
- **Categories:** Automation, Developer tools, Integrations
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 results

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, DNS, SSL & HTTP in one call

Everything about a domain in a **single run**: registration and expiry (WHOIS), full DNS records, SSL certificate details, and live HTTP/redirect status — as clean structured JSON. Pass one domain or a whole list.

Most tools do one of these. This does all four, together, per domain.

### What you get per domain

- **WHOIS / registration** — registrar, creation & expiry dates, domain age, days until expiry, status flags, nameservers.
- **DNS records** — A, AAAA, MX, NS, TXT, CNAME, SOA.
- **SSL certificate** — issuer, subject, valid-from/to, **days until expiry**, SANs, and whether the chain is trusted.
- **HTTP status** — status code, final URL after redirects, the full redirect chain, server header, and page title.

### Use cases

- **Security & due diligence** — vet a domain's age, cert health, and DNS setup at a glance.
- **Sales & lead enrichment** — enrich a list of company domains with registrar, tech signals, and reachability.
- **Portfolio & uptime monitoring** — watch SSL/domain expiry and redirect changes on a schedule.
- **Migration & audits** — snapshot DNS and cert state before and after changes.

### Input

| Field | Type | Description |
|---|---|---|
| `domains` | array | Domains or URLs (the hostname is used) |
| `checks` | array | Any of `whois`, `dns`, `ssl`, `http` (default: all) |
| `proxyConfiguration` | object | Optional — not needed for most runs |

```json
{
    "domains": ["github.com", "https://apify.com"],
    "checks": ["whois", "dns", "ssl", "http"]
}
```

### Output

One dataset item per domain, with a flat summary plus full detail:

```json
{
    "domain": "github.com",
    "registrar": "MarkMonitor Inc.",
    "createdDate": "2007-10-09T18:20:50Z",
    "expiresDate": "2026-10-09T18:20:50Z",
    "domainAgeDays": 6863,
    "daysUntilDomainExpiry": 77,
    "sslIssuer": "Sectigo Limited",
    "sslDaysUntilExpiry": 68,
    "httpStatus": 200,
    "reachable": true,
    "whois": { "statuses": ["client transfer prohibited"], "nameservers": ["dns1.p08.nsone.net"] },
    "dns": { "A": ["140.82.121.3"], "MX": ["..."], "NS": ["..."], "TXT": ["..."] },
    "ssl": { "subjectCN": "github.com", "validTo": "...", "san": ["github.com", "www.github.com"] },
    "http": { "finalUrl": "https://github.com/", "redirectChain": [], "server": "..." },
    "checkedAt": "2026-07-24T00:00:00.000Z"
}
```

### Notes

- Lookups use public RDAP and DNS-over-HTTPS endpoints and a direct TLS handshake — no API keys needed.
- Any single failed lookup (e.g. a domain with no SSL) is reported in that section without failing the rest.

# Actor input Schema

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

Domains or URLs to inspect (e.g. "github.com" or "https://github.com/foo"). The hostname is used.

## `checks` (type: `array`):

Which lookups to perform for each domain.

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

Not needed for most runs — the lookups use public endpoints.

## Actor input object example

```json
{
  "domains": [
    "github.com",
    "https://apify.com"
  ],
  "checks": [
    "whois",
    "dns",
    "ssl",
    "http"
  ],
  "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": [
        "github.com"
    ]
};

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

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

```

## MCP server setup

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

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/Bkm54M5biDkOKkXaI/builds/FeNrwiwcM3Zko4DcX/openapi.json