Cost
Free
Port
443
/ Free tool

SSL certificate checker

Enter a domain and the checker connects to it on port 443, the way a browser would, and reads the certificate it is given: the expiry date and days left, the issuer, the names it covers, whether the chain verifies against public roots, and the TLS version agreed. A certificate that has expired, names the wrong host or is missing an intermediate shows up here before your visitors see a warning.

One TLS connection to port 443. Nothing is stored.

/ Certificate guide

What each line means, and how to fix the usual faults

Most certificate outages are one of four things: it expired, it does not cover the name people type, the server sends it without its intermediate, or the server only speaks an old version of TLS. Each has a short fix.

How to read the result

The check makes one TLS connection to the address the domain resolves to, sends the domain as the server name, and verifies the certificate against the public root store our server trusts. It then reads the certificate itself, even when verification failed, so you can see what the server is actually sending.

  • Valid until and days left: the certificate's notAfter date. Browsers refuse the connection after it.
  • Names covered: the DNS names in the Subject Alternative Name extension. The name you entered has to match one of them.
  • Issuer: the certificate authority that signed it, or the certificate itself when it is self-signed.
  • Chain: whether a path from this certificate to a trusted root could be built from what the server sent.
  • Protocol and cipher: the TLS version and cipher suite the server agreed with us. The checker only offers TLS 1.2 and 1.3.

Expiry, and why renewal has to be automatic now

Certificates are issued for a fixed period and the period is getting shorter. Under the CA/Browser Forum Baseline Requirements, a publicly trusted certificate issued on or after 15 March 2026 can be valid for at most 200 days. From 15 March 2027 the limit is 100 days, and from 15 March 2029 it is 47 days.

At those lengths a renewal by hand once a year is no longer possible. Use a client that speaks ACME, the protocol in RFC 8555, so the certificate renews itself well before it runs out, and alert on the expiry date as well as on renewal errors. A renewal job that quietly stopped working is the usual reason a certificate expires on a site that had automation.

Incomplete chain: the missing intermediate

A server is meant to send its own certificate followed by the intermediates that lead to a root. RFC 8446 puts it this way: the sender's certificate must come first, and each following certificate should directly certify the one before it. The root itself may be left out, because clients already hold it.

When the intermediate is missing, some browsers can still find a way to a root and load the page, while other clients, such as apps, payment and webhook callers and command-line tools, refuse the connection. That is why a site can look fine in one browser and fail everywhere else. The fix is in the server configuration: point it at the full chain file your certificate authority or ACME client produced (for Certbot that is fullchain.pem), not at the single certificate.

Hostname mismatch and wildcards

Clients match the name you typed against the DNS names in the Subject Alternative Name list. RFC 9525 is explicit that the Common Name must not be used to identify a service, so a name that appears only in the Common Name does not count.

A wildcard covers exactly one label. *.example.com matches www.example.com and shop.example.com, but not example.com itself and not a.b.example.com. A site served on both example.com and www.example.com needs both names on the certificate.

Old TLS versions and failed handshakes

RFC 8996, published in March 2021, formally deprecates TLS 1.0 and 1.1. The checker offers TLS 1.2 and 1.3 only, so a server that can only speak an older version will fail the handshake here, and it will fail in current browsers too. The fix is to enable TLS 1.2 and 1.3 in the web server or load balancer and update the TLS library if it is too old to offer them.

A handshake can also fail because nothing answers TLS on port 443, because a firewall drops the connection, or because the server expects a different name. If the domain is meant to be served over HTTPS, all three are worth checking on the server itself.

What this check does not cover

It connects to one address on port 443 from our server. A site behind several servers or a CDN may hand out different certificates in different places. It does not list every cipher suite the server accepts, test revocation, or look at mail and other ports. For the HTTPS redirect and the security headers on the same domain, use the server health check or the security headers checker.

/ Questions

Questions people ask

How do I check when an SSL certificate expires?
Enter the domain above. The checker reads the certificate the server sends and shows the notAfter date with the number of days left. In a browser you can also open the certificate details from the padlock or site information icon in the address bar.
What does "unable to get local issuer certificate" mean?
The server sent its certificate without the intermediate that links it to a trusted root, so the chain could not be built. Configure the server with the full chain file rather than the certificate alone, then check again.
Does a wildcard certificate cover the bare domain?
No. *.example.com covers one label in front of example.com, such as www.example.com, but not example.com itself. Certificates that need both usually list example.com and *.example.com as two names.
How long can an SSL certificate be valid?
For publicly trusted certificates issued on or after 15 March 2026, at most 200 days under the CA/Browser Forum Baseline Requirements. The limit drops to 100 days from 15 March 2027 and to 47 days from 15 March 2029.
Is it SSL or TLS?
TLS. SSL is the name of the older protocols it replaced, but the word stuck to the certificates. A certificate sold as an SSL certificate is used for TLS connections.
Is the result stored?
No. The check runs when you ask, the result goes back to this page, and nothing about the domain or the result is saved.
/ Sources

Where each statement comes from

Checked against the sources on .