SSL/TLS Checker
Retrieve certificate details and test modern TLS support.
How to Check SSL/TLS Certificates?
- Enter the hostname (e.g., example.com) without https://.
- Optionally change the port (default: 443 for HTTPS).
- Click Check to retrieve certificate details.
- View expiry date, issuer, subject, and TLS version support.
SSL/TLS Certificate Checker
Inspect SSL/TLS certificates for any domain and verify your HTTPS configuration is correct. An expired or misconfigured certificate causes browser warnings that drive users away and can hurt search rankings. This tool retrieves the full certificate chain and checks validity, expiry, and supported TLS versions without requiring any software installation.
What Gets Checked
- Certificate Expiry ā Days remaining before the certificate expires (get alerted before users see warnings)
- Issuer & Certificate Authority ā Who issued the certificate and whether it's a trusted CA
- Subject / Domain Coverage ā Verify the certificate covers your domain including wildcard and SAN entries
- TLS Version ā Confirm the server supports TLS 1.2/1.3 and has disabled deprecated TLS 1.0/1.1
Essential for webmasters, developers, and security teams doing pre-launch checks or monitoring certificate renewals.
Frequently Asked Questions
How do I check if my SSL certificate is expired?
Enter your domain name (without https://) and click Check. The tool shows the certificate expiry date and how many days remain. Certificates typically need renewal every 90 days (Let's Encrypt) or 1-2 years (commercial CAs).
What TLS versions should my server support?
Your server should support TLS 1.2 and TLS 1.3. TLS 1.0 and 1.1 are deprecated and should be disabled ā browsers show warnings and some refuse connections. Most modern servers and CDNs default to TLS 1.2+ already.
What is a wildcard SSL certificate?
A wildcard certificate (e.g. *.example.com) covers all first-level subdomains under a domain ā blog.example.com, api.example.com, etc. ā with a single certificate. It doesn't cover second-level subdomains like api.v2.example.com.
Why does my certificate show as invalid even though I installed it?
Common causes: the certificate chain is incomplete (intermediate CA certificates missing), the domain name doesn't match the certificate's subject/SANs, or the certificate was issued by an untrusted CA. This tool shows the full chain to help diagnose which issue applies.
