TLS / SSL
The cryptographic protocols that encrypt traffic between a browser and a server. TLS is the current standard; SSL is its outdated predecessor and should no longer be used.
Why 'SSL' is still used even though it is outdated
SSL, the original protocol, has known vulnerabilities and has been formally deprecated for years. TLS is its modern replacement, but the term "SSL" persists in everyday usage, certificate naming and product names out of habit.
What actually needs checking, not just installing
Having a certificate installed is not the same as having it configured securely. Outdated protocol versions, weak cipher suites, and certificates nearing expiration are all common gaps on servers that technically "have HTTPS" but are not actually well configured.
Frequently asked questions
Should I still support old SSL protocol versions for compatibility?
No. SSL 2.0 and 3.0, and increasingly early TLS versions, are considered insecure and should be disabled in favor of modern TLS versions only.
How do I check if my TLS configuration is actually secure, not just present?
Free online tools like SSL Labs' server test analyze protocol versions, cipher suites and certificate details, and highlight specific weaknesses beyond just confirming a certificate exists.
Does using TLS protect against every type of attack?
No. It protects data in transit between the browser and server from interception or tampering, but does nothing against server misconfiguration, weak credentials, or vulnerabilities in the application itself.
Want to see where your own server stands?
Run the free, read-only server check, or open the Security Lab and watch the detect, contain, recover, verify loop in action.
Get your free server checkOpen the Security Lab