HTTP & SSL auditing
The fastest way to know something's wrong.
A single lightweight request checks reachability, the HTTP response, and the full SSL/TLS handshake - a rapid canary for infrastructure health, not a substitute for browser-level testing.
- Status codes & redirects - exact-match validation, with redirect chains followed or flagged.
- SSL/TLS health - certificate expiry, TLS version, chain completeness, and wildcard usage.
- Configurable method, timeout, expected status code, and HTTP version
SCHEDULING
Check every minute, or run it on demand.
Availability is built for speed - the tightest schedule of any TestCLIX test type, so outages get caught within seconds, not hours.
Available frequencies
| Frequency | Runs / day | Best for |
|---|---|---|
 Every 1min | 1,440× | High-traffic, revenue-critical endpoints |
 Every 5min | 288× | Mission-critical uptime monitoring |
 Every 6h | 4× | Standard uptime monitoring |
 Every 24h | 1× | Low-priority checks & staging environments |
| Do not schedule | On-demand | Manual / CI triggers |
Live schedule preview
Today Tue · Jul 28
LiveLive schedule for Tue · Jul 28, running every 1min. 703 passed and 4 failed of 707 checks run so far today. Next check at 11:47.
707 / 1440 today · next
Locations
Run availability checks from the regions that matter to your users
Outages and SSL issues can be region-specific. Each availability test runs from a single location you choose - create one test per region to compare and catch geography-specific problems.
- Five regions available - four in Europe, one in North America, with more by request.
- One location per test, set when you create it or from Edit test properties afterward
- Duplicate a test to a second region to spot location-specific outages
Alarms & Notifications
Alerting that matches your risk tolerance
Set how many recent runs to evaluate and how many failures should trigger a notification. Higher thresholds suit tests that depend on external services or dynamic content, to avoid alert fatigue.
- Evaluation period & failures to alarm - both configurable from 1 to 50 runs.
- Notify by email, Slack, Telegram, Jira or webhooks - sent the moment the threshold is crossed
- Up to 10 custom headers per test - filter TestCLIX traffic out of analytics, allowlist it past bot protection, or test auth and localization.
- Evaluation period:
- 10 runs
- Failures to alarm:
- 3 runs
Recent runs
WHAT'S INCLUDED
Everything you need to catch outages fast
Availability tests come with everything listed here, included in every plan.
Fast HTTP checks
Validate status codes, response time, and redirect chains on every run - a lightweight canary for infrastructure health.
SSL & TLS auditing
Catch certificate expiry, weak TLS versions, broken chains, and unexpected wildcard certificates before they become outages.
Every minute
The fastest cadence on TestCLIX - catch outages within a minute, or trigger a check manually whenever you need one.
Multi-location testing
Choose London, Paris, Frankfurt, Warsaw, or Ohio. Run a separate test per region to catch geography-specific outages.
Instant alerts
Email, Slack, Telegram, Jira or webhooks - with a configurable evaluation period and failure threshold.
Custom headers
Attach up to 10 custom HTTP headers per test for analytics filtering, bot allowlisting, or auth testing.
FAQ
Frequently asked questions
HTTP reachability and status codes, redirect behavior, response time, and SSL/TLS certificate health - a fast technical health check, not a full user-flow test.
Availability is a lightweight GET/HEAD check for uptime and SSL - it doesn't click through your UI. For login flows, checkout, or form validation, use Scenario instead.
Every minute - the fastest cadence on TestCLIX - or disable scheduling and trigger checks manually or from CI.
Certificate expiry (warn 7, 14, or 21 days ahead), a TLS version below your configured minimum, a missing intermediate chain, or an unexpected wildcard certificate.
The status flips to Error and, once your evaluation period and failures-to-alarm thresholds are crossed, you're notified by email, Slack, Telegram, Jira or webhook. Acknowledge a known issue to reset the window and auto-recover once it's fixed.
Each test runs from one location - choose London, Paris, Frankfurt, Warsaw, or Ohio, with more by request - so create a test per region to catch geography-specific outages.