# Domain Intelligence: WHOIS, DNS, SSL & Tech Stack (`gnom-tools/domain-intel`) Actor

WHOIS/RDAP lookup with domain age and expiry, DNS records (A, MX, TXT, NS), SSL certificate details and website tech stack in one run. Bulk domain intelligence for lead enrichment, SEO audits and domain monitoring.

- **URL**: https://apify.com/gnom-tools/domain-intel.md
- **Developed by:** [Gnom Automation](https://apify.com/gnom-tools) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## 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 & Tech Stack

One run gives you a complete technical profile of any domain: registration data, DNS records, TLS certificate and website metadata with detected technologies.

Built for lead enrichment, SEO audits, security reviews and domain portfolio monitoring — no proxies, no logins, no per-domain manual lookups.

### What you get

For every domain, one dataset item:

| Block | Data |
| --- | --- |
| `whois` | Registrar, IANA ID, registration date, last update, expiration date, **domain age in days**, days to expiry, status flags, nameservers, DNSSEC |
| `dns` | A, AAAA, MX, TXT, NS, CNAME, SOA records |
| `ssl` | Issuer, subject, valid from/to, **days left**, SAN list, serial number, TLS protocol |
| `http` | Status code, final URL, title, H1, meta description, Open Graph, canonical, robots, security headers |
| `technologies` | CMS, frameworks, analytics and hosting detected from headers and HTML (WordPress, Shopify, Next.js, React, Cloudflare, Vercel and 30+ more) |
| `errors` | Per-block error messages, so partial failures never break the run |

### Use cases

- **Lead enrichment** — append registrar, hosting and tech stack to a list of company domains.
- **Domain monitoring** — track expiration dates and SSL expiry to avoid outages.
- **Competitor research** — see which platforms and tools other companies run on.
- **SEO audits** — DNS, canonical URLs, Open Graph and metadata health in one pass.
- **Security triage** — certificate issuer, SAN list and DNSSEC status at a glance.

### Input example

```json
{
  "domains": ["apify.com", "https://example.com/pricing", "stripe.com"],
  "whois": true,
  "dns": true,
  "ssl": true,
  "http": true,
  "concurrency": 5,
  "timeoutSecs": 15
}
```

### Output example

```json
{
  "domain": "apify.com",
  "rootDomain": "apify.com",
  "checkedAt": "2026-11-01T03:10:00.000Z",
  "whois": {
    "registrar": "GoDaddy.com, LLC",
    "createdAt": "2015-05-14T18:23:22Z",
    "expiresAt": "2028-05-14T18:23:22Z",
    "ageDays": 3823,
    "daysToExpiry": 559,
    "status": ["clientDeleteProhibited", "clientTransferProhibited"],
    "nameservers": ["ns1.apify.com", "ns2.apify.com"],
    "dnssec": false
  },
  "dns": {
    "A": ["18.208.5.10"],
    "MX": ["10 inbound-smtp.us-east-1.amazonaws.com"],
    "TXT": ["v=spf1 include:amazonses.com ~all"],
    "NS": ["ns1.apify.com", "ns2.apify.com"]
  },
  "ssl": {
    "issuer": "Let's Encrypt",
    "validTo": "2027-01-20T12:00:00.000Z",
    "daysLeft": 80,
    "altNames": ["DNS:apify.com", "DNS:www.apify.com"],
    "protocol": "TLSv1.3"
  },
  "http": {
    "statusCode": 200,
    "title": "Apify: Full-stack platform for web scraping",
    "description": "Build and run web scrapers in the cloud.",
    "ogImage": "https://apify.com/img/og-image.png"
  },
  "technologies": ["Cloudflare", "Google Tag Manager", "Next.js", "React"],
  "errors": []
}
```

### Notes

- WHOIS data comes from RDAP (the modern structured replacement of port-43 WHOIS). Some ccTLD registries do not publish RDAP; those domains return a `whois.error` but the other blocks still work.
- DNS is resolved through Google Public DNS over HTTPS, so results are not affected by the runner's local resolver.
- The actor never stores or logs page contents — only extracted metadata.
- Works well with 1–1000 domains per run. For larger lists, split into batches or run on a schedule.

# Actor input Schema

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

Domains, hostnames or full URLs. Scheme, path and query are ignored. Duplicates are removed.

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

Registrar, registration and expiration dates, domain age, status flags, nameservers and DNSSEC.

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

A, AAAA, MX, TXT, NS, CNAME and SOA records via DNS-over-HTTPS.

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

Issuer, validity dates, days left, SAN list, serial number and TLS protocol.

## `http` (type: `boolean`):

Status code, final URL, title, meta description, Open Graph, canonical and detected technologies.

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

How many domains are processed in parallel.

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

Timeout applied to each individual network request.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com"
  ],
  "whois": true,
  "dns": true,
  "ssl": true,
  "http": true,
  "concurrency": 5,
  "timeoutSecs": 15
}
```

# Actor output Schema

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

Dataset with one item per domain: registrar, domain age, expiry, DNS records, SSL certificate, page metadata and detected technologies.

## `summary` (type: `string`):

Run counters: number of domains, processed, fully failed, enabled checks and finish time.

# 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",
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("gnom-tools/domain-intel").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",
        "example.com",
    ] }

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

```

## MCP server setup

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

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/20mYBOzvKdEWqhCwA/builds/Dk9hhg0BaluKSJ2Uf/openapi.json