SSL Certificate Checker
Enter a domain to see when its SSL certificate expires, who issued it, whether the name matches and whether the chain is trusted. The check runs on this site's server, because browsers cannot read certificate details, and nothing is stored. Renew with at least two weeks to spare; under 30 days left often means auto-renewal has failed.
Updated
How to use the SSL Certificate Checker
- 1Type the domain, such as example.com, or paste a full address.
- 2Leave the port at 443 for a website, or choose the port of a mail or other TLS service.
- 3Press Check certificate.
- 4Read the expiry date and any chain or name problems, and add a renewal reminder to your calendar if you like.
How it works
Browsers do not let web pages see certificate details, so this check runs on this site's server. It opens a TLS connection to the domain as a browser would — sending the domain name so the server presents the right certificate — reads the certificate and the chain the server sends, and closes the connection. Nothing about the check is stored.
Three things must all be right for a certificate to work. It must be within its validity dates; it must name the domain being visited, either exactly or through a wildcard such as *.example.com; and it must chain up to a root certificate authority that devices trust. The tool checks all three, verifying the chain against the root certificates bundled with Node.js, which follow Mozilla's trusted list.
The most common problem after expiry is a missing intermediate certificate. Desktop browsers can often fetch the missing piece themselves, so the site looks fine in Chrome while phone apps, API clients, payment providers and older devices refuse to connect. A chain error is worth fixing even when your browser shows a padlock.
Public certificate lifetimes are being shortened in stages under CA/Browser Forum rules — to a maximum of 200 days from March 2026, falling to 47 days by 2029 — so automated renewal and regular expiry checks matter more each year. Before connecting, every address the domain points to is checked to be on the public internet, so the tool cannot be used to probe private networks.
Tips and common mistakes
- Check both the bare domain and www, and any subdomains that serve traffic; they can use different certificates.
- Set a reminder well before the expiry date even if renewal is automated, so a silent failure is caught in time.
- Fix chain errors even when your own browser shows a padlock; phones, API clients and payment providers are stricter.
- Automate renewal; certificate lifetimes are getting shorter every year.
Frequently asked questions
When should I renew my certificate?
Why does my browser show a padlock when this tool reports a chain problem?
Can it check mail servers?
Is the domain I check stored?
What is an intermediate certificate?
Do the bare domain and www need checking separately?
How long do certificates last now?
Guides
- How to verify a file checksum (SHA-256) — and what it proves
- How to check when an SSL certificate expires — and why it matters
- How to fix an incomplete SSL certificate chain
- SSL certificates are getting shorter lifetimes: what changes for you
- Why a site shows a certificate name error on www or without it