How to use Live SSL/TLS Certificate Checker
- Enter the public hostname to inspect on TLS port 443. The service must have human verification and its isolated worker configured.
- Verify that you are human, then select Check TLS certificate.
- Review hostname, current dates and chain findings separately. Download the JSON report if needed; revocation remains explicitly unchecked.
Example: Live SSL/TLS Certificate Checker
Check certificate findings with an explicit revocation limit.
Supported inputs and limits
- Your entered hostname is sent to this site and its isolated metadata worker.
- Public hostnames on port 443 only; every resolved address must be public and the connection is pinned with the original hostname/SNI.
- Certificate data is capped at 64 KiB and each task at 15 seconds.
- Trust uses the worker image’s CA store.
- Invalid-chain certificates may be displayed as findings and are never labelled chain-verified.
More details
OCSP, CRL and AIA URLs are not followed; revocation, ownership and historical validity are not established.
Human verification is single-use and session-bound.
Access to private metadata expires after 15 minutes.
Worker cleanup and an independently scheduled app-minute fallback remove expired files; if both are offline, deletion waits for recovery.
Stale fallback health disables new live checks.
Where your input is processed
The entered public target is sent to this site and a separate restricted metadata worker after human verification. DNS uses the disclosed Cloudflare resolver. The checked service receives only the fixed metadata probe, with no browser cookies or custom headers. Job access expires after 15 minutes. The worker and an independent scheduled app cleanup remove expired metadata; if both are offline, deletion waits for recovery.
Questions about Live SSL/TLS Certificate Checker
Does a valid certificate prove the site is trustworthy?
No. This check reports certificate and connection findings. It does not establish business identity, site ownership or whether a site is safe to use.
Are OCSP, CRL and AIA services queried?
No revocation or issuer-discovery URLs are followed. Revocation is always marked not checked, even when the supplied chain verifies.
Can an invalid certificate still appear in the report?
Yes. A failed certificate verification can be followed by a metadata-only connection to the same validated public address. Its chain remains marked unverified.