← Back to the security guide
SSL/TLS SecurityHigh risk

Server accepts outdated or weak TLS configuration

What does this mean?

Your SSL certificate itself may be perfectly valid, but the server is still willing to negotiate an outdated protocol version (TLS 1.0 or 1.1, both deprecated industry-wide since 2021) or a weak cipher when a client asks for one. An attacker positioned between a visitor and your server can sometimes force this weaker connection deliberately, then exploit known cryptographic weaknesses in it — a class of attack broadly known as a protocol downgrade.

What are the potential impacts?

  • An attacker positioned on the network path between a visitor and your server can sometimes force the connection down to an older, weaker protocol before exploiting known vulnerabilities in it — this is exactly the class of attack POODLE and BEAST specifically targeted.
  • Compliance frameworks including PCI-DSS explicitly require disabling TLS 1.0/1.1 — accepting them can be a real problem if you ever handle payment data directly, even if no attack has happened yet.
  • This typically doesn't affect the average visitor's everyday browsing, since modern browsers already prefer the strongest available protocol — the real risk is to anyone actively targeted by a network-level attacker, e.g. on public wifi or a compromised router.

How to fix it

This is a server/web-server configuration change, not something fixed by renewing your certificate. On most modern hosts, disabling TLS 1.0/1.1 and weak ciphers is a checkbox in your hosting or CDN dashboard (Cloudflare, for example, has an explicit "Minimum TLS Version" setting). If you manage your own server, the fix lives in your TLS termination point's config (nginx's ssl_protocols / ssl_ciphers directives, for example) — ask your host or developer if you're not comfortable making the change yourself.

Want to see whether this actually affects your site? Run a free scan — no signup required.

Run a free scan