ACME clients, host panels, and CDN cert managers create and renew certificates.
Certificates · Continuous watch
How to continuously monitor SSL certificates.
To monitor SSL certificates continuously, check each hostname's certificate expiry on a schedule and alert a named person well before the date. Aepto can check expiry on each website monitor, next to uptime.
Why certificates still surprise teams
Automation helps until it does not. Portfolios multiply the exception cases.
- Let’s Encrypt and host-managed TLS removed most manual renewals.
- What remains are the exceptions: a CDN cert on the wrong hostname, a forgotten subdomain, a load balancer that stopped renewing, a client site on shared hosting with no owner watching mail.
- Continuous monitoring is how you catch those exceptions without weekly human audits.
- When a certificate fails, browsers warn visitors and trust drops faster than with a soft error.
What good SSL monitoring looks like
- 01 Early window alerts, not day-of panic
- 02 Hostname named in the alert
- 03 Same Attention queue as uptime and domain expiry
- 04 Clear owner: who fixes ACME, host panel, or CDN
Aepto’s place in the certificate loop
Visibility and triage. Issuance stays with your existing stack.
Surfaces SSL windows for domains in your portfolio so the exception cases do not hide.
Portfolio scale
Agencies and hosters watch many hostnames. One queue beats twenty provider dashboards.
Next to uptime
Pair with global uptime so “up but untrusted” is still visible.
Next to renewals
Domain expiry and cert expiry are different clocks. Track both via expenses and SSL alerts.
When SSL is fine but the page is still dead
Certificate health does not prove checkout works. After TLS is green, paid Content Monitoring catches body-level failures HTTP 200 can hide. Start from the definition of domain monitoring if you are building the full stack.
Aepto does not replace your CA or ACME automation. It makes certificate risk visible across the book.

Why are certificate expiries getting more frequent?
Shorter lifetimes mean more renewals, and fewer reminder emails.
398 → 47 days
maximum lifetime for public TLS certificates, cut in steps from March 2026 to March 2029
Source: CA/Browser Forum SC-081
Every monitor
in Aepto can check certificate expiry next to uptime
What does a shorter lifetime mean for 40 certificates?
Worked example: one certificate per domain, each used for its full lifetime. Dates follow the CA/Browser Forum schedule above.
| Maximum lifetime | Applies from | Issuances per certificate per year | Issuances across 40 certificates |
|---|---|---|---|
| 398 days | Until 14 March 2026 | about 0.9 | about 37 |
| 200 days | 15 March 2026 | about 1.8 | about 73 |
| 100 days | 15 March 2027 | about 3.7 | about 146 |
| 47 days | 15 March 2029 | about 7.8 | about 311 |
Arithmetic is 365 divided by the lifetime. Automated renewal usually happens before the last day, so real counts run higher.
Who renews each certificate?
An alert is useless if nobody knows which panel renews the cert.
| Where TLS ends | Who renews | What to check |
|---|---|---|
| CDN (for example Cloudflare) | The CDN, automatically | Both the edge certificate and the origin certificate |
| Hosting control panel | The host, often via Let's Encrypt | Renewal still works after DNS changes |
| Cloud load balancer | Your cloud account | The managed certificate covers the right hostnames |
| Server with an ACME client | Your cron job or certbot | The renewal job still runs |
| Forgotten staging subdomain | Often nobody | Delete it or monitor it |
Common questions
What does continuous SSL monitoring check?
That certificates serving your hostnames remain valid and that expiry windows are visible early enough to renew or fix automation before browsers show warnings.
Is SSL monitoring included on Free?
Yes. Free includes SSL visibility for domains in your plan limits, alongside uptime, DNS, renewals, and PageSpeed. See Pricing for domain caps.
Does Aepto issue or renew certificates?
No. Issuance stays with your CA, host, or ACME automation. Aepto alerts so the window does not sneak up across dozens of names.
Why do portfolios miss SSL more than single sites?
Many hosts, many dashboards, and staging leftovers. Central Attention items beat a sticky note per certificate.
How does this relate to uptime?
A site can be “up” while browsers block users on certificate errors. Monitor both. Link uptime and SSL in the same queue.
Catch certificate windows before browsers do.
Free includes SSL visibility within plan domain limits.
