Server accepts TLS 1.0 / 1.1
TLS 1.0 and 1.1 are deprecated and vulnerable to several attacks. A server that still accepts them lets clients — or an attacker forcing a downgrade — negotiate a weak connection.
Why it matters
Weak protocol versions enable downgrade and padding-oracle style attacks against otherwise-secure traffic.
PCI DSS and modern baselines require TLS 1.2 or higher; accepting older versions is a direct compliance finding.
How to check for it
- Test with an external SSL checker, or: nmap --script ssl-enum-ciphers -p 443 <host> lists the protocols offered.
- Review the TLS config of your web server, load balancer or CDN for a minimum version setting.
How to fix it
- Set the minimum TLS version to 1.2 (prefer 1.3) on the server, load balancer or CDN, and disable 1.0/1.1.
- Keep a modern cipher suite list and disable known-weak ciphers.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Will requiring TLS 1.2 break old clients?
- Only very old browsers and devices; all current browsers and OSes support TLS 1.2+, so the impact is usually negligible.