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™.
Unfortunately the string of phishing attacks using domain-confusionand legitimate-looking emails continues. This is the same…
SummaryI recently responded to an attack campaign where malicious actors injected code into GitHub Actions…
Internet security is leveling up with MPIC. While your organization likely won’t need to do…
Sept. 10: Get actionable insights from 20+ global experts as they discuss PQC readiness assessments,…
SummaryPyPI now checks for expired domains to prevent domain resurrection attacks,a type of supply-chain attack…
PyPI now serves project status markers in its standardindex APIs. This allows downstream consumers (like…
This website uses cookies.