WebSocket Tester
A browser-based WebSocket client for probing ws:// and wss:// servers, sending messages, and reading back close codes without installing anything.
This WebSocket tester opens a real connection straight from your browser so you can check whether a socket server is reachable and behaving. Point it at any ws:// or wss:// endpoint, click Connect, and the status flips through connecting, open, and closed while every frame you send or receive lands in a timestamped log. When the server drops the connection you get the raw close code and reason back, which is usually what you need when a WebSocket debugger session goes wrong. It runs as a plain browser WebSocket client, so wss:// endpoints connect directly with no CORS preflight in the way.
No messages yet. Connect to a ws:// or wss:// endpoint, then send a frame or a ping.
How it works
- 1
Connect to an endpoint
Type or paste a ws:// or wss:// URL (http/https gets rejected with a suggested fix) and hit Connect. The badge tracks the handshake from connecting to open.
- 2
Send frames or a ping
Once the socket is open, type a message and Send it, or hit Ping to fire a text 'ping' frame. Sent rows are marked ↑, received rows ↓, each with a local timestamp.
- 3
Read the close code
On disconnect the log prints the close code and reason (e.g. 1000 normal, 1006 abnormal). Toggle auto-reconnect to retry dropped sockets, or copy the whole transcript.
Instant & 100% private — nothing is uploaded
Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.
Frequently asked questions
- What URL can I use to try the WebSocket tester?
- The public echo server is the easiest smoke test. Enter wss://echo.websocket.org, click Connect, then Send any text — the server sends the exact same payload straight back, so you'll see your ↑ sent line followed by a matching ↓ received line. That confirms the connection, the send path, and the receive path in one round trip.
- Why did my WebSocket close with code 1006?
- 1006 is an abnormal closure: the connection dropped without a proper close frame, so the browser never got a status from the server. It usually means the TCP connection failed, the TLS handshake was rejected, a proxy or firewall cut the socket, or the server crashed. A clean shutdown shows 1000 instead.
- Does the Ping button send a real WebSocket ping frame?
- No — the browser WebSocket API doesn't expose the protocol-level ping/pong control frames. The Ping button sends a normal text message with the payload 'ping', which is the standard workaround for an app-layer heartbeat. If your server echoes or replies, you'll see the response in the log.
- Can it test secure wss:// sockets?
- Yes. Secure wss:// endpoints connect the same way as ws://. One caveat: because this page loads over HTTPS, browsers block plain ws:// connections to remote hosts as mixed content, so use wss:// for anything that isn't ws://localhost.
More tools
More from the Hivly network
Free sister tools on our other sites.
