For owners of websites, shops and web apps: add your domains, and each certificate is checked daily for its expiry date, issuer and chain; you get an alert weeks before expiry, when a certificate changes unexpectedly, or when an automatic renewal did not happen.
I need thisService in preparation · No payment is accepted on this page
Small agency running 40 client sites, most with automatic renewal. One morning an alert says the certificate of a client's shop expires in 14 days and has not renewed — the DNS record for validation was removed during a redesign. The agency fixes it the same day, and the shop never shows a browser warning to its customers.
Choose your planAn expired SSL certificate turns a working website into a full-page browser warning. Visitors leave, online shops stop taking orders, and connected apps or payment callbacks fail, often on a weekend when nobody is watching.
Automatic renewal has made this rarer, but not rare. Renewals fail when a DNS record changes, a server moves, a firewall blocks validation or a forgotten subdomain keeps an old certificate. The problem is usually discovered by a customer, not by the owner.
The service watches your certificates from the outside, the way a visitor's browser sees them. You add your domains and subdomains — the main site, the shop, the admin panel, the mail server, the API — and each one is checked every day.
For every host you see the certificate's expiry date, the issuer, the names it covers and whether the chain is complete. A clear list shows which certificates are fine, which expire soon and which have problems.
Alerts go out 30, 14 and 3 days before expiry by email or to a team chat. If a certificate that should renew automatically is still the old one close to its expiry, you get a separate alert that the renewal did not happen.
The service also warns when a certificate changes unexpectedly: a different issuer, a new key, or a certificate issued for your domain that you did not order. Such changes can mean a misconfiguration, or that someone else obtained a certificate for your name.
When a site goes down or the certificate is served incorrectly — wrong name, incomplete chain, an old certificate on one server behind a load balancer — the alert says what is wrong, so you know where to look.
Agencies and freelancers who look after many client sites can group hosts by client and send each client a short monthly report showing that their certificates are in order.
A history is kept for every host: when each certificate was issued and replaced, and every alert that was sent. When something breaks, you can see at a glance whether the certificate changed recently and which change came first.
Getting started takes a few minutes: add domains one by one or paste a list. Nothing needs to be installed on your servers; the checks run from outside.
The service is built for website owners, small businesses, agencies and freelancers anywhere. It is in preparation: we are checking whether site owners need it before it is built.
The service monitors and alerts; renewing and installing certificates stays with the site owner or their hosting provider.
No, certificates are checked from outside, the way a browser sees them.
30, 14 and 3 days before expiry, and whenever a renewal fails or a certificate changes unexpectedly.
Yes, any host name that serves a certificate.
No. It monitors and alerts; renewal stays with you or your hosting provider.
Not yet. The service is in preparation, and we are checking whether site owners need it.