This is a problem because the certificate handling is not in the hands of process managers, but in the hands of the sysadmins, who do not generally work on a ri

This is a problem because the certificate handling is not in the hands of process managers, but in the hands of the sysadmins, who do not generally work on a rigorous business-cycle type of schedule, and who don't already have tools in place to keep track of such things, and have a hard time justifying creating a tool that would, assuming they just have one or two certs to manage, be used only once every two years (and thus would probably take four years to troubleshoot, by which point something about the assumptions would have changed, meaning the reminders/warnings would probably fail and the cert will get overlooked). It does make me wonder, though... why don't web servers have options to warn their admins (via logging or email or what-have-you) that the certs they are using are near expiration? Or do they? Alternatively, some good samaritan could set up a service to scan the known SSL web for near-expired certs and email webmaster@ or other scraped addresses of the issue.