Free tool

SSL checker

An expired or broken certificate puts a full-page warning in front of every visitor. Enter your address: we connect on port 443, read the certificate your server sends, and tell you whether browsers trust it and how long it has left.

No sign-up and no email. Results are not published or tied to you.

Your result shows up here

Whether browsers trust your certificate and why, the names on it, who issued it, when it expires, and its length against the CA/Browser Forum limit.

How it works

Three steps, about ten seconds

01

Enter your address

Any public site works. We connect to it on port 443, the HTTPS port, using the name you typed.

02

We read the certificate

We complete a TLS handshake and read the certificate your server sends. We never ask for a page.

03

We check it as a browser does

Trust, the names on it, the dates, and its length against the CA/Browser Forum limit for its issue date.

Reference

How long a certificate may last

The CA/Browser Forum, where certificate authorities and browser makers set the rules for public certificates, approved a schedule in April 2025 that shortens the longest a certificate may last. The limit depends on the day the certificate was issued, and its length counts every day from its start date to its end date.

The longest a public TLS certificate may last, by the date it was issued
Issued on or afterIssued beforeLongest allowed
Any earlier date15 Mar 2026398 days
15 Mar 202615 Mar 2027200 days
15 Mar 202715 Mar 2029100 days
15 Mar 2029No end date47 days

Source: CA/Browser Forum Ballot SC-081v3, now section 6.3.2 of the Baseline Requirements.

Fix it on your platform

Renew or fix a certificate on your platform

Most problems this finds are an expired certificate, a renewal that stopped running, or a server that sends its certificate without the intermediate. Each fix is in your server's config or your host's settings.

Certbot (Let's Encrypt)

Certbot sets up a timer that renews certificates for you. To see where yours stand and test the renewal:

# List each certificate and its expiry date
sudo certbot certificates

# Test renewal without changing anything
sudo certbot renew --dry-run

If the dry run fails, fix the error it prints, then run sudo certbot renew.

Nginx

Point ssl_certificate at the full chain: your certificate first, then the intermediates. With Certbot that file is fullchain.pem.

ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

Nginx reads the file when it starts or reloads, so reload it after a renewal: sudo nginx -s reload.

Apache

Since Apache 2.4.8, SSLCertificateFile can hold your certificate and its intermediates in one file. Point it at the full chain:

SSLCertificateFile    /etc/letsencrypt/live/example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem

Cloudflare

Behind Cloudflare's proxy, this checks the certificate Cloudflare serves, which Cloudflare renews. Your own server's certificate sits behind it: with the SSL/TLS mode set to Full (strict), an expired or invalid one there shows visitors error 526.

Vercel

Vercel issues and renews certificates for the domains it serves. If one stops renewing, check that the domain's DNS still points at Vercel and that no CAA record blocks Let's Encrypt.

Questions, answered

SSL certificates, in plain terms

01

How do I check when my SSL certificate expires?

  • Enter your address above. The result shows the expiry date, the days left and the date to renew by.
  • From a terminal: openssl s_client -connect example.com:443 -servername example.com < /dev/null | openssl x509 -noout -enddate
02

Why does my site say the certificate is not trusted?

  • The usual causes are an expired certificate, a server that does not send its intermediate certificate, a self-signed certificate, or a certificate that does not name the address.
  • The result names the cause, with the error code behind it.
03

What is an intermediate certificate, and why does it matter?

  • Certificate authorities sign your certificate with an intermediate certificate, not with the root that browsers trust. Your server has to send that intermediate along with your certificate.
  • Some browsers find a missing intermediate on their own, so the site can look fine in a browser and still fail in curl, in apps and in API clients. Send the full chain and it works everywhere.
04

How long can an SSL certificate last?

  • Since 15 March 2026, a public certificate may last at most 200 days. That falls to 100 days on 15 March 2027 and to 47 days on 15 March 2029.
  • The CA/Browser Forum, where certificate authorities and browser makers agree the rules, set this schedule in April 2025. Certificates issued before 15 March 2026 could last up to 398 days.
05

How often should I renew my certificate?

  • Leave yourself a third of the certificate's life to renew, up to 30 days. Let's Encrypt suggests renewing its 90-day certificates every 60 days.
  • With lifetimes this short, renew automatically. Certbot and most hosts do it for you, so what to check is that renewal still runs.
  • Of 4,101 sites LaunchScaler scanned in the 60 days to 14 Nov 2026, 3,948 (96%) had 90 days or fewer left on their certificate, and 63 (1.5%) had under 30 days.
06

Why does this show a different certificate from the one on my server?

  • A CDN or proxy in front of your site, such as Cloudflare, serves its own certificate. This shows what visitors get, which is that one.
  • A server that hosts several sites picks the certificate by the name in the request. We send the name you typed, as a browser does.
07

What does this check not cover?

  • It does not check revocation, the full list of ciphers your server allows, or HSTS.
  • It reads the certificate and the TLS version agreed in one handshake, as a current browser would.
08

Is it free, and do you keep my results?

  • It is free and needs no account.
  • A result stays in memory for a few minutes so a repeat check does not hit your site again, then it is gone. Nothing is saved to a database or published.

One address, 156 checks, each with its fix.

No account, just the address.