Files
Checkmate/server
colinjtsen2010 75516a220d fix: handle IPs, avoid wrong parent-domain lookups, cache whois results
- Bare IP addresses and non-domain hosts (localhost, IPv6) now return a
  null expiry instead of throwing, so they no longer spam error logs.
- Extract the registrable domain with tldts instead of walking up
  hostname labels, so a subdomain can never accidentally return its
  parent domain's expiry date.
- Cache WHOIS lookups per registrable domain (1h positive, 10min
  negative) so visiting details pages does not re-query the registry
  every time.

Addresses review feedback on #3834.
2026-08-13 12:02:49 +08:00
..
2026-07-09 10:21:09 -07:00
2025-04-20 11:29:53 -07:00
2026-06-16 10:59:46 -07:00
2025-09-22 12:53:44 -07:00
2025-04-20 11:29:53 -07:00
2025-04-20 11:29:53 -07:00
2026-05-29 10:33:15 -07:00
2026-06-09 12:35:57 -07:00
2026-06-09 12:35:57 -07:00
2025-04-20 11:29:53 -07:00
2026-06-09 12:35:57 -07:00

Checkmate backend

The backend service for Checkmate, an open source uptime and infrastructure monitoring application

This directory contains the backend of Checkmate, which handles data processing, storage, and API services for the Checkmate monitoring tool. The backend is responsible for managing uptime checks, handling real-time alerts, and storing historical monitoring data.

Checkmate's backend is designed to be lightweight and scalable, ensuring reliable performance even with a high number of active monitors.

Installation & documentation

For setup instructions, configuration details, and deployment guidelines, please visit our official documentation at docs.checkmate.so.