SSL/TLS Certificate Expiry Checker

Enter a hostname, with a port if it is not 443. Our server opens a TLS connection to it and reads the certificate it presents: expiry date, days remaining, issuer, Subject Alternative Names, key size, fingerprint and the certificates above it in the chain.

Related Developer Tools

Your input is sent to our server to run the check. Results are not stored. Free, no account needed.

Last updated: · Reviewed by the QuickTooly Team

Reading the certificate report

What Our Server Does With the Hostname

The hostname you type is sent to the QuickTooly server. The server strips any https:// prefix, path or query, then opens a TLS connection to port 443, or to the port you add (for example example.com:8443), with SNI set to that hostname. It reads the certificate and closes the connection. No HTTP request is sent, so redirects and page content play no part.

IP addresses and localhost are refused before any connection is made, and so are hostnames that resolve to private, local or reserved addresses. The connection gives up after 10 seconds.

The Status Badge and the 30-Day Threshold

  • Valid: the certificate is trusted and has more than 30 days left before the Not After date.
  • Not Trusted: the dates are fine, but the certificate does not chain to a trusted CA or does not cover the hostname you entered. The reason code is shown under the badge.
  • Expiring Soon: 0 to 30 days left. Days are rounded down to whole days.
  • Expired: the Not After date has passed. The count shows how many days ago.

The server reads the certificate even when it is broken, then reports Node.js's own verdict: whether the certificate chains to a CA in Node's built-in trust store and whether it covers the hostname. Common reason codes are DEPTH_ZERO_SELF_SIGNED_CERT (self-signed), UNABLE_TO_VERIFY_LEAF_SIGNATURE (missing intermediate) and ERR_TLS_CERT_ALTNAME_INVALID (wrong hostname). Revocation (OCSP or CRL) is not checked, and a browser's trust store can differ slightly from Node's.

What Each Field Means

  • Common Name and Organisation: from the certificate subject. Domain-validated certificates usually have no Organisation, so it shows a dash.
  • Issuer: the CA that signed the certificate, shown by its Common Name, or its Organisation if there is no CN.
  • Valid From and Valid To: the Not Before and Not After dates.
  • TLS Protocol: the version negotiated between our server and yours, such as TLSv1.3. It is the version this connection used, not a list of every version your server accepts.
  • Key Size: the public key size in bits, such as 2048 for RSA or 256 for an EC P-256 key. A 256-bit EC key is not weaker than a 2048-bit RSA key.
  • Serial Number and SHA-256 Fingerprint: identify this exact certificate. Both change on renewal, so compare the fingerprint to confirm a new certificate is live.
  • Subject Alternative Names: the hostnames the certificate covers. Only DNS entries are listed; IP address entries are left out. Browsers match the hostname against this list, not against the Common Name.
  • Response time: measured from our server and includes the DNS lookup and the handshake. It says little about how fast the site loads for visitors.

The chain section lists the certificates above the server's own one, usually one or two intermediates, each with its issuer and expiry date. An intermediate that expires before the server certificate will break the chain on that date. To inspect a PEM file you already have, use the Certificate Decoder.

Error Messages

  • DNS resolution failed: the hostname does not resolve from our server. Check the spelling, or look it up with the DNS Lookup tool.
  • Connection refused: nothing is listening on that port.
  • Connection timed out after 10 seconds: a firewall is dropping the connection, or the port is wrong.
  • Other TLS errors: the port is open but does not speak TLS, for example a plain HTTP port such as 80.

SSL Checker Questions

What does "Not Trusted" mean?

The certificate is within its dates, but Node.js could not chain it to a trusted CA, or it does not list the hostname you checked. Self-signed certificates, a missing intermediate certificate on the server and a certificate issued for another name are the usual causes. The reason code under the badge says which.

Can I check a mail server or a port other than 443?

Yes, if the port speaks TLS from the first byte, such as 465 or 993. Add it after a colon, for example mail.example.com:993. Ports that need STARTTLS first, such as 25 or 587, fail, because the tool does not send STARTTLS.

Why is my IP address rejected?

The checker only accepts hostnames. IPv4 and IPv6 addresses and localhost are refused before any connection is made. Enter the hostname the certificate was issued for.