# Bulk Domain Audit: WHOIS (RDAP), DNS, SPF, DMARC, SSL expiry (`netaudit-labs/bulk-domain-audit`) Actor

Audit thousands of domains in one run: registrar, creation and expiry dates (official RDAP, no scraping), A/MX/NS records, SPF and DMARC policy, SSL certificate issuer and expiry, plus a plain list of issues.

- **URL**: https://apify.com/netaudit-labs/bulk-domain-audit.md
- **Developed by:** [NetAudit Labs](https://apify.com/netaudit-labs) (community)
- **Categories:** Developer tools, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 domain auditeds

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

## Bulk Domain Audit: WHOIS (RDAP), DNS, SPF, DMARC, SSL expiry

Paste a list of domains, get one clean row per domain with everything you usually look up in five different tools:

| Group | Fields |
|---|---|
| Registration (RDAP) | `registered`, `registrableDomain` (parent looked up for subdomains), `registrar`, `createdAt`, `expiresAt`, `domainAgeDays`, `daysUntilDomainExpiry`, `status`, `nameservers` |
| DNS | `resolves`, `aRecords`, `nsRecords`, `mxRecords`, `hasMx` |
| Email security | `spfRecord`, `spfAllQualifier`, `dmarcRecord`, `dmarcPolicy` |
| SSL | `sslValid`, `sslError`, `sslIssuer`, `sslValidTo`, `daysUntilSslExpiry` |
| Summary | `issues` (for example `MX without DMARC`, `SSL expires in 9 days`, `domain expires in 12 days`) |

### Why RDAP instead of WHOIS scraping

Registration data comes from the official RDAP server of each TLD registry (IANA bootstrap list). RDAP is the structured successor of port 43 WHOIS: no HTML parsing, no captcha, no rate-limited third-party site. A TLD without an RDAP server returns `rdapAvailable: false` and the DNS, email and SSL checks still run.

### Typical uses

- **Lead qualification**: domain age, whether the company runs its own mail (MX), whether it protects it (DMARC).
- **Email deliverability audits** for agencies: find clients with no SPF, no DMARC or `p=none`.
- **Portfolio monitoring**: domains and certificates expiring in the next weeks.
- **Expired domain research**: `registered: false` on a list of candidates.

### Input

```json
{ "domains": ["apify.com", "https://www.example.com/page"], "includeWhois": true, "includeSsl": true, "concurrency": 10 }
```

### Output example

```json
{ "domain": "example.com", "registered": true, "registrar": "RESERVED-Internet Assigned Numbers Authority",
  "createdAt": "1995-08-14T04:00:00Z", "expiresAt": "2027-08-13T04:00:00Z", "domainAgeDays": 11395,
  "resolves": true, "hasMx": true, "spfRecord": "v=spf1 -all", "dmarcPolicy": "reject",
  "sslValid": true, "sslIssuer": "DigiCert Inc", "daysUntilSslExpiry": 80, "issues": [] }
```

### Pricing

Pay per event: you are charged once per audited domain (`domain-audited`), duplicates in the input are removed first. Use `maxDomains` to cap the cost of a run.

### Limits

- DNS queries go to public resolvers (1.1.1.1, 8.8.8.8). DKIM is not checked because it needs the selector name.
- Some registries hide the registrar or dates in RDAP; those fields are then `null`.

# Actor input Schema

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

Domains or URLs. https://, www. and paths are stripped automatically.

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

Optional: paste domains separated by new lines, commas or spaces.

## `includeWhois` (type: `boolean`):

Registrar, creation date, expiry date, status, nameservers from the official registry RDAP server.

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

Connects to port 443 and reads the certificate issuer, validity and days until expiry.

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

Domains audited in parallel.

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

Safety cap on the number of domains processed (and charged).

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com"
  ],
  "includeWhois": true,
  "includeSsl": true,
  "concurrency": 10,
  "maxDomains": 10000
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("netaudit-labs/bulk-domain-audit").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("netaudit-labs/bulk-domain-audit").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 netaudit-labs/bulk-domain-audit --silent --output-dataset

```

## MCP server setup

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

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/LrlrfPk8ustFzQ8nJ/builds/bGrCSX2l1Rkhmyipp/openapi.json