Skip to content
Sign inStart free

Use case

Pulsy watches your TLS/SSL certificates and warns you before they expire. On every HTTPS monitor it reads the certificate's expiry from the handshake, tracks the days remaining, and can alert your team while there is still time to renew.

Start monitoring free
Pulsy / Monitor overviewDEMO DATA

HTTPS · GET

www.example.com

Down
Response trace240–300 ms / HTTP 503
Successful responses, then failed HTTP 503 checks from 09:08. Incident opens at 09:10. No response-time value is plotted for failures.
Failed checks → threshold reached → incident at 09:10

The problem

  • An expired certificate takes a site offline for every visitor at once, often outside business hours.
  • Renewal reminders scattered across calendars and registrars are easy to miss.
  • Certificate checks bolted on separately from uptime monitoring drift out of sync.

How Pulsy helps

  • Extracts certificate expiry during the normal HTTPS check — no separate tooling.
  • Tracks days-until-expiry per monitor so you can act before the deadline.
  • Sends TLS-expiry alerts through the same channels as your uptime alerts.
  • TLS expiry monitoring is included within your plan’s monitor allowance. Self-hosting has no subscription monitor cap.

  1. Example: add an HTTPS URL and enable certificate-expiry notifications on its channel.
  2. Choose the interval, timeout and failure threshold. For HTTP checks, configure the expected status and any body, header or JSON assertions.
  3. Configure a notification channel, send an explicit test, and review the first recorded result.

Detection depends on the check schedule, timeout and failure threshold. Delivery depends on your channel provider; alerts are not instantaneous.

Example setup

Illustrative inputs and responses — not a live check or an import file.

GET https://www.example.com/
HTTPS · TLS

Use an HTTPS endpoint and review the observed certificate expiry. Select expiry events on an alert channel; a check cannot diagnose why renewal failed.

Add each HTTPS URL as a monitor in Pulsy. On every check it reads the TLS certificate's expiry date, tracks the days remaining, and can alert you before it lapses — alongside up/down and response-time status.

Yes. Pulsy records certificate expiry per HTTPS monitor and can notify your channels ahead of the expiry date so you have time to renew.

Yes. TLS-expiry monitoring is built into Pulsy and included on every plan, including the free tier.

Track Linux host CPU, RAM, swap, filesystem use, load and uptime alongside website checks. Sustained resource pressure and a disconnected agent become actionable incidents.

Create a server monitor, then run its one-command systemd installer or Docker Compose setup. The agent reports over outbound HTTPS; Linux amd64 and arm64 are supported.

Default thresholds are 90% for CPU, RAM and each filesystem: 3 violating reports to alert, 2 healthy reports to recover. Missing reports cause an outage after 3 intervals. RAM alerts are not confirmed OOM events.

Available on every Cloud plan. Each server uses one monitor slot. Reports default to 60 seconds, subject to the plan’s minimum interval; history follows plan retention.

Explore Linux server monitoring

Start with one website or Linux server. Understand the incident and know what to tell your customers.

Start monitoring freeSelf-host on GitHub