# 🔐 Domain, SSL & DNS Monitor - Expiry + Change Alerts (`that_red_bird/domain-ssl-monitor`) Actor

⚡ Never lose a domain or serve an expired certificate again. ✅ Domain expiry via RDAP, live TLS certificate expiry and validity, nameserver and DNS record changes. ✅ Warns before expiry and alerts the moment records move. No API key needed.

- **URL**: https://apify.com/that\_red\_bird/domain-ssl-monitor.md
- **Developed by:** [mohamed alaya](https://apify.com/that_red_bird) (community)
- **Categories:** Developer tools, Automation, 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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Domain, SSL & DNS Monitor

Three of the most expensive outages in tech are also the most preventable: a domain that
quietly expired, a certificate nobody renewed, and DNS records that changed without anyone
noticing. This watches all three.

### What it checks

**Domain (via RDAP, the structured successor to WHOIS)** — registrar, registration status,
DNSSEC, nameservers, and `daysUntilDomainExpiry`.

**TLS certificate (read live off the socket, not from a third party)** — issuer, subject,
SAN list, fingerprint, `daysUntilCertExpiry`, and whether it actually **validates**.

**DNS (over DNS-over-HTTPS)** — A, AAAA, MX, NS, TXT and more, snapshotted and compared.

### What raises an alert

- Domain or certificate inside your warning window (`expiryWarningDays`, `certWarningDays`)
- A certificate that no longer validates
- **Nameservers changed** — often the first visible sign of a domain hijack
- Certificate **issuer** changed, or registration status changed
- Any watched DNS record changing

### What deliberately does not alarm you

A rotated certificate **fingerprint** is reported but is not treated as critical on its own —
Let's Encrypt renews every 60 days and flagging that as an incident would train you to ignore
the alerts. A changed **issuer** is critical; a routine renewal is not.

DNS answers and nameserver lists are **sorted before comparison**, so a round-robin resolver
returning the same records in a different order can never look like a change.

### Typical uses

Agencies and MSPs watching client domains · security teams tracking hijack indicators ·
DevOps preventing certificate outages · anyone who has ever lost a domain to auto-renew
failing silently.

### Schedule it

Daily is right for expiry and DNS. Point `webhookUrl` at Slack and you will hear about a
problem weeks before it becomes an outage.

# Actor input Schema

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

Domain names or URLs. https:// and www. are stripped automatically.

## `checkDomainExpiry` (type: `boolean`):

Registrar, registration status, nameservers and the domain's expiry date.

## `checkCertificate` (type: `boolean`):

Reads the live certificate off the socket: issuer, expiry, SAN list, fingerprint and whether it validates.

## `checkDns` (type: `boolean`):

Snapshots DNS records over DNS-over-HTTPS and reports changes between runs.

## `dnsTypes` (type: `array`):

Which records to snapshot. Supported: A, AAAA, MX, NS, TXT, CNAME, SOA, CAA.

## `compareDnsTypes` (type: `array`):

Only these record types are compared between runs. A and AAAA are excluded by default because load-balanced and CDN-fronted domains return different IPs on every query — including them would raise an alert on every run. Add "A" if your domain has a fixed IP.

## `expiryWarningDays` (type: `integer`):

Raises an alert while the domain is inside this window.

## `certWarningDays` (type: `integer`):

Raises an alert while the certificate is inside this window.

## `onlyChanges` (type: `boolean`):

Push only rows that changed or raised an alert. Recommended when watching many domains.

## `alertOnErrorAfter` (type: `integer`):

Flags a domain that keeps failing every check. 0 disables it.

## `resetBaseline` (type: `boolean`):

Forget stored values and start fresh.

## `maxItems` (type: `integer`):

Hard cap on dataset rows per run. 0 = no cap.

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

How many domains to check in parallel.

## `webhookUrl` (type: `string`):

POSTed when a domain alerts. Slack/Discord/Zapier compatible.

## `stateStoreName` (type: `string`):

Named key-value store holding the previous snapshot. Use different names per client.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "https://www.google.com"
  ],
  "checkDomainExpiry": true,
  "checkCertificate": true,
  "checkDns": true,
  "dnsTypes": [
    "A",
    "AAAA",
    "MX",
    "NS",
    "TXT"
  ],
  "compareDnsTypes": [
    "MX",
    "NS",
    "TXT",
    "CAA"
  ],
  "expiryWarningDays": 30,
  "certWarningDays": 21,
  "onlyChanges": false,
  "alertOnErrorAfter": 3,
  "resetBaseline": false,
  "maxItems": 0,
  "concurrency": 5,
  "stateStoreName": "domain-ssl-monitor-state"
}
```

# Actor output Schema

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

No description

## `downloadCsv` (type: `string`):

No description

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

No description

## `count` (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": [
        "example.com",
        "https://www.google.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("that_red_bird/domain-ssl-monitor").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": [
        "example.com",
        "https://www.google.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("that_red_bird/domain-ssl-monitor").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": [
    "example.com",
    "https://www.google.com"
  ]
}' |
apify call that_red_bird/domain-ssl-monitor --silent --output-dataset

```

## MCP server setup

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

```

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/FXBmsbXTTkvciDB7l/builds/rP4pjnRhvicGLtaLJ/openapi.json