📑 I have found these related issues/pull requests

#6779

🔖 Feature description

Currently, Uptime Kuma treats TLS certificates with very short validity periods as expiring, which triggers warnings and notifications even though the certificates are still valid by design.

However, the EFF has recently announced official support for short-lived TLS certificates with a lifetime of just six days. These certificates are intended to improve security by significantly reducing the impact window of key compromise and encouraging automated, continuous renewal workflows.

I know, you can already set when notifications are being sent. But the system isn't generally ready for short-lived certificates yet.

✔️ Solution

As short-lived certificates gain broader adoption, monitoring systems like Uptime Kuma may need to adapt their expiration logic to distinguish between genuinely expiring certificates and intentionally short-lived ones that are regularly rotated.

❓ Alternatives

No response

📝 Additional Context

No response