SSL Certificate Checker

Paste the chain from openssl s_client and check expiry, hostname coverage, weak keys, SHA-1 signatures and chain order. Parsed locally, nothing uploaded.

The interactive tool loads here when JavaScript runs.

About this tool

What is SSL Certificate Checker?

The SSL Certificate Checker reviews the certificate chain a TLS server sends. You enter the hostname, copy the generated openssl s_client command, run it in a terminal and paste the output. The checker then reports days until expiry, whether the hostname is covered by the Subject Alternative Names, key size, signature algorithm, self-signed status and whether each certificate was issued by the next one in the list.

It works this way because a web page cannot see another site's certificate. Browsers complete the TLS handshake themselves and never hand the certificate to JavaScript, so any in-browser "checker" that claims to fetch it is either calling a server somewhere or making the result up. Parsing happens in your tab; the pasted chain is not uploaded.

The checks are offline and structural. The tool does not verify the cryptographic signatures between certificates, does not compare the root with a browser trust store and does not query OCSP or CRLs for revocation. Use it to catch the everyday failures: an expired leaf, a missing intermediate, a hostname that is not on the certificate, or a chain served in the wrong order.

  • Days to expiry, not-yet-valid and expired detection
  • Hostname matching against SANs with RFC 6125 wildcard rules
  • Weak key (RSA under 2048 bits) and SHA-1 or MD5 signature flags
  • Chain order and missing-intermediate checks
  • Ready-to-copy openssl s_client command; parsing runs in the browser
Read the guide: How to Read an X.509 Certificate and Debug a TLS Chain

Updated

How to use SSL Certificate Checker

  1. Type the hostname into the input at the top, for example example.com. The command below it updates as you type.
  2. Click Copy openssl Command and run it in a terminal. It connects to port 443 with SNI and prints every certificate the server sends.
  3. Paste the output into the chain box. Everything outside the BEGIN and END CERTIFICATE lines is ignored.
  4. Click Check Certificate and read the Checks list first, then the details, SANs and chain order.
  5. Use Load Sample to see a two-certificate chain for www.example.com with an RSA leaf and an EC P-256 root.

Worked examples

The sample chain

Input

Hostname www.example.com, leaf CN=www.example.com followed by CN=Example Test Root CA

Output

Hostname matches; key RSA 2048 bits; signature ecdsa-with-SHA256; chain in order; SANs DNS:www.example.com, DNS:example.com, IP:192.0.2.10

The leaf expires on 1 January 2027, so the expiry check turns to a warning inside the last 30 days and a failure after that date. Swap the two PEM blocks and the tool reports that the first certificate is a CA and that the chain is out of order.

A bare domain on a wildcard certificate

Input

Hostname example.com, SAN list DNS:*.example.com only

Output

Hostname mismatch

A wildcard covers exactly one label to the left of the domain. The bare domain has to be listed as its own SAN entry.

Background and insight

Since Chrome 58 (2017), browsers match the hostname only against the Subject Alternative Name extension and ignore the Common Name. RFC 6125 also limits wildcards: *.example.com covers www.example.com but not example.com and not a.b.example.com. A surprising number of outages come from a certificate that lists the www name but not the bare domain, or the other way round.

Servers are expected to send the leaf followed by the intermediates, each one issued by the next. Clients do not fetch missing intermediates reliably (some desktop browsers do via the AIA extension, most HTTP libraries and mobile apps do not), which is why a site can look fine in Chrome and fail in curl with "unable to get local issuer certificate". The root itself does not need to be sent.

Public TLS certificates have been capped at 398 days of validity since September 2020, and the CA/Browser Forum has voted to shorten that further over the next few years. Short lifetimes make automated renewal (ACME clients such as certbot renew at around 30 days left) the norm, so an expiry warning usually means automation has stopped working.

Common use cases

  • Diagnosing "certificate not valid" reports

    Check expiry, hostname coverage and chain order from the exact bytes the server sends, rather than what a cached browser session shows.

  • Checking a load balancer after renewal

    Confirm the new certificate is the one being served and that the intermediate bundle was uploaded with it.

  • Reviewing internal services

    Spot self-signed certificates, 1024-bit keys and SHA-1 signatures on older internal endpoints.

  • Explaining a curl failure

    When curl says it cannot get the local issuer certificate but the browser works, check whether the server sends its intermediates.

Tips and limitations

  • Always pass -servername. Without SNI, many servers return a default certificate for a different host.
  • The tool checks structure, not trust: a chain that passes here can still fail if the root is not in the client's trust store or a certificate was revoked.
  • If only one certificate appears in the openssl output, the server is not sending intermediates. Fix the server bundle rather than relying on clients to fetch them.
  • Warnings start at 30 days and become urgent at 14. If you see one on an ACME-managed site, check the renewal job, not just the certificate.
  • For a deeper look at a single certificate (extensions, OCSP and CRL URLs, fingerprints) paste it into the X.509 Parser.

Sources and further reading

  1. RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile, IETF. The certificate format, extensions and path validation rules
  2. RFC 6125: Representation and Verification of Domain-Based Application Service Identity, IETF. Hostname matching and the wildcard rules
  3. Baseline Requirements for TLS Server Certificates, CA/Browser Forum. The industry rules that cap public certificate lifetimes
  4. RFC 8555: Automatic Certificate Management Environment (ACME), IETF. The protocol behind automated renewal with clients such as certbot

Frequently asked questions

Why can't this SSL checker just fetch the certificate from a URL?

Browsers do not expose a site's TLS certificate to JavaScript, so a page cannot read it directly. Services that check from a URL run the connection on their own servers. This tool keeps everything local by analysing the chain you fetch with the openssl command it generates.

What does "unable to get local issuer certificate" mean?

It means the client could not build a path from the server certificate to a trusted root, usually because the server did not send its intermediate certificate. Paste the openssl output here: if only one certificate appears, add the intermediate to the server's certificate bundle.

Does a wildcard certificate cover the bare domain?

No. A SAN of *.example.com matches www.example.com or api.example.com, but not example.com itself and not deeper names like a.b.example.com. Certificates that need the bare domain list it as a second SAN entry, which is what the sample certificate does.

Does this checker verify revocation or the trust chain?

No. It parses the certificates and checks dates, names, key sizes, signature algorithms and issuer-to-subject order. It does not verify signatures, consult OCSP or CRLs, or compare the root with a trust store, so treat a clean result as structurally sound rather than fully trusted.

How many days before expiry should a certificate be renewed?

Around 30 days before expiry is the common practice, and ACME clients such as certbot renew at that point by default. The checker warns below 30 days and flags anything under 14 days as urgent, because that usually means automated renewal has failed silently.

Why does my certificate work in Chrome but fail in curl or a mobile app?

Desktop browsers often fill in a missing intermediate from their cache or the AIA URL, while curl, most libraries and many apps do not. If the server sends only the leaf certificate, the browser hides the mistake and everything else fails.

Is there an in-depth guide to SSL Certificate Checker?

Yes. “How to Read an X.509 Certificate and Debug a TLS Chain” covers the background, how it works, common pitfalls and worked examples. Read the full guide.