Renewing certificates means repeating the same steps every time
At my workplace we renew server certificates once a year, a quietly tedious job. It roughly goes like this:
- Log in to the certificate authority’s web console (DigiCert, etc.)
- Type in the target domain, organization details by hand every time
- Generate a CSR (certificate signing request), copy-paste it
- Handle the domain validation email or DNS record
- Download the issued certificate, deploy it to the server
- Copy the expiry date into the Excel certificate register
Once a year was bearable, but learning that the “once a year” premise is about to collapse, I decided to act now.
Short answer: CSR generation was never the pain; typing into the CA’s web form was. I keep the form values in a CSV, then have Claude Code fill the form through Claude in Chrome, stopping before Submit so I check it myself.
TLS certificate lifetimes are shrinking to 47 days in stages
Ballot SC-081v3, approved in April 2025 by the CA/Browser Forum (the standards body of certificate authorities plus browser vendors), shortens the maximum lifetime of SSL/TLS certificates in stages:
| Effective from | Maximum lifetime |
|---|---|
| March 15, 2026 | 200 days |
| March 15, 2027 | 100 days |
| March 15, 2029 | 47 days |
Compared with the current 398 days, that’s close to 8 renewals a year by 2029. The domain validation (DCV) reuse period is also set to drop from 398 days to 10, so “once validation is done, renewal is routine” won’t hold either (sources: DigiCert blog, Sectigo summary of the CA/B Forum decision).
If we keep renewing by hand, I can imagine this happening:
- A renewal gets missed right after the person in charge changes, taking a site down with an expired certificate
- Typos with every manual entry, burning more time on resubmissions
- The register goes stale, leaving nobody sure which server expires when
We already handle monitoring, visualization with Grafana plus the Infinity plugin, so I won’t cover that here. This time I tried reducing the effort of the application work itself with Claude Code.
The pain is typing into the web form, not making the CSR
What actually feels tedious in renewals isn’t generating the CSR, but typing the organization, department, domain, SANs into the CA’s console every time. A CSR is one openssl command, but transcribing into the web form can’t be scripted, so a person ends up typing while looking at the browser.
So I tried having Claude Code’s browser control do that transcription. Claude Code works with the official Chrome extension “Claude in Chrome”; with it installed, you just tell the CLI “fill in this form” and it operates the browser directly. Before trying, keep these in mind:
- As of 2026, Claude in Chrome is a beta for paid plans such as Pro, Max, Team, Enterprise; it isn’t available on the free plan
- Only Google Chrome is supported (not Edge, Brave, Arc, etc.)
- The extension uses the browser’s signed-in state as is, so stay signed in to the CA site beforehand
- Being a beta, it has accuracy limits such as misclicks, using more of your allowance than normal chat
Once ready, keep each certificate’s form values in a CSV, hand it over, then tell it to fill in the web form:
# certs.csv: CommonName,SAN,Organization,Department,Country www.example.com,www.example.com;example.com,Example Corp,IT Dept,US
My instruction to Claude Code looks something like this:
Fill the DigiCert certificate request form that's open now with row 1 of certs.csv. In the CSR field, paste the contents of csr/www.example.com.csr as is. When you're done, don't press Submit; let me review the form first.
I always include that last sentence. A mistake in a certificate request has a big impact, so it only fills in the form; I always check with my own eyes before pressing Submit. The idea is to hand Claude Code just the dullest part: “figure out what goes where, find the field, paste it”.
Updating the register too
After renewing, we still record the renewal date, new expiry, person in charge in an Excel register. I had Claude Code append the results to the certs.csv used for the request, then pour them straight into the register format. It looks like it’ll cut down the quietly annoying problem of missed register entries too.
Summary
2029, when the 47-day rule fully applies, is still a way off, but the 200-day phase starts in March 2026, so renewals will steadily get more frequent. Monitoring differs by workplace, but just standardizing the application work now should keep you calm as lifetimes drop to 100 then 47 days.
Plenty of people must find manual certificate renewal a chore, so I hope this helps anyone in the same spot.
References: DigiCert - TLS Certificate Lifetimes Will Officially Reduce to 47 Days, Sectigo - CA/B Forum Cuts SSL/TLS Certificate Lifespan to 47 Days


コメント