Backlog

Next up

In Progress

Done

Main Roadmap

Users would like to create custom monitors: IPs, Ports, HTTP, HTTPS, SMTP, and other services for sites, devices, and items that they have to manage that might be internal or not one of their already supported sites.

In Review

Add other monitoring types

Valeria Kurolapova

It would be helpful to track intermediate certs in the chain. We had an intermediate expire which another monitoring service detected (BetterUpTime) which we use for uptime monitoring primarily.

Track intermediate certs

Users would like to get notifications via the WhatsApp channel.

WhatsApp notifications

Users would like to have the possibility to track a certificate from a specific location (EU/USA/Rest of the World at least) in case a site is blocked in some countries.

Choose monitoring locations

Users would like to have the ability to send a test email notification

The ability to send a test email notification

Users would like to have an option to just check a single domain's certificate instead of triggering all certificates. Let's say the example of updating an expiring cert live and want to validate that the specific host is now updated.

check a single domain's certificate instead of triggering all certificates

Users would like to increase the number of certificates listed per page above 25 (maybe 50 or 100).

Increase the number of certificates listed per page above 25

In some cases, an end point might be behind a CDN and what you really want to monitor is the cert from the origin. The way to resolve this would be with an IP and an optional host header.

Support host header for fetching origin certs

Its impossible to tell which channel your integration is connected to right now so we should store and display it in the UI.

Store and display Slack channel name

s there any way to customize the notification times for specific certificates. We have some short duration certificates (Let's Encrypt) that are only good for 90 days. I really don't need to be notified when they're 30 days out from expiry. They auto renew, so 7 days would be fine. However, for most of our certs we want to know at 30 days.

Per domain notification options

<p>The ability to upload the certificate manully</p>

Planned

Manual certificate monitoring

Free trial

Users would like to have multiple logins for their account

Completed

Allow multiple users per account

Can the ability to edit the Expiry Date be added to the functionality? We have some domains located in networks where we cannot install the on-prem agent and the Expiry Date is inaccurate as it is seeing the WAF cert.

trackssl

Main Roadmap