How to fix: TLS Certificate Expiry
Async check: opens a TLS connection to :443 and reports the certificate validity window, expiry, self-signing, and incomplete chains.
Why it matters
An expired or self-signed certificate breaks HTTPS trust and exposes users to MITM attacks.
TLS certificates are short-lived by design. The scan opens a TLS connection (not just an HTTP request) so it can inspect the leaf certificate and chain directly.
How to fix it
- 1Renew the certificate via your CA (Let's Encrypt is free).
- 2Enable auto-renewal (certbot, Caddy, or hosting-provider automation).
- 3Verify the chain: openssl s_client -connect example.com:443 -showcerts.
Code examples
OpenSSL verification
openssl s_client -connect example.com:443 -showcerts < /dev/null | openssl x509 -noout -dates -subject -issuerReferences
Detected automatically by VulnRadar. The check id is tls-certificate-expiry, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is TLS Certificate Expiry?
- VulnRadar rates this high severity in the tls category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id tls-certificate-expiry, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does TLS Certificate Expiry map to?
- It maps to CWE-298. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.