SSL certificate monitoring

An expired certificate takes a site down as surely as a broken server: browsers show a full-page warning, and most visitors leave. UptimeChecker checks the certificates of your sites with every check, and warns your team before one runs out.

In short

Checked like a browser checks

Signed by a trusted authority, valid for the name of the site, not expired and not valid only from a later date.

A warning 14 days ahead

One email to every member of your space when a certificate expires within 14 days. A renewed certificate gets a warning of its own when its time comes.

An invalid certificate is an outage

A site with a certificate that is not valid counts as down, with the same email as for a server that does not answer.

Why certificates still expire

Most certificates renew themselves today, for example with Let's Encrypt. That works until it does not: a changed server, a DNS record that moved, a renewal job that stopped after an update. Nobody notices, because the old certificate keeps working for weeks. Then it expires, often at night or on a weekend.

What exactly is checked

Each check of a site with an address that starts with https:// opens a new connection and lets Go's TLS library verify the certificate, the same rules browsers follow:

If the site redirects, for example from example.com to www.example.com, the certificate of every step is checked, and the one that expires first counts for the warning.

When you get an email

What it does not check

Only the certificate the site shows. It does not check the strength of the encryption, old protocol versions or whether the certificate was revoked, and it does not grade your setup. For that, there are dedicated tests such as the one of SSL Labs.

Never be surprised by an expired certificate

Add your sites, and the certificates are watched with them.

Get started

More questions? Read the answers.