فاحص شهادات SSL
تحقق من تفاصيل شهادة SSL وتاريخ انتهائها
What Does This Tool Check?
Our SSL Certificate Checker performs a comprehensive real-time analysis of any website's SSL/TLS certificate. Unlike basic checkers that only tell you "valid or not," our tool digs deep into every aspect of your certificate:
Certificate Validity & Expiry Countdown — instantly see if your certificate is valid, with a visual countdown ring showing exactly how many days remain. The color-coded indicator turns green (healthy), yellow (expiring soon), or red (critical) so you can spot problems at a glance.
Certificate Details — view the Common Name (CN), organization, issuer (Certificate Authority), valid from/to dates, key type and strength (RSA/ECDSA with bit count), signature algorithm, and serial number.
Certificate Chain Verification — see the full trust chain from your domain certificate through intermediate certificates to the root CA. Missing intermediate certificates are one of the most common SSL issues — our tool makes them immediately visible.
Subject Alternative Names (SAN) — see every domain and subdomain covered by the certificate. This is critical for wildcard and multi-domain certificates where you need to verify coverage.
Custom Port Support — unlike most SSL checkers that only check port 443, you can specify any port (e.g., 8443, 993 for IMAP, 465 for SMTP, 636 for LDAPS). This makes our tool invaluable for checking SSL on mail servers, APIs, and non-standard configurations.
How to Use This Tool
- Enter the domain name (e.g.,
google.com) - Optionally specify a custom port (default is 443)
- Click Check SSL
- Review the comprehensive results including validity, expiry countdown, certificate details, chain, and SANs
Why Regular SSL Checks Matter
Expired certificates kill traffic. When your SSL expires, browsers show a full-page warning that scares away visitors. Google may drop your pages from results. Your traffic can fall to zero in hours.
Broken chains cause mobile issues. A missing intermediate certificate works on some browsers (desktop Chrome) but fails on others (mobile Safari, older Android). Our chain verification catches this.
Weak encryption is a vulnerability. Older certificates may use deprecated algorithms (SHA-1) or weak key sizes. Our tool shows key type and bit strength so you can verify your security meets current standards.
SAN misconfiguration loses coverage. If your wildcard certificate does not cover a new subdomain, that subdomain shows as insecure. Check SANs regularly when adding subdomains.
For a deeper understanding of SSL certificates, read our comprehensive SSL Certificate Guide. Also check your server status, DNS records, and HTTP-to-HTTPS redirects for a complete security audit.
Frequently Asked Questions
How often should I check my SSL certificate?
At minimum monthly, and always after any server or DNS changes. If your certificate auto-renews (Let's Encrypt), check that renewal is actually working. Set a calendar reminder 30 days before expiry as a safety net.
What does "Certificate Chain Incomplete" mean?
Your server is not sending the intermediate certificate(s) between your domain certificate and the root CA. While some browsers can fetch missing intermediates automatically, many mobile browsers and API clients cannot. Install the full chain provided by your Certificate Authority.
Can I check SSL on any port?
Yes! Enter the port number next to the domain. Common ports: 443 (HTTPS), 8443 (alternative HTTPS), 993 (IMAP SSL), 465 (SMTP SSL), 636 (LDAPS), 995 (POP3 SSL). This is especially useful for checking mail server and API certificates.
What key size should my certificate have?
For RSA keys, 2048-bit is the minimum acceptable in 2026, and 4096-bit is recommended. For ECDSA (elliptic curve), 256-bit provides equivalent security to RSA 3072-bit with better performance.
My certificate is valid but the browser shows a warning — why?
Usually mixed content — your HTTPS page loads some resources (images, scripts, CSS) over HTTP. Check your page source for any http:// URLs and change them to https://. Use our Meta Tags Analyzer to scan for issues.
Is a free Let's Encrypt certificate secure enough?
Yes. Free certificates use the same encryption algorithms and strength as paid certificates. The padlock in the browser is identical. Google treats them equally for SEO. The difference is only in validation level (DV vs OV/EV), not security.
What is the difference between SSL and TLS?
TLS is the modern successor to SSL. All current "SSL certificates" actually use the TLS protocol (version 1.2 or 1.3). The name "SSL" persists by convention but is technically outdated. Learn more in our complete SSL guide.