certificate.watch

What it is

Certificate Watch is an SSL/TLS certificate monitoring service for developers and operations teams that need to make sure website certificates do not expire and sites remain online. Its core value is 24/7 certificate monitoring, with notifications before expiry to reduce the risk of outages caused by missed renewals. The page also notes that certificate validity periods are expected to become shorter over time, increasing renewal frequency and making certificate monitoring more important.

Key features and ecosystem

Based on the available content, it offers SSL expiry alerts, certificate change notifications, a centralized dashboard, and email notifications. The centralized dashboard is useful for managing multiple URLs, while change notifications can help detect when a certificate has been renewed or modified. The Pro plan also includes Custom Notifications and API Integration, suggesting some level of integration with internal workflows. However, the page does not disclose API documentation, SDKs, Webhook, Slack, PagerDuty, Prometheus, or other specific integration capabilities. Supported languages and frameworks are also not mentioned, as this is essentially an external monitoring service rather than an in-app SDK.

Pricing

The pricing structure is straightforward: Free monitors 1 URL and includes expiry alerts and email notifications; Basic costs $5/month, supports up to 10 URLs, and adds SSL change notifications; Pro costs $20/month, supports up to 100 URLs, and adds custom notifications, API Integration, and priority support. Paid plans are billed monthly and can be canceled; the terms state that fees are non-refundable except where required by law. For small and medium-sized teams, Basic is inexpensive, and Pro’s per-URL cost is also reasonable.

Pros and cons

The advantages are its clear positioning, low barrier to entry, usable free tier, and coverage of the two key scenarios: certificate expiry and certificate changes. The downside is that public information is limited: it does not specify monitoring frequency, how many days in advance alerts are sent, notification retry mechanisms, SLA, or history logs, nor does it disclose whether it is open source or supports self-hosting. The API is only listed as a Pro feature, with no details on usage or limits, so teams evaluating automation integrations should confirm these points further.

Who it is for and access from China

It is suitable for individual site owners, small SaaS products, and operations/SRE teams that want centralized monitoring for certificates on public websites. If an enterprise already has a complex observability platform, a solution that integrates more deeply with the existing alerting stack may be a better fit. The text does not provide information about access from mainland China, and payment methods are not disclosed, so users should test access stability and payment availability before purchasing. Alternatives include UptimeRobot, Better Stack, Oh Dear, StatusCake, or a self-built cron/Prometheus/Alertmanager certificate monitoring setup.