A certificate issued the week of March 15, 2026 reaches the end of its 200-day validity period in early October 2026, twice as fast as it would have under the old 398-day standard. That means the renewal workload security and IT teams budgeted for annually is now landing twice a year, and it's landing for the first time this fall.

This isn't a future risk to plan around anymore. It's a present one to manage.

In April 2025, the CA/Browser Forum approved Ballot SC-081v3, a motion originally proposed by Apple and backed by major browser vendors and certificate authorities, including Google/Chrome, Mozilla, and Sectigo. The ballot set a phased schedule for shrinking public SSL/TLS certificate validity and Domain Control Validation (DCV) reuse periods:

The rationale was straightforward: longer certificate lifespans mean longer windows of exposure if a certificate or its underlying key is ever compromised, and longer stretches between validation checks mean domain ownership data can drift out of date. Shorter lifespans, paired with post-quantum cryptography's push toward faster key rotation, are part of the same broader shift toward crypto-agility.

That was the policy. What's landing on IT and security teams now is the operational reality of it.

Halving certificate validity both doubles how often a certificate needs to be renewed and compounds every process built around that renewal:

• Renewal volume doubles, immediately: Every certificate an organization manages now needs attention twice as often as it did under 398-day validity. Teams that renewed annually are now renewing roughly every six months, with no reduction in per-renewal effort if the process is still manual.
• Discovery gaps surface faster: Certificates that were "set and forget" under a 13-month cycle now resurface for action in under seven months. Any certificate that wasn't properly inventoried the first time around is due again, sooner than expected.
• DCV reuse windows tighten too: Domain Control Validation reuse periods are compressing alongside certificate validity. Teams that don't have a repeatable DCV workflow will feel that friction on every renewal, not just some of them.
• The margin for error shrinks: With renewals landing more frequently, a missed one is a recurring risk. Expired-certificate outages become a matter of when, not if, for organizations still relying on spreadsheets and calendar reminders.

None of this is unique to any one industry or company size. Any organization with a public-facing certificate footprint (which is to say, nearly all of them) is now working through this same compression at the same time, which is part of why the effects are showing up broadly this fall rather than trickling in gradually.

Manual certificate management was already expensive before validity periods shortened. However, Forrester Total Economic Impact™ (TEI) study conducted on behalf of Sectigo found that organizations automating certificate lifecycle management with Sectigo Certificate Manager (SCM) saw a 243% return on investment, including $1.3 million in reduced provisioning labor and $965,000 in reduced renewal expenses over three years, plus a further $2.4 million in avoided outage-related costs.

Those figures were calculated against a slower renewal cadence. At 200-day validity, the labor and risk that automation offsets double in frequency. Every dollar manual processes were costing per renewal cycle is now being spent twice as often, and every hour spent chasing down expiring certificates is now an hour spent twice as often too. The ROI case for automation holds at 200-day lifespans, and strengthens with each stepdown.

The first 200-day renewal cycle tends to expose the same gaps:

• Certificate inventories that are incomplete, outdated, or split across teams and tools.
• No clear ownership for renewals, DCV, or certificate-related incident response.
• Renewal tracking that lives in spreadsheets, tickets, or someone's calendar rather than a centralized system.
• No automated issuance or renewal path (e.g., via ACME) for at least the highest-volume certificate types.

If any of these sound familiar, this renewal cycle is the signal to act before the next one (100-day validity) arrives in March 2027.

1. Reconcile your certificate inventory now: Confirm which certificates were issued around March 15 and are approaching expiration, and identify the owner for each. While you’re at it, inventory every certificate across your organization.
2. Automate what you can before the next renewal hits: Even partial automation for your highest-volume or highest-risk certificates reduces the operational load of the next compression.
3. Establish clear ownership across security, IT, and DevOps: Renewal cadence is now fast enough that ambiguity about who's responsible causes real delays.
4. Build (or stress-test) your DCV workflow: With reuse periods shrinking, a repeatable validation process matters as much as the renewal itself. Consider persistent DCV from CLM providers like Sectigo, so you can set it and forget it with domain validation.
5. Set monitoring and alerting thresholds now, not after a near-miss: With renewals landing every six months instead of annually, alerting windows calibrated for a 398-day cycle are already out of date.
6. Use this cycle as a dry run for 100 days: Whatever breaks or takes too long this time is exactly what needs fixing before March 2027, when the same workload compresses again.

The gaps that show up in a first 200-day renewal cycle are rarely about certificates themselves. They're about the manual processes wrapped around them. Automated certificate lifecycle management (CLM) addresses each one directly:

• Discovery: A continuously updated inventory replaces one-time audits, so certificates don't fall out of view between renewal cycles.
• Issuance and renewal: Protocols like the Automated Certificate Management Environment (ACME) let certificates renew automatically as they approach expiration, without a person tracking dates manually.
• DCV: Centralized, repeatable domain validation workflows keep pace with shrinking reuse windows instead of becoming a bottleneck at each renewal. Persistent DCV simplifies domain validation at scale.
• Monitoring and alerting: Centralized visibility flags certificates approaching expiration before they become urgent, rather than after a service is already degraded.
• Governance: Clear audit trails and ownership records replace the ambiguity that slows down response when something does need attention.

None of this eliminates the underlying policy shift. Validity periods are still shrinking on schedule and will likely continue to shrink after the 47-day stepdown. What it removes is the labor and risk of managing that shift by hand.

200-day validity was framed as an adjustment window, and for organizations acting now, it still can be. But the next stepdown is already scheduled: 100-day maximum validity takes effect March 15, 2027, cutting today's renewal cycle in half again. Whatever gaps this first 200-day cycle exposes will only get harder to manage at 100 days, and unsustainable at the eventual 47-day maximum in 2029.

Organizations that use this cycle to build real automation will absorb the next one. Organizations that patch through it manually will hit a harder wall in less than a year.

Renewal frequency will keep climbing between now and 2029. Manual, calendar-driven certificate management wasn't built for this pace, and the current renewal cycle is proving it in real time.

Sectigo Certificate Manager (SCM) automates certificate discovery, issuance, renewal, and monitoring end-to-end, so a compressed validity period becomes a configuration change, not a fire drill. Schedule a demo to see how SCM handles the renewal surge already underway.