Connect to any ws:// or wss:// server, watch the live connection status, send messages once it's open, and read a timestamped log of everything sent and received.
Your browser connects directly to the server you enter — nothing passes through My Panda Toolbox.
Uses a genuine browser WebSocket, unaffected by the same-origin restrictions that block plain fetch requests.
A colored indicator tracks connecting, open, closed and error states as they happen.
Every sent and received message gets its own timestamped, color-coded line in a scrolling log.
Test any WebSocket endpoint without writing a line of client code.
A WebSocket starts as an HTTP handshake and then upgrades to a persistent, full-duplex connection, letting either side send messages at any time without the request/response overhead of ordinary HTTP calls. That makes it a natural fit for chat, live dashboards, multiplayer state and anything else that needs low-latency, two-way communication.
The browser sends an HTTP Upgrade request; a compatible server responds with a 101 status and the connection becomes a raw duplex socket.
Once open, onmessage fires for every frame the server sends, and calling send() pushes a frame to the server immediately.
Either side can close the connection with a status code and reason. The onclose handler fires whether the close was clean or the connection simply dropped.
wss:// encrypts the connection with TLS, the same relationship https has to http, and is required when testing from a page loaded over https.
Questions about connections, failures and privacy.
Yes. It creates a genuine browser WebSocket to the URL you enter. Unlike fetch, WebSocket connections are not restricted by the same-origin policy, so this works against any server that accepts connections from a browser.
Common causes are an unreachable host, a server that requires a specific sub-protocol or auth header the browser cannot send, a mixed-content block (using ws:// from an https page), or a server that simply rejected the handshake. The status indicator and log will show Error or Closed when this happens.
Yes. Once a connection is closed, the Connect button becomes available again, so you can reconnect to the same URL or type a new one.
Yes. Both are supported. wss:// is the encrypted version of the protocol, similar to how https relates to http, and is required when testing from a page served over https.
No. The only network connection made is the WebSocket you choose to open. The log itself lives only in your browser tab and is never stored or transmitted elsewhere.