Applies to: Uptime Kuma 2.5.9 (HTTP(s) and HTTP(s) - Keyword monitors, domain expiry through RDAP)

Every HTTPS monitor in Uptime Kuma already reads the site's certificate and shows how many days are left. To get an alert before it expires, tick Certificate Expiry Notification on the monitor and attach a notification. Uptime Kuma 2.5.9 can also warn about the domain name expiring, with Domain Name Expiry Notification, for domains whose registry offers RDAP.

You need a working notification first (email, Telegram, Slack and so on). See website uptime alerts with Uptime Kuma for that part.

1. Turn on certificate expiry alerts

  1. Open the monitor for your site and press Edit, or create one with Add New Monitor, type HTTP(s), and the https:// address.
  2. Under Advanced, tick Certificate Expiry Notification. It is off by default.
  3. Leave Ignore TLS/SSL errors for HTTPS websites unticked. In the 2.5.9 source code, the expiry check is skipped completely when that option is on, so a monitor with it ticked never sends a certificate alert.
  4. Under Notifications, tick at least one notification and press Save.

The monitor page then shows a Cert Exp. box with the expiry date and the days left. Lab example for https://example.com:

Cert Exp.
( 2026-12-26 )
46 days

2. Choose when the alerts arrive

The warning days are set once for all monitors, in Settings, Notifications, section TLS Certificate Expiry ("HTTPS Monitors trigger notification when TLS certificate expires in:"). The defaults are 7 days, 14 days and 21 days.

  • To add a day, type the number in the box under the list, press the add button next to it (its label is "Add a new expiry notification day") and then Save. In our lab, adding 30 gave the list 7, 14, 21 and 30 days.
  • To remove one, press the red X next to it and Save.

As the page says, "Notifications must be assigned to a monitor to function": the days do nothing for a monitor with no notification ticked.

What the alert looks like

We tested this with a lab HTTPS site whose certificate had 10 days left. Uptime Kuma showed 9 days in the Cert Exp. box and, because 9 is below the 14-day threshold, sent this email straight away:

[lab certificate][https://localhost:8443/] server certificate localhost will expire in 9 days

Only one email arrived for that threshold. In the 2.5.9 code, Uptime Kuma records each threshold it has alerted on and does not repeat it, so you get one warning at 21 days, one at 14 and one at 7, not one per check.

If you use Let's Encrypt, an expiry warning usually means automatic renewal has stopped working. Check it with certbot renew --dry-run (see Nginx HTTPS with Certbot) and read the certificate directly with OpenSSL.

3. Turn on domain expiry alerts

We checked this on 2.5.9 rather than assume it: the feature is there and it works for .com domains.

  1. Edit the monitor and, under Advanced, tick Domain Name Expiry Notification. On new monitors in our lab it was already ticked.
  2. Make sure a notification is ticked and press Save.
  3. Set the warning days in Settings, Notifications, section Domain Expiry. The defaults are again 7, 14 and 21 days.

The monitor page then shows a Domain Exp. box. Lab example for example.com:

Domain Exp.
( 2027-08-13 )
276 days

How it works in 2.5.9, from its source code:

  • Uptime Kuma asks the registry's RDAP service for the expiry date, using the list of RDAP servers published by IANA. It does not use WHOIS.
  • Each domain is looked up at most once a day, however short the monitor interval.
  • It works on monitors with a URL or hostname: HTTP(s), HTTP(s) - Keyword, HTTP(s) - Json Query, TCP Port, Ping, DNS, SMTP and a few others. A Push monitor has no domain, so it cannot use it.
  • The expiry is read for the registered domain, so a monitor for https://shop.example.com checks example.com.

When a domain cannot be checked, the edit form says so under the checkbox. For a lab address it showed:

The domain "localhost" is not a candidate for domain expiry monitoring, because its public suffix ".localhost" is not managed by ICANN

For a country or new TLD whose registry has no RDAP service in the IANA list, the 2.5.9 interface text reads "Domain expiry monitoring is not available for ".TLD" because no RDAP service is listed by IANA", with the real extension in place of TLD. For those domains, check the date with the whois command or your registrar's renewal reminders instead.

The domain alert itself reads "Domain name example.com will expire in N days" in the 2.5.9 code; we could not trigger one in the lab, as no test domain was close to expiry.

Where to run it

Expiry checks only need outbound internet access, so they work the same on managed Uptime Kuma hosting and on your own Uptime Kuma VPS. To install it yourself, see installing Uptime Kuma with Docker.

Official documentation: Uptime Kuma wiki, domain expiry code in 2.5.9.

Related services

Web hosting

shared hosting on Virtualmin with NVMe storage, free SSL and email.

SSL certificates

DV, OV and wildcard, with free installation help.

Reseller hosting

white-label cPanel hosting for your own clients.

Was this answer helpful?

Still stuck? Open a ticket