🚫
blog.cat.ssl

Disabling TLS 1.0 and 1.1: Why It Matters and How to Do It

18.11.2026
← All articles

TLS 1.0 dates from 1999 and TLS 1.1 from 2006. They were solid for their time, but cryptography has moved on and weaknesses were found one after another. In 2021 the IETF formally deprecated both versions in RFC 8996, and major browsers had dropped them even earlier. Yet many servers still accept them, often simply because nobody switched them off.

What is wrong with the old versions

TLS 1.0 and 1.1 rely on outdated building blocks: a combination of MD5 and SHA-1 for integrity and no support for modern AEAD ciphers. Attacks such as BEAST and POODLE exploited these old mechanisms. Patches mitigated many of them, but the protocols no longer meet current security expectations. Accepting old versions also widens the room for downgrade attempts, and PCI DSS requires systems that handle card payments to move away from early TLS.

Who is affected

TLS 1.2 is available on practically every device, and current Chrome, Firefox, Safari and Edge already refuse the old versions. Problems appear only with very old clients: Android phones more than a decade old, unpatched legacy operating systems, and long-neglected accounting software, point-of-sale devices or internal scripts that call your site.

Check your logs first

Nginx can log the protocol of each request with $ssl_protocol:

http {
    log_format tlslog '$remote_addr [$time_local] $ssl_protocol '
                      '$ssl_cipher "$http_user_agent"';

    server {
        listen 443 ssl;
        server_name example.uz;
        access_log /var/log/nginx/example.uz-tls.log tlslog;
    }
}

After a few days, count requests by version:

awk '{print $4}' /var/log/nginx/example.uz-tls.log | sort | uniq -c | sort -rn

Lines with TLSv1 or TLSv1.1 are usually bots, old monitors or scanners. A wholesale company in Andijan running a dealer portal on misol.uz might find that nearly all TLS 1.0 traffic comes from one IP: an old warehouse PC that uploads stock levels. Updating that machine first means switching off old TLS causes no outage.

Disabling in Nginx and Apache

server {
    listen 443 ssl;
    server_name example.uz;

    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_prefer_server_ciphers off;
}

When several server blocks share an IP and port, the protocol list effectively comes from the default server, so keep it identical everywhere. Run nginx -t and systemctl reload nginx. In Apache with mod_ssl:

SSLProtocol -all +TLSv1.2 +TLSv1.3

If your OpenSSL is too old for TLS 1.3, drop +TLSv1.3 and plan an upgrade. Check with apachectl configtest before reloading.

Verifying the result

Recent OpenSSL builds may refuse TLS 1.1 on the client side because of their security level, so lower it for the test:

openssl s_client -connect example.uz:443 -servername example.uz \
  -tls1_1 -cipher 'DEFAULT:@SECLEVEL=0' < /dev/null

A handshake failure means TLS 1.1 is off; the same command with -tls1_2 should succeed. For a full picture:

nmap --script ssl-enum-ciphers -p 443 example.uz

Only TLSv1.2 and TLSv1.3 sections should remain.

Hosted sites and partner integrations

If a partner system or an internal script stops working right after the change, check its runtime before re-enabling anything. Very often an old PHP, Java or .NET runtime, or an outdated operating system library, is the real cause, and updating it fixes the problem permanently instead of keeping the whole server exposed for one client. Announce the change to partners a week or two in advance so they have time to test.

On shared hosting, protocol versions are set server-wide by the provider and cannot be changed in .htaccess; ask sayt.uz support from the cabinet if in doubt.

Related articles

🔑 ECDSA or RSA Certificates: Speed, Security and Compatibility 🛡️ Cloudflare Origin Certificates: When to Use Them and When Not To 🔐 ERR_CERT_COMMON_NAME_INVALID: when the SSL certificate name does not match 🔐 acme.sh: Issuing and Renewing SSL Certificates on a VPS
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓