From d185e317df67a051cfaf9a94c4a209e44cc02ccc Mon Sep 17 00:00:00 2001 From: shankar0123 Date: Wed, 25 Mar 2026 03:53:56 -0400 Subject: [PATCH] docs: update README subtitle Co-Authored-By: Claude Opus 4.6 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a64d2eb..7ca673c 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # certctl — Self-Hosted Certificate Lifecycle Platform -Built by a solo developer. 91 API endpoints. 21 database tables. 900+ tests. Full GUI. Ships with Docker Compose. +91 API endpoints. 21 database tables. 900+ tests. Full GUI. Ships with Docker Compose. TLS certificate lifespans are shrinking fast. The CA/Browser Forum passed [Ballot SC-081v3](https://cabforum.org/2025/04/11/ballot-sc081v3-introduce-schedule-of-reducing-validity-and-data-reuse-periods/) unanimously in April 2025, setting a phased reduction: **200 days** by March 2026, **100 days** by March 2027, and **47 days** by March 2029. Organizations managing dozens or hundreds of certificates can no longer rely on spreadsheets, calendar reminders, or manual renewal workflows. The math doesn't work — at 47-day lifespans, a team managing 100 certificates is processing 7+ renewals per week, every week, forever.