EN
Home Category Tool

WebSocket Test

Connect to ws/wss endpoints and exchange messages

FAQ

Do messages pass through your server?

No. The browser connects directly from your device to the target ws service, so the messages never touch this site.

What is the difference between ws and wss?

wss is WebSocket over TLS, the same relationship https has to http. Production endpoints should use wss.

Can I test an authenticated endpoint?

This tool does not support custom headers. Endpoints requiring a token or cookie need a dedicated client such as Postman or the browser console.

About this tool

Connects to a ws:// or wss:// endpoint straight from the browser, sends and receives text messages and logs the session. Messages do not pass through this site - the browser talks to the target server directly, which also means the target sees your real IP. Check that before connecting anywhere unfamiliar.

Why connections fail, most common first:

  • ws:// from an HTTPS page: blocked as mixed content; use wss:// (or test from an http:// page locally).
  • The server validates Origin: many frameworks only accept same-origin or whitelisted Origins, and a browser handshake carries this site's domain, so you get 403.
  • Wrong path: most libraries mount at /ws or /websocket, so wss://host alone often 404s.
  • Reverse proxy does not forward Upgrade: Nginx needs the Upgrade and Connection headers explicitly passed through, or the handshake never reaches the backend.
  • Untrusted certificate: a self-signed wss fails outright; browsers offer no "continue anyway".

If the handshake does not finish within 10 seconds the log says so - on some networks the socket neither opens nor errors, leaving the UI stuck at "connecting", and this notice tells you where to look.

Limits: only text frames are handled, binary frames are not decoded; custom headers are not supported, so token- or cookie-authenticated endpoints cannot be reached from here (use Postman or a code client); there is no heartbeat or reconnect. To verify two-way traffic you need an echoing server - the built-in sample points at a public echo service, and you should never send tokens, internal addresses or real data through one.