SSL Certificate Checker
Find out whether a domain's certificate has expired, whether it covers the name you typed, and whether anything is missing from the chain - and what to do if something is wrong.
What the Result Tells You
Green means nothing needs doing today. Amber means something will bite you soon. Red means visitors are already seeing a warning. Three things decide which one you get.
In date
How long you have left. Under 30 days turns amber - renew now and nobody ever notices. Already past it, and you get the date it lapsed and how long ago, which is usually enough to match against whatever changed that day.
Covers this domain
*.badssl.com is shown standing in for incomplete-chain.badssl.comrather than leaving you to work it out. When it is not covered, visitors get Chrome's NET::ERR_CERT_COMMON_NAME_INVALID or its equivalent, and the fix is a reissue with the missing hostname on it.Chain served
Whether the server is handing over everything a visitor needs, not just its own certificate. You will see something like "4 certificates, each signed by the next, up to ISRG Root X1" when it is complete. When it is not, that is the one failure your own browser will hide from you, because it has the missing piece cached and your customers do not.
Two things are worth knowing this cannot tell you: whether the certificate has been revoked, and whether one particular laptop or phone trusts the root behind it. Neither is written in the certificate, so no checker can read them off. There is a section further down on getting at both.
Common SSL Certificate Problems and How to Fix Them
The certificate has expired
Every visitor gets a full-page browser error until a new certificate is live. Renew with your CA, install the new certificate where TLS terminates, reload the service, then check again here. If renewal is automated, look at the renewal job's logs: a common cause is a certificate that renewed but was never deployed or picked up by a reload.
The certificate doesn't cover the name
example.com but not www.example.com, or the reverse. A wildcard such as *.example.com covers shop.example.com but not example.com itself, and not a.shop.example.com. Reissue the certificate with every hostname you serve in the SANs. If the right certificate exists, check that your server or CDN presents it for this hostname.The site works for you but fails for everyone else
fullchain.pem from Certbot, the ssl_certificate file in nginx, or SSLCertificateFile in Apache 2.4.8 and later. That file should hold your certificate followed by the intermediates. The root does not need to be included.An intermediate has expired
The server is still sending an old intermediate bundle. Download the current intermediates from your CA and replace the bundle.
It expires within 30 days
Nothing is broken yet. Renew now so the replacement is live with time to spare.
How to Check an SSL Certificate
- Enter the domain or subdomain, such as
example.comorshop.example.com. - Click SSL Lookup.
- Read the verdict line first. Green means the certificate is in date, covers the name and arrives with a complete chain. Amber or red points to the check that needs attention.
- Scroll down for the full SSL certificate lookup: the server certificate first, then every certificate in the chain.
What each field means
- Host: the name you checked.
- Issued to: the certificate's subject, usually the main domain name.
- Issued by: the Certificate Authority (CA) that signed the certificate.
- Valid From / Valid To: the dates the certificate is good for.
- Subject Alternative Names (SANs): every name the certificate covers. Browsers match the address you typed against this list.
- Certificate Chain Info: each certificate the server sent, with its issuer, signature algorithm, total validity, days remaining and serial number.
If the domain doesn't respond, the result says why: the domain may not exist, may serve plain HTTP only, or may be refusing outside connections.
How to Tell if an SSL Certificate Is Valid
A certificate is valid for a site when four things are true:
- It is in date. Today falls between Valid From and Valid To.
- It names the site. The hostname is in the SANs, directly or through a wildcard.
- It chains to a trusted root. The server sends its intermediates, and the root at the top is in the visitor's trust store.
- It has not been revoked by the CA that issued it.
This SSL checker answers the first two directly, plus the chain-building half of the third. For the trust-store half, open the site in the browser or app you care about, since each uses its own store. For revocation, use a full server test that queries the CA's revocation data, or the OpenSSL commands further down this page.
A padlock in your own browser is not proof. Browsers cache intermediates from other sites, and some fetch missing ones on demand, so a broken chain can look fine on your laptop and still fail in curl, an API client or a mobile app.
Which Names a Certificate Covers
The Subject Alternative Names (SANs) are the list of hostnames a certificate is allowed to secure. Browsers match the address in the URL bar against that list, so a name that is missing from it fails, however good the rest of the certificate is.
- Single-name certificates cover one hostname, often with
wwwadded as a second SAN. - Wildcard certificates (
*.example.com) cover one level of subdomain. They do not cover the bare domain unless it is listed separately, and they do not cover deeper levels such asa.b.example.com. - Multi-domain certificates list several unrelated names in one certificate, common on CDNs and SaaS platforms.
The SAN list in your results shows exactly which names this certificate covers.
What a Complete Certificate Chain Looks Like
A chain has three layers:
- Site (leaf) certificate: issued for your domain.
- Intermediate certificate(s): issued by the CA's root, used to sign your certificate. Most public CAs use one or two.
- Root certificate: already installed on devices. Your server does not need to send it.
To check the SSL certificate chain in your results, look down the Certificate Chain Info list. Each certificate's "Issued by" should match the "Issued to" of the next one. If the list stops at your own certificate, the intermediates are not being sent, and the Chain served check will flag it.
Check an SSL Certificate from the Command Line
For hostnames this SSL cert checker can't reach, such as internal servers, OpenSSL gives the same certificate details.
Show the expiry dates, subject and issuer:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -dates -subject -issuerList the SANs (OpenSSL 1.1.1 or later):
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -ext subjectAltNamePrint every certificate the server sends:
echo | openssl s_client -connect example.com:443 -servername example.com -showcertsVerify return code: 0 (ok) means the chain verified against the trust store on the machine running the command. To check certificates on a schedule rather than by hand, use the SSL Lookup API.How to Renew an SSL Certificate
- Check the expiry date here and start before the 30-day warning.
- Get a new certificate from your CA. Some renewals reuse your earlier domain validation; others ask you to prove control of the domain again.
- Install it where TLS terminates: your server, load balancer or CDN. Include the intermediates.
- Reload or restart the service. Many servers keep presenting the old certificate until they do.
- Check again here to confirm the new Valid To date is live and the chain has no gap.
Renewal is getting more frequent. Public certificates issued since 15 March 2026 can last at most 200 days. That limit drops to 100 days on 15 March 2027 and 47 days on 15 March 2029, so automate issuance with ACME wherever your CA supports it.