Check availability, content and SSL certificates for any website. The HTTP(s) monitor is the most versatile check in Uptime Kuma, working with any public site, web application, REST API or health-check endpoint.
The HTTP(s) monitor type • Methods, headers and authentication • Accepted status codes and redirects • Keyword monitoring • SSL certificate expiry alerts • Practical examples • FAQ
The HTTP(s) monitor sends a request to a URL, waits for a response, and evaluates whether the result meets your criteria. If the server responds with an accepted status code within the timeout, the monitor is up. If the request fails, times out, or returns unexpected status, the monitor goes down and triggers notifications.
Because it works over standard web protocols, HTTP(s) monitors check any public website, web app, REST API or health endpoint. HTTPS URLs automatically track SSL/TLS certificates.
When creating an HTTP(s) monitor, configure:
{"Authorization": "Bearer token123"}Authentication:
Default accepted: 200–299. Adjustments:
Format: 200-299,301,302 (comma-separated list, ranges allowed).
A successful HTTP status doesn’t always mean everything works. Your web server might return 200 OK while displaying an error page, maintenance page or wrong content. Keyword monitoring checks what the page actually says.
Enter a Keyword — a string Uptime Kuma searches for in the response body. Found = pass; not found = down.
Enable Invert Keyword to reverse logic: monitor is up only when the keyword is NOT present. Handy for detecting error messages — set keyword to “503 Service Unavailable” with inversion enabled to alert when error text appears.
Common use cases:
"status":"ok"Good to know: keyword matching is case-sensitive. “Welcome” with capital W won’t match “welcome” lowercase. Copy exact text from the page source.
Every HTTPS monitor tracks the SSL/TLS certificate automatically. Monitor detail page shows issuer, validity period, days remaining.
Default notification 30 days before expiry. Adjust in Certificate Expiry Notification field — set 14 or 7 days for tighter warnings, or add multiple thresholds (30, 14, 7) for escalating reminders.
For sites using self-signed certificates or untrusted authorities, enable Ignore TLS Errors. Check continues despite invalid cert; expiry notification still works.
Tip: on SmartXHosting, SSL auto-renews — certificate monitoring is most valuable for third-party services hosted elsewhere.
https://www.mybusiness.co.ukhttps://shop.mybusiness.co.uk/shopIf the shop stops displaying “Add to basket” due to a plugin conflict or database error, you’re alerted immediately.
https://api.mybusiness.co.uk/health{"Content-Type": "application/json"}{"check": "full"}"status":"ok"Monitor any website for £1/month
HTTP, keyword, SSL and API monitoring — all included with SmartXHosting Uptime Kuma Hosting for a single monthly price. UK-hosted.
View Uptime Kuma HostingQ: What HTTP method should I use?
A: GET for standard websites. POST/PUT only for APIs requiring a body. GET is the default and works for virtually all monitoring.
Q: How does keyword monitoring work?
A: Uptime Kuma searches the response body for a specific string. Found = up. Invert Keyword flips the logic so up = keyword absent.
Q: Does SSL certificate monitoring work automatically?
A: Yes. Every HTTPS monitor tracks expiry and alerts at the configured threshold (default 30 days). No extra setup.
Q: What codes for sites with redirects?
A: Add 301 and 302 alongside 200–299. Or use Max Redirects setting to follow them automatically.
Q: Can I monitor a password-protected page?
A: Yes. Basic Auth, Bearer Token or NTLM in the Authentication section. Credentials are stored encrypted in Uptime Kuma’s configuration.
Q: What’s the fastest check interval?
A: 20 seconds (vs 1 min on commercial SaaS paid tiers). Be mindful of the load on monitored services.