SSL Certificate Expiry Checker — Live TLS Cert Status avatar

SSL Certificate Expiry Checker — Live TLS Cert Status

Pricing

$20.00 / 1,000 certificate checkeds

Go to Apify Store
SSL Certificate Expiry Checker — Live TLS Cert Status

SSL Certificate Expiry Checker — Live TLS Cert Status

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.

Pricing

$20.00 / 1,000 certificate checkeds

Rating

0.0

(0)

Developer

Timothy Kelvin

Timothy Kelvin

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 days ago

Last modified

Categories

Share

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

{
"hosts": ["google.com", "example.com:8443"]
}
FieldTypeDescription
hostsarray of stringsHostnames to check, without protocol. Add :port for a non-standard port (default 443). One check is billed per host.

Output

One record per host:

{
"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.