SSL/TLS Overview
SSL/TLS protocols secure communication between web browsers and servers. Our analyzer checks certificate validity, protocol support, and security configuration.
Grading System
A+/A: Excellent security
B: Good security
C: Fair security
D/F: Poor/Insecure
Security Headers
HSTS prevents downgrade attacks, CSP prevents XSS, and other headers enhance overall security posture of your website.
Best Practices
Use TLS 1.2+, strong ciphers (256-bit), valid certificates from trusted CAs, and implement security headers like HSTS.
Where to look next
A certificate is served by a specific machine on a specific network, and knowing which one often explains the result above. Run the hostname's address through the IP address lookup to see the hosting provider and network behind it — that quickly reveals whether you are inspecting the origin server or a CDN edge node, which is the usual reason a certificate looks different from the one you believe you installed.
TLS also has a direct performance cost. The handshake happens before any content can be sent, so a slow or misconfigured setup shows up as inflated time to first byte. If pages feel sluggish, the website speed test measures TTFB and total server response time, letting you see whether the delay is in the connection setup or in the application behind it. Certificate chains that are incomplete are a common culprit, since clients must then fetch the missing intermediate themselves.
Finally, a certificate is only valid for the hostnames it lists. When a name mismatch error appears, confirm what the name actually resolves to with the DNS record lookup before changing anything on the certificate itself.