SSL/TLS Checker
Check a domain’s certificate status, issuer, validity window, and more. Certificate status is classified from real data, not guessed — see "How It Works" for exactly where each field comes from.
Input
Results
Overview
The SSL/TLS Checker tells you whether a domain currently completes a trusted HTTPS connection and, using public Certificate Transparency records, shows details of the certificate issued for it: issuer, subject, alternative names, serial number, validity dates, and days remaining. It then classifies the result as Valid, Expiring Soon, Expired, or Invalid / Error.
Use it to catch certificates about to expire, to check that a certificate covers the hostname you expect, or as the first step in diagnosing a browser certificate warning.
How It Works
Two independent checks are combined, and the page is explicit about which fact came from which. First, this site's server opens a real HTTPS connection to the domain. The server's HTTPS client rejects a connection when the certificate chain is untrusted, expired, or not valid for the hostname, much as a browser does, so a successful connection is good evidence that the certificate is acceptable right now. Second, the tool searches Certificate Transparency (CT) logs (via crt.sh) for certificates issued for the name, and picks the most recent one that covers it. That provides the issuer, subject, SAN list, serial number and dates.
The status follows the evidence: a failed connection is Invalid / Error (or Expired if CT records show the newest certificate has lapsed); a successful connection is Valid, or Expiring Soon if 30 days or fewer remain. HTTP status codes are never used to judge the certificate.
Some details cannot be obtained in this environment and are shown as Not available rather than guessed: the negotiated TLS version and cipher suite, certificate version, signature algorithm, public key size, and a complete chain validated to a root. The chain shown is the leaf and its issuer only.
How to Use the SSL/TLS Checker
- Enter a domain name such as
example.com(withouthttps://). - Press Calculate. The check takes a few seconds because it contacts the site and a CT log service.
- Read the status banner first, then HTTPS Reachable, Hostname Match, and Days Remaining.
- Review the certificate fields and SAN list to confirm which names the certificate covers.
Worked Example
Checking a certificate before it expires
You want to know when the certificate for www.example.org needs renewing. The values below are an illustrative sample.
Input
Domain: www.example.org
Illustrative output
Certificate Status: EXPIRING SOON
HTTPS Reachable: Yes
Hostname Match: Yes
Days Remaining: 12 days
Subject: www.example.org
Issuer: Let's Encrypt
Valid From: 2026-08-01
Valid Until: 2026-10-30
SANs: www.example.org, example.org
TLS Version: Not available
Cipher Suite: Not available
This output is an illustrative sample to show the layout and meaning of each field. Real results depend on the target and on when you run the check.
The connection succeeded, so the certificate is valid right now, but only 12 days remain, which crosses the 30-day threshold and produces Expiring Soon. Automated certificates (such as Let's Encrypt's 90-day certificates) are normally renewed well before this point, so a low number usually means the renewal job has failed.
The SAN list shows the certificate covers both www.example.org and example.org. If you visit a name that is not in this list the browser shows a name-mismatch error. TLS version and cipher are "Not available" because this environment cannot see them.
Interpreting Results
- VALID
- The live connection succeeded and more than 30 days remain (or, if no CT data was found, the connection succeeded but dates are not available).
- EXPIRING SOON
- Connection works; 30 days or fewer remain. Renew now.
- EXPIRED
- The newest known certificate has passed its end date and the connection failed.
- INVALID / ERROR
- The secure connection could not be established. The message gives the most specific reason the available evidence supports, such as a name not listed in the newest certificate.
- Hostname Match
- Whether the requested name appears in the certificate's SAN list (wildcard entries such as
*.example.orgare honored). - Issuer / chain
- The certificate authority that signed the certificate. The chain shown is partial.
Troubleshooting
- Status is Invalid but the site works in my browser.
- Your browser may have cached a working path (for example it fetched a missing intermediate certificate automatically), or the site serves different certificates by region or client. Test with
openssl s_client -connect host:443 -servername hostand compare. - Hostname does not match.
- Check the SAN list. The certificate may cover only the apex or only
www, or the site is served from a default certificate because the server does not support SNI for that name. - "Certificate details unavailable" with a successful connection.
- The CT log service may be slow, or the certificate was issued very recently or by a private CA that does not log publicly. The successful connection still shows the certificate is acceptable.
- The connection timed out.
- The host did not answer on port 443 in time: check DNS, firewalls, and that the service is listening.
Limitations and Accuracy
- Certificate fields come from Certificate Transparency records, not from reading the certificate presented on the connection. They describe the newest matching certificate issued for the name, which is normally, but not always, the one being served.
- TLS version, cipher suite, signature algorithm, key size, and a fully validated chain are not available in this environment and are never guessed.
- Certificates from private or internal CAs are not in public CT logs, and internal hostnames are refused.
- crt.sh is a free public service with no uptime guarantee and can be slow or unavailable; the page reports this.
Data Handling
Uses server-side requests. The domain you enter is sent to this site's server function, which connects to that domain over HTTPS and queries a Certificate Transparency search service.
Sent to: The server for the domain you named, crt.sh (Certificate Transparency log search), and Cloudflare's DNS-over-HTTPS resolver for the safety check.
Inputs travel as URL query parameters, so avoid entering confidential internal hostnames or personal data. See the Privacy Policy for how requests are handled.
Frequently Asked Questions
Why can't it show the TLS version?
The environment this site runs on does not expose the negotiated TLS version or cipher for outgoing connections. Rather than guess, the tool says "Not available".
Is a "Valid" result a security audit?
No. It means the certificate is currently acceptable for that name. It does not assess protocol configuration, cipher strength, or the rest of the site's security.
How do I fix certificate errors?
The TLS troubleshooting guide maps each common error to its cause and fix.