Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
Today we’ve released a huge update, completely changing how our SSL monitoring works and enabling you to keep a much closer eye on all aspects of your certificates. We’ve introduced a new set of features for SSL, that enable much more powerful monitoring, these are summarized below:
Expiration Monitoring – We’ve fully revamped our expiration monitoring increasing the options in terms of how often the details are checked (anywhere from 5 minutes to 7 days dependent on plan level), also allowing customization of when the alerts for expiry come through – meaning that self-signed certs are now much less troublesome to keep an eye on.
Certificate Validity
As well as expiry we now watch out for validity issues, we will run a complete check of the certificate chain, verify that the certificate is on the correct domain, and we’ll also ensure that the certificate has not been revoked by the relevant authority. You can get alerted by our system right away if any of these factors are not as they should be.
Certificate Score
We now take a range of factors into account to provide you with a certificate score. Firstly we look at the “Cipher Strength”. Cipher strength has a proprietary scoring algorithm that takes the following variables into consideration:
* Key Exchange
* Bulk Cipher & Strength
* Used Keyed-hash message authentication (HMAC)
From the Cipher Strength and other factors, we give your certificate a final score, the full weightings for this score are shown below:
* Cipher Strength (50%)
* Perfect Forward Secrecy (25%)
* Certificate Errors (10%)
* Certificate Validity (5%)
* Certificate Presence (5%)
* Extended Validation presence (5%)
We will mark your certificate with a score out of 100%, you can see all scores within the SSL section in the left menu. All of the info can also be viewed on the details page, where we provide further data and comparison graphs.
The new functionality is available across all paid plans, and all functions are now managed within the SSL section, meaning that there’s increased separation from the uptime tests and the ability to manage these separately.
StatusCake Team
Share this
More from StatusCake
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026
Alerting Is a Socio-Technical System
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
James Barnes
February 25, 2026
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026