Certificates renewed by hand: the TLS change that reaches a deal
Since March 2026 a public TLS certificate can be valid for at most 200 days, from March 2027 for at most 100 and from March 2029 for at most 47. Where renewal is automatic and watched, nothing changes. Around a sale it reaches certificates renewed by hand, installs and devices in the field, pinned mobile apps and the accounts that control the domains, and the outage tends to land after closing.
Every public website and API on HTTPS depends on a TLS certificate with an end date, and under the rules browsers and certificate authorities agree in the CA/Browser Forum, that date keeps coming closer. Since March 15, 2026 a public TLS certificate can be valid for at most 200 days. From March 15, 2027 the limit is 100 days, and from March 15, 2029 it is 47 days. Let's Encrypt, the free certificate authority many sites rely on, moves to 64-day certificates by default in February 2027. Where renewal is automatic and watched, none of this needs attention. Where a person renews a certificate once a year from a calendar reminder, it turns into a recurring outage risk, and around a sale that risk tends to land on the buyer.
This note is for owners preparing a sale, buyers reading a target and the advisors between them. It covers what the change does to a deal, not the engineering of the fix.
The dates
| When | What happens |
|---|---|
| March 15, 2026 | Maximum validity of a public TLS certificate drops from 398 to 200 days. Domain validation can be reused for 200 days instead of 398, and company identity data for 398 days instead of 825. |
| February 10, 2027 | Let's Encrypt issues 64-day certificates by default. A domain authorization is reused for 10 days instead of 30. |
| March 15, 2027 | Maximum validity drops to 100 days. Domain validation reuse drops to 100 days. |
| May 11, 2027 | The last 90-day Let's Encrypt certificate is expected to expire. |
| February 16, 2028 | Let's Encrypt issues 45-day certificates by default. Authorization reuse drops to 7 hours. |
| March 15, 2029 | Maximum validity drops to 47 days. Domain validation reuse drops to 10 days. |
The CA/Browser Forum dates come from section 6.3.2 and section 4.2.1 of the Baseline Requirements, as introduced by ballot SC-081v3, which passed in April 2025 with votes in favor from Apple, Google, Microsoft and Mozilla. The Let's Encrypt dates come from its posts Decreasing Certificate Lifetimes to 45 Days and 64-Day Certificate Lifetimes Coming Feb 2027. We keep these and other dates that matter to owners on our page of technology deadlines for owners. To see which of them apply to your own software, drop your project files into our stack check; nothing leaves your browser.
Why it reaches a deal
A certificate that expires does not degrade slowly. On the day it lapses, browsers show a full-page security warning, and programs that call an API refuse the connection. Three things move this from an IT routine into a review.
The first is where manual renewal hides. The main website is usually automated. The risk sits in the corners: an old server that nobody wants to touch, a customer-facing API that partners call from their own systems, a load balancer or appliance with its own certificate store, a product installed on a customer's premises, devices in the field, and mobile apps that pin a certificate or its key. At 100 days, a certificate renewed by hand needs a person at least four times a year. At 47 days, at least eight times. Each time is a chance to miss one.
The second is control. A certificate authority issues a certificate only after the company proves it controls the domain, and from 2029 that proof can be reused for only 10 days. Whoever holds the DNS, the registrar account and the certificate authority accounts holds the ability to renew. When those accounts sit with a founder, an agency or a former developer, the shorter cycle turns a loose end into a dependency that comes due every few weeks. This is part of the wider question in Ownership gaps in a software acquisition.
The third is timing. A deal that signs in late 2026 or 2027 closes into the 100-day rule and the Let's Encrypt change. The months after closing are also when domains, DNS and accounts are moved, merged or split, and every such move can quietly break a renewal that worked before. An expired certificate in the buyer's first year is an outage on the buyer's watch.
What a reviewer looks at
Most of this takes a few days when the target keeps records, and some of it can be checked from public data, because publicly trusted certificates are recorded in Certificate Transparency logs.
- The inventory: every public certificate for the company's domains, matched to a system, its issuer, its end date and a responsible person. The public logs often show certificates the team has forgotten.
- The renewal method: for each certificate, whether it renews automatically and deploys itself, or whether someone buys, downloads and installs it. Let's Encrypt suggests searching cron jobs, scripts and runbooks for fixed renewal intervals such as 60, 80 or 83 days, which stop working with shorter lifetimes.
- Monitoring: whether an expiring certificate or a failed renewal raises an alert to someone who acts on it, or whether the first signal is a customer.
- Pinning and embedded trust: whether the mobile apps, desktop clients, devices or partner integrations pin a certificate or key. Android's own documentation warns that a pin without a backup key means an app update is needed to restore connectivity when keys or authorities change.
- Installs outside the company: for on-premise products and devices, who renews the certificates at the customer's site, and what the contracts say about it.
- Who owns the accounts: the registrar, the DNS provider, the certificate authority accounts and the address that receives expiry notices, and whether each is registered to the company.
- History: past outages caused by expired certificates, and what changed after them.
How it turns into deal terms
On its own, this rarely moves a price. Automated renewal with monitoring and company-owned accounts is a note, not a finding. Manual renewal on a few internal systems is usually Low or Medium. It rises when customer-facing services or partner APIs depend on manual renewal, when pinned apps or devices in the field cannot be updated quickly, or when the accounts that control the domains are outside the company.
The size of the repair also varies, and a reviewer should say what decides it rather than call it easy: the number of certificates, how many sit on systems that cannot run a renewal client, whether devices and apps can be updated remotely, how many customer sites are involved, and how quickly account ownership can be moved. The review sets out that scope, the risk and the effort. The repair itself is separate work.
A hypothetical example: a company sells an on-premise product that ships with a certificate the customer renews by hand, and its sales contracts promise uptime. The reviewer lists the installs, the renewal duty and the contract language. The parties may then agree that the seller moves the critical services to automated renewal before closing, that the accounts transfer as a closing deliverable, that the integration plan carries the remaining work with an owner and a budget, or that the issue is disclosed with a plan attached. The choice is for the parties and their lawyers.
What a seller can do now
- Build the inventory. List every public certificate from your own records and from the public logs, with its system, issuer, end date and owner.
- Automate renewal and deployment wherever possible, starting with customer-facing sites and APIs, and test against Let's Encrypt's staging environment before February 2027 if you use it.
- Add monitoring that alerts on expiring certificates and on failed renewals, independent of the renewal tool itself.
- Move the accounts for the registrar, DNS and certificate authorities into company ownership, with more than one administrator.
- Review pinning in apps and devices, and plan the release or firmware change that removes the risk.
- Put it in the data room. One page with the inventory, the renewal method and the account owners answers most of the questions before they are asked.
Our exit readiness program tracks findings like this month by month before a sale.
What a buyer can do
A buyer can add certificates to the review scope at little cost: pull the public certificate records for the target's domains early, ask for the renewal method and account owners, and check whether the integration plan moves domains, DNS or accounts. If it does, renewals go on the list of things to verify before each move, not after. A red-flag memo early in the process, or a full technical due diligence, puts it on the table while it can still be planned.
A short checklist
- An inventory of every public certificate, with system, issuer, end date and owner.
- Renewal method for each certificate, with manual renewals marked.
- No fixed renewal intervals that assume 90-day or longer certificates.
- Alerts on expiring certificates and failed renewals, with a named recipient.
- Pinning in apps, devices and partner integrations identified, with backup keys or a removal plan.
- Renewal duties for on-premise installs and devices documented, with the contract terms.
- Registrar, DNS and certificate authority accounts owned by the company.
- For a buyer: domain, DNS and account moves after closing checked against renewals.
Questions
Will our website stop working when the new limits apply?
No. Certificates already issued stay valid until their own end date. The limits apply to new certificates, so each renewal after March 15, 2027 gives at most 100 days, and after March 15, 2029 at most 47. Sites that renew automatically notice nothing. The risk is in certificates someone renews by hand, which will need attention far more often.
Do the rules cover certificates on internal systems?
The CA/Browser Forum rules cover publicly trusted certificates, the kind browsers accept without warnings. Certificates from a company's own private authority, or self-signed ones on internal systems, follow that company's own policy. A reviewer still lists them, because their renewal is often manual too, but the public dates do not force their pace.
Why does a pinned certificate in a mobile app matter?
An app that pins a certificate or a public key accepts only that one. If a renewal brings a new key or a different authority and the app has no backup pin, it stops connecting until users install an update. Shorter lifetimes mean more renewals, so a pin that was a rare concern becomes a regular one.
Is this a reason to lower the price?
Rarely on its own. Automated renewal with monitoring is a note, not a finding. It becomes a deal point when customer-facing services or partner APIs depend on manual renewal, when apps or devices in the field cannot be updated quickly, or when the domain and certificate accounts are held by someone outside the company.
Where are the dates for other technologies?
On our page of technology deadlines for owners, which lists end of support, major releases and new rules for languages, frameworks, databases and platforms, each with its official source. The two certificate steps in March 2027 and March 2029 and the Let's Encrypt change in February 2027 are on it, with links to the rules themselves.
