Warnings and outages stay distinct
By default UPKira warns 14, 7, and 1 day before expiry. You can type your own days, from 1 to 90. A warning marks the monitor degraded and opens an incident immediately. It is not called down.
Hear about a certificate before it expires.
An SSL monitor connects to the site and reads the certificate your visitors' browsers check. A date inside your warning window is degraded. An expired or invalid certificate is a failure.
Expired and invalid certificates
An expired certificate, or one the check cannot trust, is a failure. UPKira confirms that failure before the monitor is down, so a handshake glitch is not treated as an expired certificate.
What this does not do
This check does not install or renew the certificate. It does not scan every hostname on an account, and it does not replace a certificate transparency feed. Private addresses are refused, the same as every other target.
Questions people ask first
- Will I be paged 14 days before expiry?
- You get a degraded incident at the first warning day you configured. The default days are 14, 7, and 1. An expired certificate is the one that is confirmed and then marked down.
- Can I point it at an IP address?
- The target is a site URL. Addresses that are private or cloud metadata are refused before the check runs.
Cron jobs · API checks · All features · Pricing · Getting started