# SSL Certificate Checker: Expiry, Issuer, Chain, TLS (`dodge_bot/ssl-certificate-checker`) Actor

Check SSL/TLS certificates for any list of domains: days until expiry, issuer, whether it covers the host name, trusted chain, self-signed, TLS version, cipher, key type and all subject alternative names. Great for expiry monitoring on a schedule.

- **URL**: https://apify.com/dodge_bot/ssl-certificate-checker.md
- **Developed by:** [Dodge Sucharda](https://apify.com/dodge_bot) (community)
- **Categories:** Developer tools, Automation
- **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

## SSL Certificate Checker: Expiry, Issuer, Chain, TLS

Check the SSL/TLS certificate of any number of domains in one run: expiry date and days left, issuer, whether it covers the host name, whether the chain is trusted, self-signed certificates, TLS version, cipher, key type and every subject alternative name.

**$1 per 1,000 hosts.** Hosts that do not exist or refuse the connection are free.

### Good for

- **Expiry monitoring**: schedule it daily or weekly on your domains and alert on `daysLeft` (use Apify's schedules and integrations)
- **Agencies and IT teams**: audit every client site at once
- **Security reviews**: find self-signed, mismatched or old-TLS endpoints
- **Inventory**: list which certificate authority each domain uses

### Output (one row per host; real result from 30 Sep 2026, shortened)

```json
{
  "host": "apify.com",
  "port": 443,
  "status": "ok",
  "valid": true,
  "daysLeft": 108,
  "validTo": "2027-01-16T23:59:59.000Z",
  "issuer": "Amazon",
  "issuerCommonName": "Amazon RSA 2048 M04",
  "coversHost": true,
  "trusted": true,
  "selfSigned": false,
  "protocol": "TLSv1.3",
  "keyType": "RSA 2048",
  "sanCount": 4,
  "subjectAltNames": ["*.apify.com", "apifier.com", "*.apifier.com", "apify.com"],
  "issues": []
}
```

`valid` is false when there is any error: expired, expiring within 7 days, not yet valid, host name not covered, self-signed, or an untrusted chain. `expires_soon` (within your warning window, default 30 days) and old TLS versions are warnings.

### Input

- **Hosts**: domains or URLs, optionally with a port (`mail.example.com:993` works for any TLS service).
- **Warn when expiring within (days)**: default 30.

### Limits

- It reads the certificate the server presents for the host name you give (SNI). It does not scan every server behind a load balancer.
- It does not check revocation (OCSP/CRL).

# Actor input Schema

## `hosts` (type: `array`):

Domains or URLs (a port like example.com:8443 is allowed). Up to 20,000 per run.

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

Certificates expiring within this many days get an 'expires_soon' warning.

## Actor input object example

```json
{
  "hosts": [
    "apify.com",
    "expired.badssl.com",
    "wrong.host.badssl.com"
  ],
  "warnDays": 30
}
```

# Actor output Schema

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

No description

## `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 = {
    "hosts": [
        "apify.com",
        "expired.badssl.com",
        "wrong.host.badssl.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dodge_bot/ssl-certificate-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 = { "hosts": [
        "apify.com",
        "expired.badssl.com",
        "wrong.host.badssl.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("dodge_bot/ssl-certificate-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 '{
  "hosts": [
    "apify.com",
    "expired.badssl.com",
    "wrong.host.badssl.com"
  ]
}' |
apify call dodge_bot/ssl-certificate-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dodge_bot/ssl-certificate-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/2D3tIpf8x9zsGVthD/builds/3UBvR41YrGHdk2Ugb/openapi.json