Let’s Encrypt (LE) announced earlier this year that it would discontinue SSL/TLS expiration notification emails on Wednesday, June 4. That’s just two days from now, so now’s the time to be sure that you have the systems in place to help keep your certificate management on track once it’s “go time.”
Even if you’re using automation to keep your certificate renewed and updated (that’s good!), you’re not 100% home free. The unfortunate reality is that certificate renewal cron jobs/automated tasks can and do fail (online forums are rife with examples), leaving sites down due to an expired SSL/TLS certificate. Fortunately, there are some simple solutions.
So, what does all of this mean for Let’s Encrypt users, and what options are there for monitoring your SSL/TLS security?
Let’s hash it out.
The post Monitoring Should Take Center Stage as Let’s Encrypt Abandons SSL Expiration Notifications appeared first on Hashed Out by The SSL Store™.
Starting March 1, the lifespans of software-signing digital certificates will be reduced from 39 months…
Providing insight into our product roadmap and, subsequently, the projects being worked on in our…
Hi everyone,We are currently refreshing our marketing pages to better explain what Open Collective is…
Some of our team, and members of the OFi and Open Collective family, will be…
Hello there! I am Maria, the inaugural PyPI Support Specialist. I go by "Thespi-Brain" on…
We’ve kickstarted our sidebar reorganization campaign. We will gradually introduce improvements to the sidebar over…
This website uses cookies.