Tls certificate expiring
Your TLS certificate has expired. Every visitor now sees a full-page browser security warning and most will not click through it, so the site is effectively offline — and API clients and webhooks will be refusing connections outright.
Why it matters
Your TLS certificate has expired. Every visitor now sees a full-page browser security warning and most will not click through it, so the site is effectively offline — and API clients and webhooks will be refusing connections outright.
How ShipReady detects it
TLS configuration checks. The only check that inspects the transport itself rather than an HTTP response, so it opens its own TLS connections instead of using the shared PageContext. Both probes are passive: a TLS handshake exchanges no application data, sends no request, and changes nothing on the server. Certificate expiry is the highest-value item here — an expired certificate takes a site completely offline for every visitor, and it is entirely preventable with notice.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.0.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Your TLS certificate is at or past the end of its validity. Renew it now, then fix the renewal so this cannot recur: use an automated issuer (Let's Encrypt via certbot/acme.sh, or your host's managed certificates, which most platforms renew automatically) and add an expiry alert so you find out weeks ahead rather than from users. If renewal automation already exists, check why it stopped — a failed hook or a changed DNS/HTTP challenge path is the usual cause.
Frequently asked questions
- What does "Tls certificate expiring" mean?
- Your TLS certificate has expired. Every visitor now sees a full-page browser security warning and most will not click through it, so the site is effectively offline — and API clients and webhooks will be refusing connections outright.
- How serious is it?
- ShipReady rates this high. Fix before launch. A real weakness that an attacker can act on.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site