SSL certificate management services discover every TLS certificate your business depends on, automate issuance and renewal, and alert you before anything expires. That has moved from nice-to-have to necessary: since March 15, 2026, public certificates can be valid for at most 200 days, falling to 100 days in March 2027 and 47 days in March 2029.
If you have had an expired-certificate outage, or suspect one is coming, tell us how your certificates are handled today and we will suggest the quickest fix.
Why the 47-day schedule changes everything
The CA/Browser Forum, the body of certificate authorities and browser makers that sets the rules for public TLS, approved ballot SC-081 in 2025. It shortens certificate lifetimes in three steps:
- March 15, 2026: maximum validity of 200 days (down from 398).
- March 15, 2027: maximum validity of 100 days.
- March 15, 2029: maximum validity of 47 days, with domain validation reuse cut to 10 days.
With a one-year certificate, a calendar reminder and a manual renewal were survivable. At 47 days, every certificate renews roughly eight times a year. Any certificate still renewed by hand, such as one pasted into a load balancer, a Java keystore or an appliance, becomes a recurring outage risk.
What expires is rarely what you expect
The main website is usually fine. The outages come from the forgotten ones: an API subdomain, a payment callback endpoint, an internal admin tool, a mail server, an IoT device, or a certificate pinned inside a mobile app.
What SSL certificate management services cover
1. Discovery and inventory
You cannot renew what you do not know about. Discovery combines Certificate Transparency log searches for your domains, DNS enumeration, scans of your public IP ranges, and a review of cloud accounts (load balancers, CDNs, API gateways) and Kubernetes clusters. The output is an inventory listing each certificate, its owner, where it is installed, its issuer and its expiry.
2. Automated issuance and renewal
The ACME protocol is the backbone of modern automation. Depending on where the certificate lives:
- Linux servers: Certbot or acme.sh with a deploy hook that reloads Nginx, Apache or HAProxy; or a web server like Caddy that manages certificates itself.
- Kubernetes: cert-manager issuing and rotating certificates as cluster resources.
- AWS: AWS Certificate Manager renews certificates attached to load balancers and CloudFront automatically. Azure Key Vault and Google Certificate Manager offer similar options.
- Legacy systems and appliances: scripts or vendor APIs that push renewed certificates, or a reverse proxy placed in front so the appliance no longer terminates public TLS.
DNS-01 versus HTTP-01 validation
HTTP-01 is simplest for a single public web server. DNS-01 is required for wildcard certificates and works for hosts that are not reachable from the internet, but it needs API access to your DNS provider, so that credential must be scoped tightly and stored securely.
3. Independent expiry monitoring
Automation fails quietly: a DNS token expires, a firewall blocks validation, a reload hook breaks. Monitoring should check the certificate actually being served on each endpoint, not just the file on disk, and alert well before expiry. Let's Encrypt stopped sending expiry reminder emails in 2025, so many teams lost a safety net without noticing. Expiry checks fit naturally into your existing observability stack alongside uptime checks.
4. Internal and private certificates
Service-to-service traffic, VPNs, databases and internal dashboards often use certificates from a private certificate authority. The public validity limits do not apply to them, yet they expire just as painfully. A private CA run through AWS Private CA, HashiCorp Vault or step-ca, with short-lived certificates issued automatically to workloads, is far easier to operate than a spreadsheet of long-lived internal certificates. Service meshes such as Istio and Linkerd handle mutual TLS rotation for you inside Kubernetes.
5. Policy and key handling
Decide which certificate authorities you allow (enforced with CAA DNS records), who may request certificates, minimum key types (ECDSA P-256 or RSA 2048 and above), and where private keys live. Keys should never be emailed or committed to a repository.
Common mistakes to fix first
- One wildcard certificate everywhere. Convenient, but a single leaked key exposes every subdomain. Use per-service certificates where automation makes it easy.
- Certificates owned by a former employee's email. Renewal notices go nowhere. Use a shared, monitored mailbox and named owners in the inventory.
- Pinning in mobile apps. Pinning a leaf certificate breaks the app at every renewal. Pin to a public key you control, or rely on standard validation.
- Incomplete chains. Serving the leaf without intermediates works in some browsers and fails in others and in API clients.
Choosing a provider for certificate lifecycle work
When comparing SSL certificate management services, ask for three things: a complete inventory you own, automation implemented as code in your repositories and clusters, and monitoring that pages a person rather than sending an email nobody reads. Commercial certificate lifecycle platforms are worth it for large estates with many internal certificate authorities; most growing companies get further with ACME automation plus solid monitoring.
iJurug Soft handles certificate automation as part of its cloud management and DevOps work, alongside uptime monitoring, patching and backups. If you prefer to hand off the whole operational layer, our managed cloud services include it, and our SRE services tie certificate health into reliability targets.
Frequently asked questions
Do existing certificates stop working on the new dates?
No. A certificate issued before a deadline stays valid until its own expiry date. The limits apply to newly issued certificates.
Are paid certificates exempt from the shorter lifetimes?
No. The limits apply to every publicly trusted TLS certificate, whether domain, organization or extended validation. Private certificates from your own internal authority are not covered, but should still be automated.
How long does it take to automate our certificates?
That depends on how many endpoints you have and how many sit on appliances or legacy systems. Cloud-hosted and Kubernetes workloads are usually quick; on-premises devices take longer.
Send us your domains and a rough picture of where your services run, and we will come back with an inventory approach, an automation plan and a clear quote. Use the contact form or write to info@ijurugsoft.com.