Why certificates still expire
Most certificates renew themselves today, for example with Let's Encrypt. That works until it does not: a changed server, a DNS record that moved, a renewal job that stopped after an update. Nobody notices, because the old certificate keeps working for weeks. Then it expires, often at night or on a weekend.
What exactly is checked
Each check of a site with an address that starts with https:// opens a new connection and lets Go's TLS library verify the certificate, the same rules browsers follow:
- The certificate is signed by an authority that operating systems trust.
- It is valid for the name in the address, for example www.example.com.
- Today lies between the first and the last day of its validity.
If the site redirects, for example from example.com to www.example.com, the certificate of every step is checked, and the one that expires first counts for the warning.
When you get an email
- Expires soon: once per certificate, when it has 14 days or less left.
- Down: when the certificate is not valid in 2 checks in a row, like any other outage.
- Up again: when a check finds a valid certificate after an outage.
What it does not check
Only the certificate the site shows. It does not check the strength of the encryption, old protocol versions or whether the certificate was revoked, and it does not grade your setup. For that, there are dedicated tests such as the one of SSL Labs.