47-Day readiness
A dashboard purpose-built for the CA/B Forum SC-081 shorter- lifetime roadmap. Certs are moving from ~398 days to ~100 and eventually to 47. That shift turns manual renewal processes into incident generators. The readiness score tells you how prepared your project is.
The score
Weighted average of three components over the project's active certificates, range 0 – 100:
- 50 % — Automation coverage: fraction of certs with
auto_renew: truethat do not use manual DNS validation (automatic DNS and HTTP-01 both count as automated). - 30 % — Distribution coverage: fraction of certs with at least one healthy distribution — enabled, and whose last run did not fail or get rolled back — so the renewed cert actually lands somewhere.
- 20 % — No manual DNS: fraction of certs NOT in the manual DNS path. Manual-DNS certs can't auto-renew.
Result buckets:
| Score | Level | Reading |
|---|---|---|
| 80–100 | Ready | You'll ride the shorter-lifetime transition easily. |
| 50–79 | At risk | Gaps remain — the recommended actions and the at-risk list show where. |
| 0–49 | Critical | Fix fast. Start with the automation coverage component. |
A project with no active certificates shows no data instead of a score.
The score sits beside its three parts, each with its weight and its own percentage, so you can see which one is holding it down.
Maximum certificate lifetime
The CA/Browser Forum SC-081 schedule drawn as a staircase: the maximum lifetime a certificate may have, stepping down on the date each limit takes effect, with today marked.
- until 2026-03-15: 398 days;
- from 2026-03-15: 200 days;
- from 2027-03-15: 100 days;
- from 2029-03-15: 47 days.
Under each step: how many renewals a year this project would need, how much more that is than today, and the expected load on the busiest day. A limit only shortens certificates that live longer than it, so a step at or above your certificates' current average lifetime shows today's workload with no change. A step below it shows the projection, which assumes every certificate is renewed at the full maximum and expirations are spread evenly; actual load depends on your issuance pattern. The step that applies now is highlighted.
What to do
The headline insight and the recommended actions for this project, in order.
Workload
- Automated — automated certificates out of all active ones, and how many still need a manual step.
- Average lifetime today — your active certificates' average lifetime, and the renewals a year it means.
- At 47 days — renewals a year once every certificate lives 47 days, and the multiple of today's.
- Busiest day ahead — the busiest renewal day in the next 90 days, and how many certificates renew on it.
By issuer
Automation coverage and average lifetime per issuer type (ACME, MSCA, CA connector, imported). Highlights issuers where you still have manual-path certificates — usually "auto-renew was never switched on" or "this issuer genuinely needs a manual step". The former is fixable; the latter requires an issuer migration.
Certificates to fix first
The active certificates that would struggle with shorter lifetimes, soonest to expire first (up to 50, with a note when there are more). Each row says why: Auto-renew off, Manual DNS, No distribution. Click a row to open the certificate.
Caching
The readiness computation runs aggregation pipelines over the whole project. It's cached for 60 seconds with singleflight — concurrent requests coalesce into one computation.
API
GET /api/v1/projects/{projectId}/dashboard/readiness-47day
# →
{
"score": 78,
"level": "at_risk",
"total_active": 120,
"automated_count": 98,
"manual_count": 22,
"avg_validity_days": 90,
"distribution_coverage": 61.5,
"automation_percent": 81.7,
"no_manual_dns_percent": 95.8,
"projections": [ ... ],
"at_risk_certs": [ ... ],
"has_more_at_risk": false,
"impact": { ... },
"timeline": [ ... ],
"by_issuer": [ ... ],
"top_insight": "...",
"recommended_actions": [ ... ],
"generated_at": "2026-04-21T14:23:45Z"
}
Troubleshooting
"My automation score is lower than expected"
A certificate counts as automated only when auto-renew is on and it does not use manual DNS validation. Check the at-risk list: every certificate tagged Auto-Renew Off or Manual DNS is pulling the score down.
Numbers haven't updated after I fixed a cert
The result is cached for up to 60 seconds. Reload the page after a minute.
See also
Video tutorial
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →