Know about a certificate problem before your visitors do
An expired certificate takes a site down as surely as a dead server. PingWise checks the certificate chain and expiry date on every check, and warns you days in advance.
What’s checked.
On every HTTPS monitor
The certificate is verified on each check. You get a warning when it expires in fewer than the days you set, and an expired certificate counts as an outage.
Certificates on any host and port
A TLS monitor checks the chain and expiry directly, including mail servers through SMTP STARTTLS.
Mail and file servers
IMAP, POP3 and FTP monitors can connect with TLS on 993, 995 and 990 and check the certificate too.
Domain expiry and mail health, included.
Domain expiry
The domains of your monitors are collected automatically. You get an alert 30, 14, 7 and 1 days before each expires, and on the day. It uses no credits. For registries that publish no date (.gr, .de, .eu, .nl and others), you can enter the date by hand.
Blocklist monitors
Tell you when your mail server’s IP lands on SpamCop or Barracuda. No credits.
SPF/DKIM/DMARC monitors
Tell you when a record goes missing or breaks. No credits.
Check one now.
SSL checker
Any site’s certificate, chain and days left.
Domain expiry checker
When a domain expires.
Questions
Is a certificate warning an outage?
No. A warning about an upcoming expiry counts as up. Only an expired or invalid certificate is a failure.
Can it check a certificate on a non-web port?
Yes, with a TLS monitor. Common ports need no verification; other ports need a verified domain.
How much does it cost?
A daily-style check is cheap: a TLS monitor every hour uses 720 credits a month, well inside the free allowance.
Related: Uptime monitoring · Website monitoring · Monitor types