How We Handle SSL So You Never Think About It

An expired SSL certificate is one of the most common self-inflicted outages on the web: the site was fine, nobody touched it, and one morning every visitor gets a scary browser warning. It’s entirely preventable, and handling it should be the host’s job, not yours.

Why certificates lapse

Certificates expire on purpose, it’s part of how the system stays trustworthy. Modern certificates are short-lived, often 90 days, which means renewal has to be automatic. When it’s left to a manual reminder or a forgotten cron job, it eventually gets missed, and the miss is public.

What good looks like

Good SSL handling is invisible. The certificate is issued automatically when a domain is connected, renews well ahead of expiry without anyone acting, and surfaces its status and renewal countdown so you can confirm it at a glance. You should never have to think about it, and you should be able to check that you don’t have to.

How we do it

On SrvBot, SSL is issued automatically for connected domains and renews on its own before expiry. The dashboard shows the certificate’s status and when it renews next, so “handled for you” is something you can verify, not just take on faith.

The bottom line

A lapsed certificate is a preventable outage that damages trust the moment it happens. Automatic issuance and renewal turn it into a non-event. If your host still expects you to remember, that’s worth changing, see how ours works at /help/ssl-not-renewed.