Free SSL Certificate Checker
Inspect TLS/SSL certificate chains, expiration countdowns, Subject Alternative Names (SAN), issuing Certificate Authorities (CA), and TLS protocol cipher strength on port 443.
Notice
Could not establish a TLS/SSL connection to port 443 on example.io.
- Verify that the web server is listening on TCP port 443 and that HTTPS is enabled
- Ensure network firewalls or security groups permit inbound HTTPS traffic from public resolvers
- The TLS handshake may have timed out (>5s) or failed due to an incompatible cipher suite or untrusted certificate
TLS Protocol Versions
Modern web encryption relies on TLS 1.2 and TLS 1.3 (RFC 8446). Legacy protocols (SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1) contain fundamental cryptographic vulnerabilities (such as POODLE and BEAST) and are deprecated across modern browsers.
Subject Alternative Names (SANs)
Subject Alternative Name (SAN) extension in X.509 certificates allows a single TLS certificate to secure multiple fully qualified domain names (FQDNs), including wildcard configurations (e.g., *.example.com). Modern browsers require valid SAN entries.
Automated Renewal Cycles
Industry standards led by the CA/Browser Forum require 90-day maximum certificate lifespans for automated CAs like Let's Encrypt, with proposals moving toward 45 days. ACME protocol clients handle renewal automatically to prevent unexpected site outages.
Frequently Asked Questions
What does this SSL certificate check verify?
What are Subject Alternative Names (SANs) and why are they needed?
example.com and www.example.com under one certificate). Modern browsers require valid SAN entries for TLS verification.