How to fix: TLS 1.3 Not Supported
The server does not offer TLS 1.3. Connections fall back to TLS 1.2, which lacks TLS 1.3's 0-RTT resumption, reduced round-trip handshake, and mandatory forward-secrecy-only cipher suites.
Why it matters
Without TLS 1.3, clients miss improved forward secrecy and the cleaner cipher-suite design that eliminates weak algorithms at the protocol level. TLS 1.2 remains safe but requires more careful cipher configuration.
TLS 1.3 removes support for all non-AEAD ciphers, weak key exchange, and the legacy handshake format. It also adds 0-RTT resumption and reduces handshake latency by one round-trip. Enabling it alongside TLS 1.2 is backward compatible.
How to fix it
- 1Add TLSv1.3 to ssl_protocols in nginx.
- 2Ensure OpenSSL 1.1.1 or later is installed.
Code examples
Nginx
ssl_protocols TLSv1.2 TLSv1.3;
ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305;
ssl_prefer_server_ciphers off;References
Detected automatically by VulnRadar. The check id is tls-tls-1-3-not-supported, stable across every scan so you can filter or diff on it.
More tls checks
Questions
- How severe is TLS 1.3 Not Supported?
- VulnRadar rates this info 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-tls-1-3-not-supported, which stays the same between runs so you can filter, diff, or gate CI on it.
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.