Certificate expiration
SSL check warns in advance that the certificate expiration date is approaching or the certificate cannot be obtained from the specified host.
This task type requires PRO plan.
When to use
- When the site or service uses HTTPS or another TLS protocol.
- When it's important not to miss the certificate expiration.
When to choose another type
- If you need to monitor domain registration expiration, use domain check.
- If you need to check the availability of the page or API itself, use HTTP.
Form fields
| Field | What it means | What to specify | Example |
|---|---|---|---|
| Name | Name of the check. | Specify for which site or service the certificate is being monitored. | SSL for example.com |
| Group | Allows assigning the task to a project or section. | Select a group if you want to keep project tasks together. | Main project |
| Host | Domain or service address whose certificate needs to be checked. | Specify the public host that actually uses this certificate. | example.com |
| Port | Port where TLS is available. | Leave 443 for standard HTTPS or specify another port for non-standard TLS service. | 443 |
| Minimum days until expiration | Warning threshold before certificate expiration. | Specify a time buffer sufficient for renewal or reissuance of the certificate. | 14 days |
| Timeout | How long to wait for connection to the TLS service. | Leave a reasonable buffer for normal network latency. | 30 seconds |
| Allow self-signed certificate | Don't consider it an error if the certificate is not trusted by browsers. | Enable for internal services with their own certificate. | Disabled |
| Allowed check points | From which points the certificate can be retrieved. | Leave all points if no special regional scenario is needed. | All check points |
| Interval | How often to check the certificate. | Leave the default value — hourly checks are sufficient for certificates. | 1 hour |
| Notification channels | Where to send messages about issues and recovery. | Check the channels where you actually read notifications. | Telegram and email |
| Reports | Periodic task summaries. | Enable if you want to receive an overview without manual panel access. | Weekly report |
When the alert will trigger
- If the certificate expiration date becomes less than the specified threshold.
- If the certificate cannot be obtained from the specified host and port.
- If the certificate is not trusted or is issued for a different name — except in the case described below.
Internal services and self-signed certificates
In an internal network, a self-signed certificate is a common thing, and the check would honestly fail with a trust error. Enable the «Allow self-signed certificate» parameter, and the check will stop treating both the lack of trust and the mismatch between the certificate name and the host as an error.
Expiration date monitoring is preserved — it's the whole reason the task exists. Only
trust checking and name matching are disabled.
Notification settings
For each notification channel in the task, you can set additional parameters. They only apply to DOWN events.
| Parameter | What it does |
|---|---|
| Enabled | Allows or disables sending notifications through this channel for this task. |
| Delay for PRO | Delays the first DOWN notification by the selected time (up to 12 hours). Convenient to avoid alerts for short-term failures. |
| Repeat after PRO | Periodically repeats the notification while the task remains in DOWN status (up to 1 hour between repeats). Suitable when it's important not to miss a prolonged outage. |
"Delay" and "Repeat" parameters do not affect UP events and recovery notifications.