# Domain & SSL Expiry Checker (RDAP + Certificate) (`thomson-digital/domain-ssl-expiry-checker`) Actor

Bulk-check domain registration and SSL certificates in one pass. Registrar, creation and expiry dates, days left, nameservers, DNSSEC, availability via official RDAP (WHOIS fallback), plus TLS issuer, validity, SANs and errors. Flags anything expiring within N days.

- **URL**: https://apify.com/thomson-digital/domain-ssl-expiry-checker.md
- **Developed by:** [Matt](https://apify.com/thomson-digital) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 domains

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 & SSL Expiry Checker (RDAP + Certificate)

Check **domain registration and SSL certificates for many domains in one pass**. For each domain you get the registrar, creation and expiry dates, days left, nameservers and DNSSEC from the official **RDAP** registry data (the modern WHOIS), with a WHOIS fallback for ccTLDs. You also get the live **TLS certificate**: issuer, validity window, days left, SANs and whether it validates. Anything expiring within your alert window is flagged.

You don't need an API key, a proxy or a browser. Results come back in seconds.

### Why this tool

- **Two monitors in one row:** domain expiry and SSL expiry together, so you don't need two tools and two schedules
- **Official data:** RDAP servers found automatically from the IANA bootstrap (gTLDs and most ccTLDs), with WHOIS on port 43 when a TLD has no RDAP
- **Ready-made alerts:** `domain-expiring-soon`, `domain-expired`, `domain-available`, `ssl-expiring-soon`, `ssl-expired`, `ssl-invalid`, `ssl-unreachable`
- **Monitoring mode:** with `onlyAlerts`, a scheduled run writes (and charges for) only the rows that need attention
- **Availability sweep:** check name ideas across many TLDs (`mybrand` × `com, io, ai, co`)

### Use cases

- Agencies and IT teams watching client portfolios for expiring domains and certificates
- Domain investors checking availability and expiry dates in bulk
- Security and compliance audits covering invalid, self-signed, mismatched or soon-to-expire certificates
- Brand protection: sweep a brand name across TLDs

### Input

```json
{
  "domains": ["apify.com", "github.com", "www.bbc.co.uk"],
  "checkDomain": true,
  "checkSsl": true,
  "warnDays": 30,
  "onlyAlerts": false
}
```

- **domains**: bare domains, subdomains or URLs. Registration data uses the registrable domain (`www.bbc.co.uk` → `bbc.co.uk`). The certificate is checked on the host as given, which you can change with `sslHost`.
- **namesToCheck** + **tlds**: optional availability sweep
- **warnDays**: alert window in days
- **onlyAlerts**: output only rows with an alert
- **whoisFallback**, **perRegistryConcurrency**, **maxConcurrency**, **requestTimeoutSecs**, **maxRetries**, **maxDomains**: advanced settings

### Output example

```json
{
  "input": "github.com",
  "domain": "github.com",
  "availability": "registered",
  "registrar": "MarkMonitor Inc.",
  "createdDate": "2007-10-09T18:20:50Z",
  "expiryDate": "2028-10-09T18:20:50Z",
  "daysUntilExpiry": 703,
  "nameservers": ["dns1.p08.nsone.net", "ns-1283.awsdns-32.org"],
  "dnssec": false,
  "lookupSource": "rdap",
  "sslValid": true,
  "sslIssuer": "Sectigo Limited",
  "sslValidTo": "2027-01-27T23:59:59Z",
  "sslDaysLeft": 82,
  "sslSans": ["github.com", "www.github.com"],
  "tlsVersion": "TLSv1.3",
  "alerts": [],
  "hasAlert": false
}
```

A `SUMMARY` record holds totals (registered, available, alerts).

### Pricing

**$1.00 per 1,000 domains** checked (pay-per-event, `domain-checked`), covering both the domain lookup and the SSL check. There's no start fee and no charge for platform usage. With `onlyAlerts`, you pay only for rows that are written.

### Scheduling

Create a schedule, for example daily or weekly, with `onlyAlerts: true`. Then connect a webhook, Slack, email, Zapier or Make so you only hear about domains and certificates that need action.

### Notes

- `available` means the registry's RDAP server returned "not found". For premium or reserved names, confirm with a registrar before buying.
- Some ccTLDs limit or redact public registration data, so a few fields may be empty for those TLDs.
- Registry servers are queried politely, with a per-registry concurrency limit.

Found a TLD that doesn't parse well? Open an issue and we'll add it.

# Actor input Schema

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

One per line. Bare domains, subdomains or full URLs. Registration data is looked up for the registrable domain (www.bbc.co.uk → bbc.co.uk); the SSL certificate is checked on the host as given.

## `namesToCheck` (type: `array`):

Optional brand / name ideas without a TLD (e.g. mycoolstartup). Each is combined with every TLD below to check availability.

## `tlds` (type: `array`):

TLDs combined with each name above, e.g. com, net, io, ai, co, app.

## `checkDomain` (type: `boolean`):

Registrar, created / updated / expiry dates, days until expiry, statuses, nameservers, DNSSEC, and registered vs available.

## `checkSsl` (type: `boolean`):

Connect on port 443 and report issuer, validity window, days left, SANs, key, TLS version and whether the certificate validates.

## `sslHost` (type: `string`):

Check the certificate on the host exactly as given (www.example.com) or on the registrable domain (example.com).

## `warnDays` (type: `integer`):

Rows get an alert (domain-expiring-soon, ssl-expiring-soon, …) when the domain or certificate expires within this many days.

## `onlyAlerts` (type: `boolean`):

Great for scheduled monitoring: only expiring / expired / invalid / available domains are written (and charged).

## `whoisFallback` (type: `boolean`):

Some ccTLDs (e.g. .de, .co.uk varies) have no RDAP; query their WHOIS server on port 43 instead.

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

Hard cap on domains checked per run.

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

Domains processed in parallel.

## `perRegistryConcurrency` (type: `integer`):

Keeps each RDAP / WHOIS server below its rate limit.

## `requestTimeoutSecs` (type: `integer`):

Timeout per lookup / TLS connection.

## `maxRetries` (type: `integer`):

Retries on rate limits and network errors.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "github.com",
    "www.bbc.co.uk"
  ],
  "namesToCheck": [],
  "tlds": [
    "com",
    "net",
    "io",
    "ai",
    "co"
  ],
  "checkDomain": true,
  "checkSsl": true,
  "sslHost": "asGiven",
  "warnDays": 30,
  "onlyAlerts": false,
  "whoisFallback": true,
  "maxDomains": 5000,
  "maxConcurrency": 10,
  "perRegistryConcurrency": 4,
  "requestTimeoutSecs": 15,
  "maxRetries": 2
}
```

# Actor output Schema

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

Dataset with one row per domain

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

Totals for the run

# 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",
        "github.com",
        "www.bbc.co.uk"
    ],
    "tlds": [
        "com",
        "net",
        "io",
        "ai",
        "co"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("thomson-digital/domain-ssl-expiry-checker").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",
        "github.com",
        "www.bbc.co.uk",
    ],
    "tlds": [
        "com",
        "net",
        "io",
        "ai",
        "co",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("thomson-digital/domain-ssl-expiry-checker").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",
    "github.com",
    "www.bbc.co.uk"
  ],
  "tlds": [
    "com",
    "net",
    "io",
    "ai",
    "co"
  ]
}' |
apify call thomson-digital/domain-ssl-expiry-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,thomson-digital/domain-ssl-expiry-checker"
        }
    }
}
```

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/HzBJi1diKqRWIb8AL/builds/izgXfkHKJH7wtsgfa/openapi.json