SSL Certificate Checker
Check a site's TLS certificate: expiry, issuer, chain, hostname match, protocol and HSTS.
- Free
- No sign-up
What is an SSL certificate checker?
An SSL certificate checker connects to a domain over HTTPS and inspects the certificate and connection the server presents. Strictly speaking, modern sites use TLS, the successor to SSL, but the old name stuck. Enter a domain and the tool opens a connection on port 443, completes the TLS handshake and reports everything a browser evaluates before showing the padlock, plus a few things browsers quietly forgive.
The report covers the certificate subject, the full list of Subject Alternative Names (SANs), the issuer and certificate authority, the validity dates and the days until expiry. Expiry is flagged as a warning under 30 days and a failure under 7 days or once expired. You also see the key type and size, the signature algorithm, the TLS protocol version and cipher suite negotiated, whether the hostname matches the certificate, whether the certificate is self-signed, and whether the site sends an HSTS header.
The tool also examines the certificate chain: the intermediate certificates the server sends alongside its own. It checks whether the full chain is served, which is one of the most common hidden TLS problems. Desktop browsers can often fill in a missing intermediate from cache or by fetching it, so the site looks fine to you, while API clients, older Android devices and command-line tools fail with an untrusted certificate error.
How to check an SSL certificate
- 1
Enter the domain
Type the hostname, such as example.com or www.example.com. Check each hostname you serve, because they can be covered by different certificates.
- 2
Run the check
Our server connects on port 443, completes the handshake and reads the certificate, chain and negotiated connection details.
- 3
Check expiry and hostname match
Confirm the days remaining and that the hostname appears in the SAN list. A mismatch causes a browser warning even if the certificate is otherwise valid.
- 4
Review the chain
Make sure the chain is complete. If intermediates are missing, configure your server to send the full chain file your CA provides.
- 5
Look at protocol and HSTS
Confirm TLS 1.2 or 1.3 was negotiated and decide whether an HSTS header is appropriate for the site.
When to use an SSL checker
Catching renewals that silently failed
Automated renewals break when DNS, firewall rules or CAA records change. A quick check shows the real expiry date on the live server, not the one in your dashboard.
Fixing untrusted certificate errors
When some users or tools report errors but your browser does not, an incomplete chain is the usual cause.
Verifying a new installation
After installing a certificate or moving hosts, confirm the server presents the new certificate with every hostname listed.
Auditing a domain portfolio
Agencies and in-house teams can check each client or brand domain for upcoming expiries before they cause an outage.
Checking a CDN or proxy
Behind Cloudflare or another CDN, the checker shows the edge certificate visitors actually receive, which helps separate edge issues from origin issues.
Certificate lifetimes, chains and keys
Certificate lifetimes are shrinking. Under a CA/Browser Forum ballot adopted in 2025, the maximum validity for publicly trusted TLS certificates dropped from 398 days to 200 days in March 2026, and is scheduled to fall to 100 days in March 2027 and 47 days in March 2029. Let's Encrypt certificates are valid for 90 days. Shorter lifetimes make automated renewal essential, and make expiry checks more useful.
A typical chain has three parts: your leaf certificate, one or more intermediates, and a root that lives in the browser or operating system trust store. Servers should send the leaf and intermediates but not the root. Sending the wrong intermediate, or only the leaf, is enough to break validation for clients that do not repair chains on their own.
For keys, ECDSA P-256 gives strong security with small, fast signatures, and RSA 2048-bit remains the widely compatible minimum. Signatures should use SHA-256 or stronger; SHA-1 certificates are no longer trusted. TLS 1.0 and 1.1 are deprecated and disabled in current browsers, so a server should offer TLS 1.2 and ideally TLS 1.3.
Frequently asked questions
Is the SSL checker free?
Yes, the SSL certificate checker is free with no account needed. Check any public domain as often as you like within the per-visitor rate limit, and see expiry, SANs, issuer, chain completeness, key details, protocol, cipher, hostname match and HSTS in one report. It is suitable for quick spot checks and routine portfolio audits.
What does the tool connect to, and is anything stored?
The tool connects only to the domain you enter, on port 443, to read the certificate and handshake details, plus one HTTPS request to check for an HSTS header. Results are shown to you and not stored. Private and internal addresses are blocked, and checks are rate-limited per visitor.
My browser shows a padlock, so why does the checker report a chain problem?
Your browser is likely repairing the chain for you. Browsers cache intermediate certificates from other sites and some fetch missing ones automatically. Many clients, including API libraries, payment webhooks, crawlers and older mobile devices, do not. Serve the complete chain from your server so every client validates the certificate.
How early should I renew a certificate?
Renew well before expiry, which is why the checker warns at 30 days. Automated clients for Let's Encrypt typically renew when about one third of the lifetime remains, roughly 30 days for a 90-day certificate. If a certificate is under 7 days from expiry, treat it as urgent, because renewal has probably failed.
What does a hostname mismatch mean?
A hostname mismatch means the domain you entered is not listed in the certificate's Subject Alternative Names. Browsers ignore the subject Common Name for this check and use only SANs. Add the hostname to the certificate, use a wildcard that covers it, or redirect that hostname to one the certificate does cover.
Is a free certificate as secure as a paid one?
Yes, for encryption a free domain-validated certificate is as strong as a paid one. Both use the same algorithms and are trusted by the same browsers. Paid options can add organization validation, warranties, support or longer-term management features, but they do not make the connection itself more secure.
Related tools
More Domain & Server tools →Bulk Redirect Chain Checker
Trace every hop for up to 100 URLs — chains, loops, 302s and broken destinations.
Domain & Server
HTTP Headers Checker
See every response header, hop by hop — with a security grade and caching explained.
Domain & Server
DNS Lookup
Query A, AAAA, MX, NS, TXT, SOA and CAA records on Cloudflare and Google DNS — plus SPF and DMARC checks.
Domain & Server
What Is My IP Address
Your public IP, country, browser and connection details — instantly, and never logged.
Domain & Server