SSL certificate management is the ongoing work of tracking your site's digital certificates: which ones your websites use, who renews them, and how you find out before one expires. Most small business owners never touch a certificate directly, which works until the day a quote form or booking page shows a browser warning.
This guide is for owners of local service businesses in the Twin Cities East Metro, the St. Croix Valley and western Wisconsin. It covers the new, shorter certificate lifetimes, how automated renewal works, what visitors see when a certificate lapses, and a checklist you can hand to whoever runs your site. For the one-time setup, see our SSL certificate installation guide. This post stays on what happens after that.
What SSL certificate management covers
"SSL" is the familiar name. The certificates in use today are TLS certificates, and the job is the same: a certificate lets a browser confirm it is talking to your domain over an encrypted connection. Every certificate has an expiration date, so a certificate is something you keep current, not something you install once.
Management comes down to four questions for every hostname you use:
- Where does the certificate live? On your host, on a CDN, or on a third-party tool.
- Who renews it? A named person or a named system.
- Is renewal automatic, and does anything have to stay in place for it to work?
- Who is told if renewal fails?
On a simple site, the answers are short. A host or CDN often handles everything, and the checklist later in this post takes a few minutes. The trouble starts when a business has pieces on several hosts, which is common for service companies.
SSL certificate management and the shorter lifetimes
Publicly trusted certificates are getting shorter. The CA/Browser Forum, the group where certificate authorities and browser makers set the rules, approved ballot SC-081v3 in April 2025. Per the Forum's ballot page, the maximum validity falls from 398 days to 47 days, with the reductions running from March 2026 to March 2029. The schedule below comes from the Forum's Baseline Requirements (the version current in November 2026 is 2.3.1, dated October 4, 2026), which list these compliance dates.
Scroll to see all columns
| Compliance date | Maximum validity of a subscriber certificate |
|---|---|
| March 15, 2026 | 200 days |
| March 15, 2027 | 100 days |
| March 15, 2029 | 47 days |
The ballot page also says the time a certificate authority may reuse a completed domain validation drops, eventually to 10 days for validation data tied to the names on a certificate. By 2029 the reuse limit for domain validation is 10 days, shorter than a 47-day certificate's life, so the domain check repeats at every renewal. If your DNS or web server setup blocks that check, the renewal fails.
This rule applies to certificates from publicly trusted authorities. Our own arithmetic on the end state: a 47-day certificate has to be replaced about eight times a year. A calendar reminder once a year no longer works. Renewal has to be automatic, and someone has to watch for the failures.
Automated renewal with ACME
Automatic renewal runs on ACME, a standard protocol that Let's Encrypt describes as a way for a server to obtain browser-trusted certificates without human intervention. A small program called an ACME client runs on the server. It proves control of the domain by adding a DNS record or serving a file, requests the certificate, and repeats the process at renewal.
Let's Encrypt is the best-known free authority, and its own schedule shows how the new rules reach ordinary sites. Per its lifetime announcement, the default classic profile moves to 64-day certificates on February 10, 2027 and to 45-day certificates on February 16, 2028. The same post says a fixed 60-day renewal schedule "will no longer be sufficient," and describes renewing about two thirds of the way through a certificate's life as acceptable. Its integration guide recommends renewing automatically when a third of the lifetime is left.
Two practical points follow. If you run your own server, check that your ACME client renews by remaining lifetime, not on a hard-coded number of days. And do not rely on an email from the authority. Let's Encrypt ended its expiration emails on June 4, 2025 and points subscribers to third-party monitoring instead.
Managed certificates on hosts and CDNs
For most small business sites, the simplest answer is to let the host or CDN own the certificate. Cloudflare's documentation says it issues and renews Universal SSL certificates for domains added to and activated on Cloudflare, and handles issuance, renewal and deployment automatically. On a full setup, those certificates cover the root domain and first-level subdomains. Your own host may offer something similar. Ask, and read what the certificate covers.
Automatic does not mean unconditional. Cloudflare's domain validation page states that if domain control validation is not completed, the authority cannot issue or renew the certificate, and visitors will see SSL/TLS errors. On a partial setup, where DNS stays with another provider, you may need to keep validation records in place. The lesson is general: changing DNS providers, deleting an "unused" record or moving a subdomain can quietly break renewal.
Scroll to see all columns
| Where the certificate lives | Who renews it | What you still do |
|---|---|---|
| Host or CDN managed (for example Cloudflare Universal SSL) | The provider, automatically | Keep DNS and validation records intact; confirm subdomain coverage |
| Your own server with an ACME client | The client, on a schedule you set | Renew by remaining lifetime; monitor for failures; keep the client updated |
| Third-party tool on your subdomain (booking, quotes, payments) | The vendor, usually | Ask the vendor in writing; keep the DNS record that points to them |
| Purchased certificate installed by hand | You or your web contractor | Name an owner; set reminders; plan to move to automation |
What visitors see when a certificate expires
Browsers put a full-page warning in front of the site. Firefox Help lists SEC_ERROR_EXPIRED_CERTIFICATE and says the error occurs when a website's certificate has expired, and the same article notes that a wrong system clock on the visitor's device can also cause date errors. Chrome's error page for certificate problems reads "Your connection is not private," per Chrome Help, which ties date errors such as NET::ERR_CERT_DATE_INVALID to the visitor's clock. Test what your own visitors would see.
Picture a Woodbury homeowner trying to book a furnace repair on a January morning. A browser warning gives them a reason to try another company. The harm is lost leads while the problem lasts, plus the time it takes you to find out.
Where small service businesses get caught
The main site is rarely the problem. The trouble is the other hostnames. Consider an illustrative example. Brightwater HVAC, a made-up Stillwater company, has its main site on a managed host, a quote form at quotes.brightwater.example run by a software vendor, and a payment link on a third-party domain. The owner knows about one certificate. Three hostnames exist, and a lapse on any of them breaks a step of the customer's path.
Booking and quote tools sit on subdomains of your domain, and a certificate on that subdomain may be issued and renewed by the vendor. That arrangement depends on the DNS record you set up when you connected the tool. One way this breaks is that an old record gets cleaned up years later and nobody connects it to the renewal.
Our guide to website management and maintenance places certificate checks next to updates, backups and uptime, and our post on protecting your website from hacks covers the wider security picture.
An SSL certificate management checklist
- Inventory every hostname. List the main domain, www, and every subdomain used for forms, booking, payments, a customer portal or email tracking. Check your DNS records for ones you forgot.
- Record where each certificate lives. Host, CDN, your server or a vendor.
- Name the renewal owner. One person or company per hostname, with a backup. Put it in writing.
- Confirm renewal is automatic. If a certificate is renewed by hand, schedule the work, and plan to move it to automation.
- Add monitoring. Use an uptime or certificate monitor that alerts you before expiry, and send alerts to a shared inbox, not one person's.
- Protect the DNS login. DNS access decides who can change validation records. Keep it with the business.
- Review after changes. A new host, a redesign, a DNS move or a new booking tool means rechecking the inventory.
- Test the pages. Open each hostname in a browser every quarter and watch for warnings.
If you want help listing your hostnames and renewal owners as part of a website design or rebuild, contact McKinney Creative Ventures.