Website security · Raksha guide

SSL Certificate Check: Expiry, Chain and TLS Version

An SSL certificate check examines the certificate actually served for a hostname: its dates, names and trust chain. TLS protocol and cipher testing is a separate task. A working HTTPS request does not prove that every protocol, virtual host or edge location is configured safely.

By Raksha · Reviewed 16 November 2026

What to check

Certificate and protocol checks answer different questions
CheckQuestionImportant detail
Validity datesIs the certificate valid now, and when does it expire?Check renewal and deployment, not just issuance.
Subject Alternative NamesDoes the certificate cover the requested hostname?An apex domain and its subdomains are not interchangeable.
Trust chainCan a client build a chain to a trusted root?Missing intermediates can fail on some clients even if your browser works.
TLS versionsWhich protocol versions can the server negotiate?Disable deprecated TLS 1.0 and 1.1; review TLS 1.2 and 1.3 configuration.
Cipher suites and deploymentAre compatible, appropriate algorithms used consistently?Test separately across endpoints, proxies and CDNs.

How to check with OpenSSL

Use the hostname you are authorised to test. SNI selects the correct virtual host; hostname verification checks the certificate name.

openssl s_client -connect example.com:443 -servername example.com \
  -verify_hostname example.com -verify_return_error -showcerts </dev/null

# Print the served leaf certificate dates and names
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
  | openssl x509 -noout -dates -issuer -subject -ext subjectAltName

The second command prints certificate information; it does not independently establish trusted validation. Review the first command’s verification result using a correctly configured local trust store.

Check TLS versions separately

openssl s_client -connect example.com:443 -servername example.com -tls1_2 </dev/null
openssl s_client -connect example.com:443 -servername example.com -tls1_3 </dev/null

These commands test two negotiations, not every cipher or legacy protocol. A failed handshake can reflect the local OpenSSL build or network restrictions. Use a dedicated tool such as SSL Labs for a broader public TLS assessment, and do not disable certificate validation with curl -k to make a failing check appear successful.

What grades and renewal dates mean

A TLS grade belongs to that tool’s methodology; it is not Raksha’s security score and does not assess application authorisation. TLS 1.2 can remain appropriate with secure configuration; TLS 1.0 and 1.1 are deprecated by RFC 8996.

Publicly trusted certificate lifetime requirements are changing. Follow your certificate authority’s current rules, automate renewal and alert on the certificate served in production. A renewed certificate that was never deployed still leaves visitors with an expiring one.

What Raksha checks and what needs a dedicated tool

Raksha’s public scan observes HTTPS reachability, served redirects and HTTP protections such as HSTS. It is not a comprehensive certificate-chain inventory or exhaustive TLS protocol and cipher scanner. Use the commands above or a specialised TLS tool for that deeper coverage.

Review HSTS and other browser protections

What should I fix first?

Prioritise expired certificates, hostname mismatches and untrusted chains that break validated connections. Then address deprecated protocols, renewal reliability and HTTPS coverage across the intended scope.

Sources and further reading

Consult current official documentation before changing a production system. Examples are illustrative, not live findings or universal configurations.

Start with a site you are authorised to test

A free passive check needs no card. Sign-in, email confirmation, ownership rules and usage limits apply. It is not an unrestricted penetration test.