SSL Certificate Checker — Expiry & Validity

Check SSL/TLS certificates for many hosts — issuer, validity window, days to expiry, hostname match, and expiring-soon flags. Ideal for scheduled expiry monitoring. No auth.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
host	Host
valid	Valid
commonName	Common Name
issuer	Issuer
validTo	Valid to
daysToExpiry	Days to expiry
expiringSoon	Expiring soon
riskGrade	Risk grade
actionNeeded	Action needed
hostMatches	Host matches

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "domains": [
    "example.com"
  ],
  "timeoutMs": 10000,
  "maxItems": 100000
}

Sample output

[
{
  "host": "example",
  "valid": true,
  "commonName": "Example commonName",
  "issuer": "example",
  "validTo": "EX12345",
  "daysToExpiry": 42,
  "expiringSoon": true,
  "riskGrade": "example",
  "actionNeeded": "example",
  "hostMatches": true
}
]

Typical uses

• Expiry monitoring — schedule daily; alert on SUMMARY.expiringSoon via the webhook notifier.
• Fleet audits — validity + issuer + hostname match across many domains.

Pricing

$1.00 / 1,000 results ($0.001 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• SSL Certificate Checker
• DNS Lookup
• HTTP Header Analyzer

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• SSL Certificate Checker — Expiry & Validity declares all 10 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of SSL Certificate Checker include host, valid, commonName, issuer, validTo and daysToExpiry.
• SSL Certificate Checker needs no API key, login or account of any kind before its first run.
• Every one of SSL Certificate Checker's 3 inputs is optional, so it runs with no configuration at all.
• SSL Certificate Checker documents commonName as: Common or trade name, where it differs from the registered name.
• Every number published about SSL Certificate Checker is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• SSL Certificate Checker is filed under developer tools and automation so that it is found by the people looking for that job, not by its internal name.

Limitations

• SSL Certificate Checker reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.