Radardue
Guide · updated October 2026

KeyChest shut down: what to use instead

KeyChest's website now says it "officially ceased its operations as of 14 Feb, 2026". If you relied on it for certificate expiry alerts, those alerts have stopped. Here's what it did, what can replace it, and how to move over in an afternoon.

What KeyChest did

You typed in a domain and KeyChest found the certificates for its subdomains, using public Certificate Transparency logs, then sent weekly reports and alerts before they expired. It had a free tier for personal use. That "enter a domain, see everything" approach is what most people will want to keep.

Replacements, honestly compared

Facts below are from each product's own website, checked on 15 October 2026. Prices change, so check before you buy.

ToolFinds subdomains for youDomain expiryBest for
Radardue (us)Yes, from Certificate Transparency logsYes, over RDAPMSPs, agencies and IT teams with many clients. Free for 25 items, paid from $19/month.
TrackSSLNo, hosts are added by handNot mentioned on its siteA polished certificate monitor, including private certificates on higher plans. Free for 2 certificates, paid from $19/month (20 certificates).
Cert Spotter (SSLMate)Watches CT logs for certificates issued for your domainsNoSecurity teams that want to spot certificates they didn't issue. From $15/month, 30-day trial. The free open-source edition only alerts on new certificates.
Uptime KumaNo, one monitor per URLYes, over RDAP (since 2.1.0)People who self-host and already use it for uptime. Free and open source.

Our take: if you used KeyChest on a handful of your own sites, Uptime Kuma or a free plan anywhere will do. If you looked after other people's domains, you want discovery from CT logs plus one list across clients, which is what we built Radardue for.

Moving your hosts over

  1. List the domains you had in KeyChest. If you can't log in any more, your old weekly report emails list them.
  2. Run each domain through a CT log search. Our free domain scan shows every hostname that has had a public certificate, with the certificate it serves today. No signup.
  3. Add them to your new monitor and send alerts to a shared channel (Slack, Teams, a group mailbox), not one person's inbox.
  4. Check how each host renews. Let's Encrypt moves to 64-day certificates from 10 February 2027, and fixed renewal schedules built for 90-day certificates will start failing. See what breaks and how to fix it.

How Radardue fits

Add a domain and Radardue finds its hostnames from Certificate Transparency logs, checks the certificate each one actually serves every day (on any port), reads the domain's registry expiry over RDAP, and keeps manual renewals such as licenses next to them, grouped by client. Alerts go by email, Slack, Microsoft Teams, Discord, Telegram or webhook. Explore the demo or scan a domain first.