WebSocket Handshake Check
A WebSocket test performs only the opening handshake against a ws:// or wss:// endpoint: it sends the HTTP Upgrade request and confirms the server responds with 101 Switching Protocols, then closes the connection.
How to Use
• WebSocket URL:Enter a ws:// or wss:// URL (a bare host defaults to ws:// and path /); http/https URLs are accepted and mapped to ws/wss
• What is checked:The opening handshake (HTTP Upgrade → 101 Switching Protocols) is completed, then the connection is closed immediately — no application frames are exchanged
• Result fields:connected (handshake accepted), handshake time in ms, the HTTP status code returned, and the negotiated subprotocol if any
• Node selection:Optionally select specific nodes; all available nodes are used by default
What WebSocket testing is for
A WebSocket test performs only the opening handshake against a ws:// or wss:// endpoint: it sends the HTTP Upgrade request and confirms the server responds with 101 Switching Protocols, then closes the connection. This is the WebSocket analogue of a TCP connect check — a fast way to confirm the endpoint is live and speaking the WebSocket protocol without exchanging any application data.
Common uses include verifying that a real-time backend (chat, notifications, live dashboards, trading feeds) accepts connections, checking that a reverse proxy or load balancer correctly forwards the Upgrade header, and confirming that a wss:// endpoint presents a valid TLS certificate before the handshake.
Frequently asked questions
Does the test exchange any messages?
The tool closes after the WebSocket handshake without deliberately exchanging application messages. The handshake can still trigger connection handlers, authentication, logs or billing; it is not guaranteed to be side-effect free.
What does the HTTP status mean?
A successful WebSocket handshake returns HTTP 101 (Switching Protocols). Any other status — 400, 401, 403, 404, 426, 5xx — means the server refused the upgrade, often because of a missing header, authentication requirement, wrong path, or an endpoint that is not actually a WebSocket.
Can I test a wss:// (secure) endpoint?
Yes. Use a wss:// URL and the probe negotiates TLS as part of the handshake. If the certificate is invalid or the TLS handshake fails, the check reports a handshake failure with the underlying error.
What is a subprotocol?
WebSocket connections can negotiate an application-level subprotocol (e.g. graphql-ws, mqtt) during the handshake. The result shows the subprotocol the server selected, if any — useful for confirming the endpoint speaks the protocol your client expects.
References and result limitations
Online results reflect the queried source or probe state at that time. Record the target, time, nodes or data source, and parameters when citing them. A single result does not establish continuous availability everywhere.
These references explain protocol or format rules; they do not endorse results produced by this site.