# SSL Certificate Expiry Checker — Live TLS Cert Status (`m_ctim/ssl-certificate-expiry-checker`) Actor

Check the live TLS certificate on any host: issuer, subject, valid dates, days until expiry, and whether it's expired or self-signed. For ops and IT teams catching cert expirations before they cause an outage, across as many hosts as they need checked.

- **URL**: https://apify.com/m\_ctim/ssl-certificate-expiry-checker.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 certificate checkeds

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?

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

## SSL Certificate Expiry Checker — Live TLS Cert Status

Check the live TLS certificate actually installed on a host: issuer,
subject, valid dates, days until expiry, and whether it's expired or
self-signed. Connects directly over TLS, the same way a browser would —
not a WHOIS/registration lookup, and not a certificate-transparency-log
search, but the real cert being served right now.

Built for ops and IT teams checking a list of hosts for certs approaching
expiry, before it causes an outage.

### Input

```json
{
  "hosts": ["google.com", "example.com:8443"]
}
```

| Field | Type | Description |
|---|---|---|
| `hosts` | array of strings | Hostnames to check, without protocol. Add `:port` for a non-standard port (default `443`). One check is billed per host. |

### Output

One record per host:

```json
{
  "host": "google.com",
  "port": 443,
  "reachable": true,
  "subjectCN": "*.google.com",
  "issuerCN": "WR2",
  "issuerO": "Google Trust Services",
  "validFrom": "2026-07-21T08:32:00.000Z",
  "validTo": "2026-10-13T08:31:59.000Z",
  "daysUntilExpiration": 61,
  "isExpired": false,
  "isSelfSigned": false,
  "trustedByNode": true,
  "trustError": null,
  "subjectAltNames": ["DNS:*.google.com", "DNS:google.com"],
  "fingerprint256": "AB:CD:...",
  "error": null
}
```

A host that can't be reached (wrong port, connection refused, DNS
failure) returns `"reachable": false` with an `error` message instead —
still billed once, since a completed check is the result either way.

### How it works

Opens a direct TLS connection to each host and reads the certificate the
server presents, the same handshake a browser performs. No proxy, no key,
no scraping — just the TLS protocol itself.

### Pricing note

Billed per **host checked**, not per field returned — one charge per host
whether it's reachable or not.

### Related products

- [Domain Expiration Tracker](https://github.com/timmKal01/domain-expiration-tracker) — domain *registration* expiry via RDAP, a different expiry date than the TLS cert
- [Certificate Transparency Monitor](https://github.com/timmKal01/certificate-transparency-monitor) — new certs issued for a domain across the public CT logs, rather than the one currently live

# Actor input Schema

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

Hostnames to check, without protocol (e.g. "example.com" or "example.com:8443" for a non-standard port). One check is billed per host.

## Actor input object example

```json
{
  "hosts": [
    "google.com"
  ]
}
```

# 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 = {
    "hosts": [
        "google.com"
    ]
};

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

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

```

## MCP server setup

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