craine

This is version 2 of a project I started three years ago (hence the test domain). I'm rebuilding the website/home page now, so not many of the links there work, but the web app (click the login link) is about 85% functional. There's still things that need to be built out in the app, like the statistics module, but I wanted to get it out there for feedback up to this point.

Hi Jens_. I'm the one who wrote the TLS certificate dashboard that the other posters are referring to here. While I don't mind people forking the dashboard I made and modifying it for their own purposes (that's why I put it up on GH after all), I do mind when proper credit isn't given for the work that I've done. I'm not interested in starting a war of words on the Internet, so all I'll say at this point is that I appreciate that you've updated your readme with a link to my project and added the license to your repo. Have a great day.

Fair point that it's the CA's job, but typically their solution is "We'll send you emails at certain thresholds". That kind of thing tends to get lost in the noise of daily work, especially at places with poorly defined processes.

I've also worked places that used multiple CAs, and that makes it more difficult to manage. This at least can pull the info in based on what the server is actually using, and puts everything on one screen, regardless of the CA it came from.

I created a dashboard to view some basic info about the TLS certificates that I manage for various websites, including days to expiration, Issuer, Issuer Common Name, and certificate common name. It's also useful for enterprise infrastructure if you have to manage lots of web server certificates as part of a security or ops team.

I use a node module to scrape the peer certificate info, and then dump it into a file that a web page picks up. It's not real-time, out of concern for too many people hitting or reloading the page and kicking off too many connection attempts at once.

An example is here: https://craine.gitlab.io/tls-dashboard/