Loading tool...
Search for a command to run...
Check SSL/TLS certificate validity and security
Enter a domain and click Check SSL
Files never leave your device
Certificate checks run through our server — no data is stored
SSL certificate inspection requires a server-side TLS connection to the target domain. Browsers cannot access raw certificate data.
An SSL/TLS certificate is a digital credential that authenticates a website's identity and enables encrypted communication between a browser and a web server. When you visit a site with https:// in the address bar, an SSL certificate is working behind the scenes — encrypting your data so it cannot be intercepted by third parties, and verifying that you are actually communicating with the intended server rather than an impersonator.
SSL certificates are issued by Certificate Authorities (CAs) — trusted organizations that verify domain ownership before issuing credentials. Major CAs include Let's Encrypt (which now issues over 200 million certificates), DigiCert, Sectigo, and GlobalSign. Each certificate has a validity period, typically 90 days for Let's Encrypt or one to two years for commercial CAs. When a certificate expires, browsers display prominent security warnings and block access, driving users away and harming SEO rankings.
Regular SSL certificate checks are essential for site reliability engineering. A certificate expiry that slips through monitoring can take a site offline more effectively than any DDoS attack — and with far less warning. Using the JumpTools SSL Certificate Checker, you can verify any domain's certificate status, chain completeness, and upcoming expiration date in seconds.
SSL certificates do not stand alone. They form a chain of trust that browsers use to validate authenticity. A complete certificate chain consists of three levels:
Leaf certificate: This is the certificate issued specifically for your domain (e.g., example.com). It contains your domain name, the issuing CA's signature, and the validity period. Browsers check this certificate first.
Intermediate certificates: Root CAs rarely sign leaf certificates directly for security reasons. Instead, they sign intermediate certificates, which in turn sign leaf certificates. Most certificate chains have one or two intermediates. An incomplete chain — where intermediate certificates are not served by the server — causes SSL errors in some browsers and client libraries even if the leaf certificate is valid.
Root certificate: The root CA's self-signed certificate is embedded in the operating system and browser trust store. When browsers can build a complete chain from your leaf certificate up to a trusted root, they display the padlock icon. If any link is missing, broken, or from an untrusted CA, a security warning appears.
The SSL checker displays each certificate in the chain, so you can immediately identify incomplete chain configurations — one of the most common SSL deployment errors that escapes notice until users report browser warnings.
Not all HTTPS connections are equally secure. The TLS protocol has gone through several versions, and older versions have known vulnerabilities:
SSL 3.0 and TLS 1.0/1.1 are deprecated and considered insecure. SSL 3.0 is vulnerable to the POODLE attack; TLS 1.0 is vulnerable to BEAST. The PCI DSS standard required all websites handling payment card data to disable TLS 1.0 by June 2018. Most modern browsers have removed support for TLS 1.0 and 1.1 entirely as of 2020.
TLS 1.2 is the current minimum acceptable standard, supported by all modern browsers and clients. It supports strong cipher suites including AES-GCM and ChaCha20-Poly1305, and is the baseline requirement for HIPAA, PCI DSS, and SOC 2 compliance.
TLS 1.3 is the modern standard, offering improved performance (one fewer round trip for handshakes) and removed support for legacy cipher suites that created downgrade attack opportunities. If your server supports TLS 1.3, the checker will report it here.
The cipher suite field shows the specific algorithm negotiated for the connection, including the key exchange method, bulk encryption algorithm, and message authentication code. Weak cipher suites — particularly those using RC4, DES, or 3DES — indicate a server configuration that needs updating.
Check SSL/TLS certificate validity and expiration
View complete certificate chain hierarchy
Analyze TLS protocol version and cipher suite
Detect security vulnerabilities automatically
Enter domain Type the domain name (e.g., google.com)
Set port Optionally specify a port if not using default 443
Check SSL Click to analyze the certificate
Review results Check certificate details, chain, and warnings
Check any domain's SSL/TLS certificate validity, expiration date, and security configuration. View certificate chain, cipher suites, and detect vulnerabilities like weak protocols.