Free SSL Checker for Website Certificates and TLS
Check the certificate a public site presents, the chain it sends and which TLS versions connect from our server, then work through a renewal and remediation checklist with sources.
Last updated 15 November 2026
This SSL checker shows what one public site presents when our server opens a TLS connection to it. It attempts four handshakes to port 443, one each for TLS 1.3, 1.2, 1.1 and 1.0, and reports which connected, with the protocol and cipher negotiated. A version the server this tool runs on cannot offer shows as not tested. For the first handshake that connected, it shows the certificate: who it was issued to and by, its dates and the days left at the time of the check, its names, and whether the name you checked matches one of them under the rule in RFC 9525. It lists the chain of certificates the server presented, leaf first. A renewal and remediation checklist then lists what it saw, Fix items first, then Review, then Note, each with a step to take and its source. Our server makes the handshakes for you, so check only a site you own or have permission to check.
How to use this tool
- 1
Enter your site's hostname or address
Type your site's hostname without https://, or paste the address from your browser's address bar. The tool keeps only the hostname, and for an http:// address it checks the same name over TLS on port 443. It refuses an address with a user name or password, a port other than 443, or an IP address in place of a name, before anything is sent.
- 2
Run the check
Press Check certificate. Our server looks up the name, refuses private and reserved addresses, and attempts four TLS handshakes to port 443, one per protocol version, without requesting a page. A version the server this tool runs on cannot offer is never offered to the site and shows as not tested. Each handshake stops after 2.5 seconds or 64 KiB, and the whole check after 10 seconds.
- 3
Read the handshakes, the certificate and the chain
Each protocol row reads Connected, with the protocol and cipher negotiated; Did not connect from our server; No answer within the time limit; or Not tested, when the server this tool runs on cannot offer that version. Below the rows are the certificate details, the time left, the name match, the names on the certificate and the chain the server presented, with a note wherever a list was cut.
- 4
Work through the checklist, then check again
Each checklist item says what was seen, what to do and the source it relies on, Fix items first, then Review, then Note. Copy the checklist as text for whoever manages the server, make the change, then run the check again.
What the SSL checker sends, and what it cannot see
First, the page takes the hostname out of what you typed and refuses an address with a user name or password, a port other than 443, or an IP address in place of a name. Our server then refuses a special-use name such as localhost or example.com, and asks DNS for the name's IPv4 and IPv6 addresses at the same time. It refuses the name if any address in an answer it reads is private or reserved. Once one answer has brought an address, our server waits a quarter of a second more for the other and does not read an answer that arrives later. It connects only to the first IPv4 address it read, or to the first IPv6 address when it read no IPv4 address, and attempts four TLS handshakes to port 443, one at a time and one version each: TLS 1.3, 1.2, 1.1 and 1.0. A version the server this tool runs on cannot offer is never offered to the site, and its row shows Not tested. No application data is sent and no page is requested. Each handshake stops after 2.5 seconds or 64 KiB of handshake data, and the whole check after 10 seconds. A handshake that gets no answer within its 2.5 seconds reads No answer within the time limit in its row, and the next handshake is attempted. A handshake that goes over 64 KiB, or a check that reaches its 10 seconds, stops the whole check, and the page shows only that error. Each check spends one slot, taken after our server checks the name and before it looks the name up in DNS, of a request limit counted in a shared store by your IP address (one IPv4 address, or one IPv6 /64 block) over a one-minute window, alongside an overall limit. What comes back is the name and port checked, the time of the check, a row for each handshake, the certificate and chain from the first handshake that connected, notes on how much of the chain was read and whether the handshakes presented different certificates, and the checklist. The address our server connected to stays on the server. When a check returns a result, the page sends one analytics event that names the tool and the page; nothing you typed or from the result goes with it. One server's handshakes at one time say nothing about other servers behind the same name. The tool does not check revocation, test ciphers one by one, or read HTTP headers or HSTS. There is no grade or score, and a check does not show you have permission to test a site.
What the protocol rows show, and what a failed handshake means
Each row is one handshake attempt limited to one protocol version, and it reads one of four ways. Connected means the handshake completed, and the row shows the protocol and cipher the two sides negotiated. Did not connect from our server means our server sent the ClientHello and the handshake did not complete. That does not prove the server has that version switched off, because the failure can come from a cipher mismatch, the network or our own runtime's settings. No answer within the time limit means the handshake did not finish within its 2.5 seconds, whether or not part of an answer came back. That does not prove the version is switched off either, because a firewall that drops the connection, the network or a slow server can each cause it. Not tested means our server never sent a ClientHello for that version, so the row says nothing about your site. The tool reads this from the first record our side wrote: RFC 9846 says a ClientHello is a handshake message carried in TLS records (section 4), and a record sent before encryption starts, as the ClientHello is, begins with its content type (section 5.1). The Node.js documentation says versions before TLS 1.2 may require downgrading the OpenSSL security level, which this check does not do, so TLS 1.0 and 1.1 may show as not tested. No row that did not connect, got no answer or was not tested is shown as a pass, a tick or disabled. A completed TLS 1.0 or 1.1 handshake is a finding, and the checklist marks it Fix. RFC 8996 says TLS 1.0 and TLS 1.1 must not be used, and that negotiation of either from any version of TLS must not be permitted. For clients, it says they must not send a ClientHello with ClientHello.client_version set to {03,01} or {03,02}, the values for those two versions. This tool still offers them where its runtime can, to see whether your server would agree to them. TLS 1.3 is specified in RFC 9846, published in July 2026, which obsoletes RFC 8446 and RFC 5246, the earlier TLS 1.3 and TLS 1.2 specifications. When the TLS 1.3 row reads Did not connect from our server while another handshake completed, the checklist adds a note to look at whether your server, load balancer or CDN offers TLS 1.3. A TLS 1.3 row that reads No answer within the time limit adds no note. Each connected row shows the one cipher that handshake negotiated.
Reading the certificate: dates, names and our server's check
The certificate view comes from the first handshake that connected, and the page says so when the handshakes presented different certificates. RFC 5280 defines the validity period as notBefore through notAfter, inclusive, and its path validation requires the period to include the current time. The tool counts whole days from the time of the check, shown in UTC. Fewer than 30 days left adds a renewal note; the 30 days is this tool's own threshold, not a rule. The CA/Browser Forum's Baseline Requirements, which their overview says are not mandatory for certificate authorities unless and until relying-party software suppliers adopt and enforce them, set the maximum validity period of a subscriber certificate at 200 days for one issued from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. For the name, the tool compares the hostname you checked with each DNS name in the certificate's subject alternative names, following RFC 9525, section 6.3: labels compared one by one with a case-insensitive ASCII comparison, and internationalised names in their A-label form. For a client that accepts wildcards, as this tool does, a wildcard counts only as the whole left-most label and stands for exactly one label, so *.example.com covers www.example.com but not example.com. RFC 9525 says the Common Name must not be used to identify a service, so the tool ignores it. Every name read is matched and the first 100 are listed; when the list reaches the 4,096 characters our server reads, a name not found is reported as possibly in the unread part. Accepted by our server's check is Node.js's own answer for the chain and the name. Its name check is a different implementation from the RFC 9525 comparison above, and the two can give different answers. Its documentation says that without a ca option it defaults to Mozilla's publicly trusted list, a snapshot fixed at release time, and that a runtime flag or setting can add the system's store or extra authorities. Your visitors' browsers run their own checks, and those are the ones that count.
The chain the server presented, and the order of the checklist
The chain list shows certificates the server sent, leaf first, following the issuer links Node.js built from them, up to five. It stops at the first certificate found in our server's own trust store, so a root certificate our server trusts is not listed. RFC 9846, section 4.5.1, says a certificate that specifies a trust anchor may be omitted from the chain, provided that supported peers are known to possess it, and that each following certificate should directly certify the one immediately before it. On a runtime that cannot list its whole trust store, only the leaf is shown, and the page says the rest of the chain was not examined. The Node.js documentation lists the function that provides that list, tls.getCACertificates, as added in versions 23.10.0 and 22.15.0. Either way, the list is what one handshake received, not a verdict that the chain is complete or valid in every client. The checklist lists every Fix first, then every Review, then every Note. Fix covers dates outside the validity period, a name that is not on the certificate and a completed TLS 1.0 or 1.1 handshake. RFC 9525, section 6.6, says a client that finds no matching name should end the connection with a bad certificate error. Review covers a No from our server's check, where the tool cannot see which check failed, so the item lists what to look at, including whether the server sends its intermediate certificates, and a name not found in a list that was cut. Notes cover fewer than 30 days left, dates that could not be read, and a TLS 1.3 row that reads Did not connect from our server while another handshake completed. Within each level, certificate items come before the renewal reminder and protocol settings. Each item says what was seen, what to do and its source, and the whole list can be copied as text for whoever manages the server. An empty checklist means none of these conditions was seen in the handshakes our server made at one time, and nothing more.
Sources
- IETF (RFC Editor): RFC 9846: The Transport Layer Security (TLS) Protocol Version 1.3
- IETF (RFC Editor): RFC 8996: Deprecating TLS 1.0 and TLS 1.1
- IETF (RFC Editor): RFC 9525: Service Identity in TLS
- IETF (RFC Editor): RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
- CA/Browser Forum: Baseline Requirements for the Issuance and Management of Publicly-Trusted TLS Server Certificates
- OpenJS Foundation (Node.js): TLS (SSL) | Node.js v26.13.1 Documentation
Worked example
An invented example, not taken from any site: an owner checks the shop hostname of a business site a fortnight before its certificate is due for renewal.
- Name checked
- The shop hostname, a subdomain of the business domain
- TLS 1.3 and TLS 1.2
- Connected
- TLS 1.1 and TLS 1.0
- Not tested: the server this tool runs on cannot offer them
- Names on the certificate
- Two DNS names: the business domain and its www hostname
- Accepted by our server's check
- No
- Time left
- 12 days at the time of the check
Three checklist items, in this order. Fix: the name is not on the certificate, because neither listed name is the shop hostname and no wildcard covers it (RFC 9525, section 6.3). Review: not accepted by our server's check, Node.js's own check of the chain and the name. Note: fewer than 30 days left, the tool's own reminder threshold. The two legacy rows bring no item, because neither was offered to the site, so they say nothing about it.
The owner asks the hosting provider to reissue the certificate with the shop hostname added, confirms that automatic renewal is switched on, and runs the check again once the new certificate is in place.
Who uses this tool
Site owners before a renewal date
See how many days the certificate has left, then confirm that the renewed certificate is the one the server presents.
Developers after a host, CDN or load balancer change
Check that the new setup presents a certificate with the right name, see which issuing certificates it sends with it, and confirm that TLS 1.3 and 1.2 handshakes still complete.
Teams retiring TLS 1.0 and 1.1
See whether a legacy handshake completes from our server. A row that did not connect is not proof on its own, and a Not tested row says nothing about your site.
Owners filling in a security questionnaire
Note the certificate details and protocol results seen, with the time of the check, before answering a question about them.
Frequently asked questions
What does the SSL checker send to my site?
Our server looks up the name in DNS, refuses it if it resolves to a private or reserved address, and attempts four TLS handshakes to port 443, one each for TLS 1.3, 1.2, 1.1 and 1.0. A version our server cannot offer is never offered to your site and shows as not tested. No page is requested. Each handshake stops after 2.5 seconds or 64 KiB, and the whole check after 10 seconds. Check only a site you own or have permission to check.
Does "Did not connect from our server" mean TLS 1.0 is turned off?
No. It means our server sent the handshake and it did not complete, which can come from a cipher mismatch, the network or our own runtime's settings. A row that reads Not tested was never offered to your site: the server this tool runs on cannot offer that version, so the row says nothing about the site. A completed TLS 1.0 or 1.1 handshake is a finding; a row that did not complete or was not tested proves nothing either way.
How does the tool decide whether the name matches the certificate?
It compares the hostname you checked with the DNS names in the certificate's subject alternative names, following RFC 9525, section 6.3: labels compared without regard to case and, for a client that accepts wildcards as this tool does, a wildcard counted only as the whole left-most label, matching exactly one label. So *.example.com covers www.example.com but not example.com. The Common Name is not used (RFC 9525, section 2). Your visitors' browsers run their own check, and that is the one that counts.
Why is the root certificate missing from the chain?
The list stops at the first certificate found in our server's own trust store, so a root certificate our server trusts is not listed. RFC 9846, section 4.5.1, says a certificate that specifies a trust anchor may be omitted from the chain when supported peers are known to possess it. The list shows what the server sent in one handshake; it is not a verdict that the chain is complete or valid in every client.
Does the checker test revocation or every cipher?
No. It does not check whether the certificate has been revoked, a check RFC 9525 (section 6) says a client should perform alongside the name check, and it does not test ciphers one by one: each row shows only the cipher that handshake negotiated. It does not read HTTP headers or HSTS either. The security headers checker and the HSTS checker cover those.
Does this checker give my site a grade?
No. There is no grade, score or pass mark. The checklist lists only what was seen, such as an expired certificate, a name that is not on it or a completed TLS 1.0 handshake, each with what to do and a source. An empty checklist covers only the handshakes our server made, at one time.