WebSocket Checker
Test whether a WebSocket endpoint (ws:// or wss://) is reachable and completes the opening handshake, from the outside, the way a real client connects. Checked from Uptimeify's EU servers.
What watches these brands watches your clients too
End the manual growth tax.
Running checks by hand eats valuable agency time. Uptimeify monitors your entire client portfolio from one place: on a fair, organization-wide quota model, on secure EU infrastructure. No per-client fees, no surprises.
Frequently asked questions about WebSocket Checker
It performs the real WebSocket opening handshake described in RFC 6455: an HTTP Upgrade request with a Sec-WebSocket-Key, then it verifies the server replies with 101 Switching Protocols and a matching Sec-WebSocket-Accept header. Open means the handshake succeeded and the endpoint is live. Rejected means the server answered but didn't upgrade (often a plain HTTP page, a 404, or auth being required). Unreachable means nothing answered in time.
ws:// is an unencrypted WebSocket connection, while wss:// runs the same protocol over TLS, the secure form you should use in production, just like https. If you enter a host without a scheme, this tool defaults to wss://. For wss:// it completes the TLS handshake to the validated IP first, then performs the WebSocket upgrade.
The connection is made from Uptimeify's EU servers, not your browser, the URL you enter is used only to perform the check and is not stored. It refuses private and reserved addresses and pins the connection to the resolved public IP. As an EU-built, EU-hosted provider, Uptimeify keeps this off US infrastructure and clear of US Cloud Act exposure, which matters for agencies handling client data under GDPR.
Ready to Keep Testing That Realtime Connection?
A handshake now says nothing about tonight. Uptimeify probes your service's port and reachability on an interval and reports the outage before your users are typing into nothing.