About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
A finding such as "TLS 1.0 enabled" or "TLS 1.1 enabled" means the scanner completed a handshake with your server using that protocol version. RFC 8996 (BCP 195) says TLS 1.0 and TLS 1.1 "MUST NOT be used", so the finding is valid whenever it is true. First prove it with openssl s_client against the address the scanner tested, then restrict the protocols in nginx with ssl_protocols or in Apache with SSLProtocol, and test again.
What the finding means
RFC 8996, published in March 2021, "formally deprecates Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346)" and moves them to Historic status. Section 4 says "TLS 1.0 MUST NOT be used." and, in its next sentence, "Negotiation of TLS 1.0 from any version of TLS MUST NOT be permitted." The same sentences appear for TLS 1.1. TLS 1.2 and TLS 1.3 remain.
Two defaults produce the finding on web servers:
- Apache: the
SSLProtocoldefault isall -SSLv3(up to 2.4.16:all). The mod_ssl page definesallas includingTLSv1,TLSv1.1,TLSv1.2andTLSv1.3, depending on the OpenSSL version. A default Apache can therefore offer TLS 1.0 and 1.1. - nginx: the current default for
ssl_protocolsisTLSv1.2 TLSv1.3. The nginx CHANGES file records that in nginx 1.27.3 (26 Nov 2024) "now TLSv1 and TLSv1.1 protocols are disabled by default". An older nginx with nossl_protocolsline still offers them.
The finding can also come from a device in front of the server, a different port, or a different virtual host, so the first job is to test the address and name the scanner used.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
nginx older than 1.27.3 and no ssl_protocols line |
s_client -tls1 and -tls1_1 connect |
nginx -v shows an older version; nginx -T has no ssl_protocols |
ssl_protocols or SSLProtocol lists the old versions explicitly |
Same | The directive in nginx -T or the Apache configuration includes TLSv1 or TLSv1.1, or all |
Apache default or SSLProtocol all |
Same | apachectl -v and the configuration show no restricting SSLProtocol |
| Setting is in a virtual host that the connection does not use | The setting is present but the scan still finds the versions | Test with and without -servername; the nginx page says a server-level value "from the default server can be used", and the Apache page says per-host SSLProtocol is honoured only from 2.4.42 with OpenSSL 1.1.1 or later |
| The scanner reached another device or port | The server tests clean but the scan does not | Test the same address and port the scanner reported, from outside |
| Another service on the host | The finding names a port that is not 443 | That service has its own protocol setting; this fix covers web servers only |
Prove the cause before changing anything
All of these are read-only.
1. Test each protocol version. The openssl s_client manual lists -tls1, -tls1_1, -tls1_2 and -tls1_3 among its options, -servername to name the site, and -brief for a short summary. Use the host name and port the scanner reported:
openssl s_client -connect app.example.com:443 -servername app.example.com -tls1_2 -brief
openssl s_client -connect app.example.com:443 -servername app.example.com -tls1_1 -brief
openssl s_client -connect app.example.com:443 -servername app.example.com -tls1 -brief
The first is a control: it should connect. If it fails, the test tool is not working and the other two prove nothing. A bad result for the finding is a connection summary naming TLS 1.1 or TLS 1.0 on the second or third command. A good result is a failed handshake on both. A failure can have a local cause as well as a server cause, so confirm it with the next check.
2. Ask a scanner built for it. The nmap documentation for the ssl-enum-ciphers script says it "repeatedly initiates SSLv3/TLS connections" and lists the ciphersuites a server accepts under a heading for each protocol, such as TLSv1.0: and TLSv1.2:. It also says the script is intrusive and "quite noisy", so run it only against servers you operate:
nmap -sV --script ssl-enum-ciphers -p 443 app.example.com
If a TLSv1.0: or TLSv1.1: heading appears, the server accepts that version.
3. Which software and which setting. The nginx page says -v prints the version and -T tests the configuration and dumps it to standard output. Apache's -v prints its version:
nginx -v
nginx -T
apachectl -v
Find every ssl_protocols line in the nginx -T output and every SSLProtocol line in the Apache configuration files. Note the context of each: http, server, or a virtual host.
4. Who still uses the old versions. Before you cut them off, find out whether anything real depends on them. The mod_ssl page shows a log format that records the protocol of each request, %{SSL_PROTOCOL}x, and the variable SSL_PROTOCOL holds the version. In nginx, the ngx_http_ssl_module page lists the embedded variable $ssl_protocol, which "returns the protocol of an established SSL connection", and the ngx_http_log_module page describes log_format for adding it to a log. A log of that value over a business week shows old clients that would break.
Fix
nginx
The nginx page gives ssl_protocols TLSv1.2 TLSv1.3; as the example and as the default. The directive's context is http and server. The page says the TLSv1.3 parameter "works only when OpenSSL 1.1.1 or higher is used". The CHANGES file records that ssl_protocols works in virtual servers other than the default server from 1.29.2 (07 Oct 2025) onward when OpenSSL 1.1.1 or newer is used. On earlier versions, put the directive in the http block or in the default server for that address and port.
First save the current file (use the file nginx -T shows for the setting; the path here is a placeholder):
cp -p /etc/nginx/nginx.conf /etc/nginx/nginx.conf.2026-11-22
Risk: the next edit makes the server refuse TLS 1.0 and TLS 1.1 handshakes. Clients that cannot use TLS 1.2, such as old appliances, old Java or Windows versions, or old payment and scanner devices, will lose access to the site.
Set the directive inside the http block (or edit the existing line if one lists the old versions):
ssl_protocols TLSv1.2 TLSv1.3;
Check the configuration and reload. The nginx page says -t tests the configuration and -s reload loads it while old workers shut down gracefully:
nginx -t && nginx -s reload
To undo it: put the saved file back, test it, and reload.
cp -p /etc/nginx/nginx.conf.2026-11-22 /etc/nginx/nginx.conf
nginx -t && nginx -s reload
Apache
The mod_ssl page gives the syntax SSLProtocol [+|-]protocol ... and the all shortcut. Removing the two old versions from all leaves the rest as the module defines it. Put the directive in the server-wide configuration, or in the base virtual host. The page says that before OpenSSL 1.1.1 the protocol negotiated was always the base virtual host's, the first one declared on the address and port, and that from Apache 2.4.42 with OpenSSL 1.1.1 or later each name-based virtual host's own setting is honoured when the client sends a server name.
First save the current file (placeholder path; use the file that holds SSLProtocol or the virtual host):
cp -p /usr/local/apache2/conf/extra/httpd-ssl.conf /usr/local/apache2/conf/extra/httpd-ssl.conf.2026-11-22
Risk: the next edit makes Apache refuse TLS 1.0 and TLS 1.1 handshakes for every site that uses this setting. Clients that cannot use TLS 1.2 will lose access.
Set or replace the SSLProtocol line:
SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
Check the configuration and restart gracefully, which the apachectl page says does not abort open connections:
apachectl configtest
apachectl graceful
To undo it: restore the saved file, check it, and restart gracefully again.
cp -p /usr/local/apache2/conf/extra/httpd-ssl.conf.2026-11-22 /usr/local/apache2/conf/extra/httpd-ssl.conf
apachectl configtest
apachectl graceful
A device or service in front of the server
If the test in step 1 shows the old versions on the load balancer, CDN or appliance, the setting is on that device, in that product's own console. The web server's setting does not affect connections that end on the device.
First record the device's current protocol setting, by exporting its configuration or taking a screenshot of the protocol page, and keep the record.
Risk: the next change makes the device refuse TLS 1.0 and TLS 1.1 handshakes for every site behind it. Clients that cannot use TLS 1.2 will lose access to all of them.
Set the device's minimum or allowed protocol versions to TLS 1.2 and TLS 1.3 as its console describes, then repeat the three s_client commands from step 1 against the device's address.
To undo it: set the protocol versions back to those in the record you made first, then repeat the s_client commands.
Example (illustrative): a scan of app.example.com (203.0.113.30) reports TLS 1.0 and TLS 1.1 enabled on port 443. nginx -v on web01 shows 1.26.2, which is older than 1.27.3, and nginx -T contains no ssl_protocols line. The three s_client commands connect for -tls1_2, -tls1_1 and -tls1. The administrator saves nginx.conf, adds ssl_protocols TLSv1.2 TLSv1.3; to the http block, runs nginx -t and nginx -s reload. Afterwards -tls1_2 connects, -tls1_1 and -tls1 fail, and nmap shows a TLSv1.2: heading and no TLSv1.0: or TLSv1.1: heading.
Confirm the fix
- The
-tls1_2control connects, and-tls1_1and-tls1fail, for each host name on the address. nmap -sV --script ssl-enum-ciphers -p 443 app.example.comlists noTLSv1.0:orTLSv1.1:heading.- The site still loads from a current browser and from the monitoring and integration clients you listed.
- A fresh scan no longer reports the finding.
What to watch afterwards
- Connection failures from one client or device after the change: use the log of
SSL_PROTOCOLvalues to identify it and decide whether to upgrade that client. - New virtual hosts and new servers copied from old templates: check them with the same three commands.
- Other ports on the same host. A mail or database service can show the same finding and has its own setting.
- A security questionnaire answer such as "TLS 1.2 and TLS 1.3 only" is true only for the addresses and ports you tested, on the date you tested them. Keep the command output with the answer.
Read next
Related articles you may want next.
- TroubleshootingTLS handshake failure: no shared protocol or cipher, read the s_client error and the Schannel eventsslv3 alert handshake failure, no protocols available or Schannel 36874: prove which side lacks a shared TLS version or cipher, fix it and confirm.Read article
- HostingShorter TLS certificate lifetimes: the 2026 to 2029 schedule and what to automateThe CA/Browser Forum schedule cutting TLS certificate lifetimes to 200, 100 and 47 days, and how to decide which renewals to automate first.Read article
- VMwareHow to harden VMware without breaking operations or recoveryStage VMware identity, permissions, management access, logging and key recovery controls with positive and negative tests.Read article
Risks and limits
- These commands have not been run or lab-tested.
- RFC 8996 states a requirement for implementations. This is not a statement of what any particular law, contract or compliance scheme requires of you; read the requirement the finding cites.
- A failed old-version test with
openssl s_clientis proof of a server setting only when the-tls1_2control connects. - The nginx and Apache defaults quoted are those of the documentation pages named below; a packaged build or a distribution's configuration files may set their own values.
- nmap sends many connections. Do not run it against systems you do not operate.
Sources
- RFC 8996: Deprecating TLS 1.0 and TLS 1.1 — IETF, March 2021, accessed 22 November 2026
- Module ngx_http_ssl_module — nginx documentation, no date shown, accessed 22 November 2026
- nginx changes — nginx project, entries dated individually, accessed 22 November 2026
- Module ngx_http_log_module — nginx documentation, no date shown, accessed 22 November 2026
- Command-line parameters — nginx documentation, no date shown, accessed 22 November 2026
- mod_ssl: SSLProtocol — Apache HTTP Server 2.4 documentation, no date shown, accessed 22 November 2026
- apachectl — Apache HTTP Server 2.4 documentation, no date shown, accessed 22 November 2026
- httpd — Apache HTTP Server 2.4 documentation, no date shown, accessed 22 November 2026
- openssl-s_client — OpenSSL 3.0 documentation, no date shown, accessed 22 November 2026
- ssl-enum-ciphers NSE script — Nmap Scripting Engine documentation, no date shown, accessed 22 November 2026
- cp(1) — GNU coreutils 9.11 manual page, April 2026, accessed 22 November 2026
This article was originally published on .