Automatically inspect certificates for your HTTPS monitors, see expiry and handshake errors, and alert your team when renewal needs attention.
Certificate renewal can fail because of DNS changes, invalid challenge routes, expired credentials, rate limits, or a broken deployment. pingdan checks HTTPS endpoints independently of the renewal system, records the leaf certificate expiry, and warns attached channels once the certificate reaches the alert window.
Create a normal endpoint monitor. Certificate monitoring is enabled automatically for HTTPS.
pingdan performs a regular TLS handshake and stores the presented leaf certificate expiry.
When days remaining enter the warning window, attached channels receive the endpoint and expiry details.
Learn why automated renewal fails and how much warning time an operations team needs.
Read guide →Pair certificate checks with one-minute availability, latency history, and downtime alerts.
Read guide →Choose alert channels people will see and include enough context to act immediately.
Read guide →Automatic renewal is a process that can fail. Independent monitoring verifies the certificate users actually receive and gives you time to fix DNS, challenge, credential, or deployment problems.
pingdan monitors the leaf TLS certificate presented by each enabled HTTPS endpoint. HTTP-only endpoints do not have a TLS certificate to inspect.
Certificate sweeps run roughly twice daily, and a check can also be triggered on demand from the endpoint view. That cadence is appropriate because certificate expiry changes infrequently.
Warnings begin when a certificate has 15 days or fewer remaining. The alert includes the endpoint, URL, days left, and exact expiry time.
Create your first monitor in under a minute. Every feature is free.
Create a free monitor