Docs

Site Uptime & SSL

Watch your websites, APIs, and TCP services around the clock and stay ahead of SSL expiry.

All Documentation

Types of Uptime Checks

Open Optimux > Site Uptime to monitor any public endpoint - your marketing site, a staging environment, an internal API, or a plain TCP service. Five check types are supported: HTTP and HTTPS (with optional status code and response time targets), TCP (any port), Ping (ICMP reachability), and Keyword (content must or must not appear in the response body). Each monitor has its own interval, timeout, and expected-status settings.

SSL Grading from A+ to F

Every HTTPS monitor is graded for certificate quality. Optimux inspects the negotiated protocol, cipher suites, intermediate chain, and certificate validity, then assigns a letter grade just like the public SSL Labs tests, without sending your URLs to a third party. Weak ciphers, missing intermediates, and outdated protocols all drop the grade and trigger an issue on the server detail page.

Domain & Certificate Expiry

For every domain behind an HTTPS monitor, the platform tracks both the SSL certificate expiry and the domain registration expiry. You choose how far in advance you want to be warned - 30, 14, or 7 days - and Optimux sends one alert per milestone through your notification channels. No more scrambling because a certificate you forgot about expired on a Sunday.

System Updates from the Web

Server Updates (inside the Optimux menu) shows every pending OS package update per server, grouped by severity. When you are ready to apply them, the "Run Update" button triggers a full pre-check, runs apt or dnf in the background, and performs a post-check against six critical services (SSH, firewall, time sync, core network, cron, and the monitoring link itself). The server is placed in Maintenance mode for the duration so alerts stay quiet.

Historical Uptime & Response Time

Every uptime monitor keeps a history of status changes and response times. The detail view shows the last 24 hours, 7 days, 30 days, or a custom range, so you can prove an SLA to a customer or spot a slow degradation that nobody else has noticed yet. Failed checks store the error response so you can see exactly what the endpoint was returning at the time.