# Domain Intelligence: WHOIS, DNS & SSL Checker (`datalantern/domain-intel`) Actor

Bulk domain lookup: WHOIS/RDAP registrar, creation and expiry dates, DNS records (A, AAAA, MX, TXT), SPF and DMARC, email provider, and SSL certificate expiry for any list of domains.

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

## Pricing

Pay per event

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 Checker

**Domain Intelligence** is a bulk domain lookup tool: paste a list of domains and get the WHOIS/RDAP registrar, creation and expiry dates, DNS records, SPF and DMARC email security, the email provider, and SSL certificate expiry for each one, in a single table.

### What can this tool do?

- Look up registrar, creation date, expiry date, days to expiry, domain status, nameservers, and DNSSEC through the official RDAP protocol (the modern replacement for WHOIS), with a classic WHOIS fallback for country domains such as .io, .co, and .de.
- Tell you whether a domain is registered at all, so you can check if a name is available.
- Resolve DNS records: A, AAAA, MX, and TXT.
- Check email security: SPF record, DMARC record and policy (none, quarantine, reject).
- Detect the email provider from MX records (Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast, and more).
- Read the SSL certificate: issuer, valid from and to, days left, whether it is trusted, and the domains it covers.
- Check hundreds of domains in one run. Full URLs and `www.` are cleaned up automatically.

### What data does it return?

One row per domain. Example values from a real run:

| Field | Example |
|---|---|
| `domain` | apify.com |
| `registered` | true |
| `registrar` | Amazon Registrar, Inc. |
| `createdDate` | 2009-06-02T17:14:10.000Z |
| `updatedDate` | 2026-05-16T16:53:04.000Z |
| `expiryDate` | 2035-06-02T17:14:10.000Z |
| `daysToExpiry` | 3172 |
| `status` | \["client transfer prohibited"] |
| `nameservers` | \["ns-1225.awsdns-25.org", "ns-449.awsdns-56.com", …] |
| `dnssec` | true |
| `registrationSource` | rdap |
| `a` | \["3.170.42.100", "3.170.42.109", …] |
| `aaaa` | \["2600:9000:2870:2000:9:a03e:6540:93a1", …] |
| `mx` | \["1 aspmx.l.google.com", "5 alt1.aspmx.l.google.com", …] |
| `txt` | \["google-site-verification=…", "v=spf1 a mx include:\_spf.google.com … -all", …] |
| `spf` | v=spf1 a mx include:\_spf.google.com include:mailgun.org include:amazonses.com … -all |
| `hasSpf` | true |
| `dmarc` | v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:dmarc-reports@apify.com; ri=604800 |
| `hasDmarc` | true |
| `dmarcPolicy` | reject |
| `emailProvider` | Google Workspace |
| `sslIssuer` | Amazon |
| `sslValidFrom` | 2026-07-03T00:00:00.000Z |
| `sslValidTo` | 2027-01-16T23:59:59.000Z |
| `sslDaysLeft` | 114 |
| `sslSubjectAltNames` | \["*.apify.com", "apifier.com", "*.apifier.com", "apify.com"] |
| `sslValid` | true |
| `sslError` | null |
| `errors` | \[] (notes when a check could not be completed) |
| `checkedAt` | 2026-09-24T17:17:05.883Z |

Every row has the same fields, so CSV and Excel exports stay tidy. Checks you turn off return empty values.

### How to use it

1. Enter your domains, one per line (or paste URLs).
2. Optionally untick checks you don't need.
3. Click **Start**, then download the results as JSON, CSV, or Excel, or read them through the API.

### Common uses

- Monitor domain and SSL certificate expiry for a portfolio of websites; schedule it weekly and alert on `daysToExpiry` or `sslDaysLeft`.
- Audit email deliverability: find domains without SPF or DMARC, or with a weak `p=none` policy.
- Enrich a lead list with company email provider (Google Workspace vs Microsoft 365) and domain age.
- Check which names in a list are unregistered and available.

### Pricing

Pay per domain: **$2.00 per 1,000 domains**, all checks included, plus $0.005 per run. You only pay for domains that were checked. Set a maximum cost per run in the run options.

### Use it through the API, AI agents, and integrations

Call it from your code with the Apify API, schedule it, or connect it to Make, Zapier, n8n, or an AI agent through Apify's MCP server.

### Is it legal?

This tool reads public technical records: the registry's RDAP/WHOIS service, public DNS, and the certificate every HTTPS website presents. It returns registrar and date information only. **Registrant, admin, and technical contact details are never collected**, and personal-looking mailboxes inside DNS records are masked. You are responsible for how you use the data.

### FAQ

**Why are the registration fields empty for some domains?** A few country registries (for example .de) publish very little registration data, and some do not offer any public lookup service. The `errors` column explains what happened. DNS, email, and SSL checks still work for those domains.

**I entered a subdomain. What do I get?** DNS, email, and SSL checks run on the exact name you entered. Registration data comes from the registered parent domain (for example `docs.apify.com` → `apify.com`).

**Can I get the domain owner's name or email?** No. Owner contact data is personal information, and most registries redact it anyway. This tool returns the registrar (the company that sells the domain) instead.

**What does `registered: false` mean?** The registry said the domain does not exist, so it is most likely available to register.

### Feedback

Found a bug or need a field added? Open an issue on the **Issues** tab. We usually respond within 24 hours.

# Actor input Schema

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

One domain per line, for example apify.com. Full URLs and www. are cleaned up automatically.

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

Leave all selected for the full report. whois = registrar and dates, dns = A/AAAA/MX/TXT records, ssl = certificate, email = SPF, DMARC and email provider.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "wikipedia.org",
    "github.com"
  ],
  "checks": [
    "whois",
    "dns",
    "ssl",
    "email"
  ]
}
```

# Actor output Schema

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("datalantern/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",
        "wikipedia.org",
        "github.com",
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datalantern/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/bk2U3U0Pj4QgLYDdy/builds/PWuLk3DcUfqzhSSmS/openapi.json