What this SSL check answers
A public site on 443 presents a certificate during the TLS handshake. That file names the hosts it covers, who signed it, and the window in which it is valid. This page runs that handshake on our server, with SNI set to the host you typed, then writes the facts in plain words. It is free, it does not ask for an email, and it does not sit behind a paid API. SSL/TLS certificates and HTTPS are defined in the website glossary.
Trusted is yes only when Node’s CA store accepts the chain, the hostname matches a SAN (or CN when no SAN is present), and revocation did not come back revoked. An expired leaf, a self-signed leaf, an untrusted root, a hostname that is not listed, or a missing intermediate is a no, with that reason attached. A self-signed leaf (subject equals issuer) is labelled self-signed. A chain whose root is not in the trust store is labelled untrusted root — not self-signed. There is no letter grade.
What an SSL/TLS certificate is, field by field
The leaf is the certificate for the site. Subject is who it claims to be. Issuer is who signed it. Valid from / valid until is the window. Days left is whole days from this check until valid until: under 30 is a warning, under 7 is critical, a past date is expired. Names come from the SAN list, including a leftmost-label wildcard such as *.example.com, which covers shop.example.com and does not cover example.com or a.b.example.com.
The chain is each certificate’s subject and issuer, leaf first. TLS protocol and cipher are what the handshake settled on. Key type and size are read from the leaf (RSA or elliptic curve). The SHA-256 fingerprint is the leaf’s fingerprint256. http to https is one HEAD (or GET if HEAD fails) to the same host on port 80, with no page body kept, using the same private-IP guard as the redirect checker. HSTS is the Strict-Transport-Security value on the https response, documented on MDN. Revocation is a separate line: we ask the CA over OCSP when the leaf names a responder, and if that is missing or fails we fetch the CRL URL from the certificate. If neither lookup can be done, the result says revocation not checked.
Common fixes
Renew before valid until. Most issuers will mint a replacement while the current leaf is still in date; waiting until the browser warning appears leaves a gap. If trust fails with an incomplete chain, install the intermediate alongside the leaf — the root stays in the client store, but the server has to send everything in between.
A www versus apex mismatch is a name problem, not an expiry problem. If people type both hosts, both names (or a matching wildcard) must appear on the leaf. Pick one live host and send the other there. If http still serves a page, send that request to https with a 301 or 308, then add HSTS on the https response so browsers skip http on later visits. For the hop-by-hop view of that move, including www and apex together, use the redirect checker.
HTTPS and Google Search
Google Search Central’s HTTPS as a ranking signal post (7 August 2014) described HTTPS as a very lightweight ranking signal, with less weight than high-quality content. The page experience documentation still asks whether pages are served in a secure fashion. Google also prefers HTTPS over HTTP when choosing a canonical URL, unless the https certificate is invalid. This check reports the certificate in front of you. It does not forecast rankings or traffic.
Limits
We only connect to public hosts on port 443. Private, loopback, link-local, and metadata addresses are refused after DNS, and the socket is pinned to the address we just checked. The handshake times out around eight seconds. Paths are stripped. Nothing is stored. We do not inspect mixed content, client certificates, or certificates on any other port. Revocation uses only the OCSP or CRL URL printed on the certificate, fetched with the same private-IP guard as the handshake. Let’s Encrypt turned off OCSP on 6 August 2025 (read 18 Nov 2026), so those leaves are checked via CRL. If OCSP and CRL both fail, or the certificate lists neither, we write revocation not checked rather than calling the leaf trusted by silence. The calendar reminder is an .ics file built in your browser; we do not collect an email address.
Tired of certificate and hosting surprises? Nuvora builds custom websites with HTTPS, hosting and renewals handled as part of the plan, for $500/month, first month paid upfront, with full ownership after 24 months.