# TLS Certificate Expiry & Domain Trust Monitor (`quanmatrix/tls-certificate-expiry-auditor`) Actor

Monitor certificate expiry, issuer, SAN coverage, TLS identity drift and renewal risk across public domains with trust scores and agent-ready actions.

- **URL**: https://apify.com/quanmatrix/tls-certificate-expiry-auditor.md
- **Developed by:** [Rafael Barreto Haddad](https://apify.com/quanmatrix) (community)
- **Categories:** Developer tools, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.95 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## TLS Certificate Expiry & Domain Trust Monitor

Monitor certificate expiry, issuer, SAN coverage, TLS identity drift and renewal risk across public domains with trust scores and agent-ready actions.

### Why use this Actor

Domain portfolios need early warning when certificate expiry, issuer, SAN coverage or TLS identity changes create trust and integration risk.

### Key features

- Buyer-native inputs aligned to **tls certificate expiry**.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.

### Quick start

Start with this working example and replace the target values with your own:

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

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

### Input

- `hosts` — Public hosts or URLs: Public HTTPS hosts or URLs whose TLS certificate lifecycle should be monitored.
- `previousSnapshots` — Previous TLS snapshots: Optional prior snapshots keyed by original input or host to detect certificate identity drift.
- `warningDays` — Renewal warning days: Days remaining at which renewal risk becomes a warning.
- `criticalDays` — Critical renewal days: Days remaining at which renewal risk becomes critical.
- `maxHosts` — Maximum hosts: Maximum TLS endpoints processed in one run.
- `concurrency` — Concurrency: Maximum parallel TLS checks.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

### Output

The Dataset exposes predictable machine-readable output. Representative fields include `dataset`.

### Pricing

This Actor uses Pay Per Event. The current factory base price is **$0.002500 per result event**. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

### Use cases

- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.

### Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

### Limitations

- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

### Detailed documentation

### Detailed documentation

### Why use this Actor

A certificate can renew successfully yet change issuer, SAN coverage or fingerprint in ways an operations team still needs to understand. Large domain and vendor portfolios also make manual expiry checking absurdly fragile. This Actor turns each host into a repeatable trust record with risk scores and an explicit recommended action.

### Key features

- Certificate expiry and configurable warning/critical windows.
- Issuer, subject and DNS SAN evidence.
- TLS version and negotiated cipher.
- SHA-256 certificate fingerprint.
- Snapshot comparison for issuer, SAN, fingerprint and TLS-version drift.
- `renewalRiskScore`, `trustScore`, `agentAction` and compact evidence.
- Concurrent portfolio checks at 256 MB.
- Optional fail-on-risk behavior for operational gates.

### Input

Provide public hosts or HTTPS URLs. Add `previousSnapshots` for continuous lifecycle and identity monitoring.

```json
{"hosts":["example.com","www.python.org"],"warningDays":30,"criticalDays":7}
```

### Output

Each host returns certificate dates, days remaining, issuer, SANs, TLS version, cipher, fingerprint, changed snapshot fields, renewal risk, trust score and a recommended action.

### Example

A host with seven days remaining can produce a high `renewalRiskScore` and `PLAN_CERTIFICATE_RENEWAL`. A renewed certificate whose issuer and fingerprint changed can be surfaced as TLS identity drift even when expiry is healthy.

### Use cases

Certificate renewal monitoring, agency portfolios, DevSecOps, SaaS vendor risk, partner endpoints, ecommerce domains, domain acquisitions, CDN migrations, managed security services and AI-agent infrastructure monitoring.

### Pricing

Pay per result. The base configured price is **$0.0025 USD per host result**, with tiered discounts where supported.

### Limitations

Only public TLS endpoints are supported. Results describe the certificate and TLS session observed from the Apify runtime location; geo-specific edge behavior can differ. This is not a replacement for private PKI inventory or certificate-authority management.

#### Input reliability — 25 October 2026

Target lists are validated before network work, trimmed and deduplicated. Empty lists and malformed baselines are rejected rather than silently auditing a default website. Exact duplicate targets produce one result. Existing output fields and prices are preserved.

# Changelog

This Actor's version history is a separate document: https://apify.com/quanmatrix/tls-certificate-expiry-auditor/changelog.md

# Actor input Schema

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

Public HTTPS hosts or URLs whose TLS certificate lifecycle should be monitored. Exact duplicates are processed once; empty target arrays are rejected.

## `previousSnapshots` (type: `object`):

Optional prior snapshots keyed by original input or host to detect certificate identity drift.

## `warningDays` (type: `integer`):

Days remaining at which renewal risk becomes a warning.

## `criticalDays` (type: `integer`):

Days remaining at which renewal risk becomes critical.

## `maxHosts` (type: `integer`):

Maximum TLS endpoints processed in one run.

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

Maximum parallel TLS checks.

## `failRunOnRisk` (type: `boolean`):

Fail after writing results if any renewalRiskScore reaches the configured threshold.

## `riskThreshold` (type: `number`):

renewalRiskScore threshold used by failRunOnRisk.

## `mcpConnectors` (type: `array`):

Optional MCP connectors authorized in your Apify account. Use them to send or write this Actor result to tools such as Slack, Notion, GitHub, Sentry, Supabase, or another compatible MCP service.

## `mcpToolName` (type: `string`):

Optional exact MCP tool name. Leave blank to let the selected MCP action preset discover a compatible tool automatically.

## `mcpToolArguments` (type: `object`):

JSON object passed to the selected MCP tool. String values may use {{actor_title}}, {{result_summary}}, or {{result_json}} placeholders.

## `mcpFailOnError` (type: `boolean`):

When enabled, an MCP delivery error fails the Actor run. Disabled by default so data extraction and intelligence results remain available even if the external destination is unavailable.

## `mcpActionPreset` (type: `string`):

Choose a safe action pattern. AUTO_SAFE_WRITE discovers a compatible non-destructive write tool automatically; use a specific preset for Slack, GitHub, Notion, or database delivery.

## Actor input object example

```json
{
  "hosts": [
    "example.com"
  ],
  "previousSnapshots": {},
  "warningDays": 30,
  "criticalDays": 7,
  "maxHosts": 200,
  "concurrency": 10,
  "failRunOnRisk": false,
  "riskThreshold": 70,
  "mcpToolName": "",
  "mcpToolArguments": {},
  "mcpFailOnError": false,
  "mcpActionPreset": "AUTO_SAFE_WRITE"
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quanmatrix/tls-certificate-expiry-auditor").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quanmatrix/tls-certificate-expiry-auditor").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 '{}' |
apify call quanmatrix/tls-certificate-expiry-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quanmatrix/tls-certificate-expiry-auditor"
        }
    }
}
```

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/BZV9PUxvw6VC7ExUG/builds/xQ6fcDBV4dRjy0BEq/openapi.json
