WebSocket Tester
Connect to WebSocket servers, send messages, and inspect live responses from your browser.
Debug WebSocket clients from the browser
Connect to a ws:// or wss:// endpoint, send frames, and read server replies in a timestamped log. Useful for echo servers, staging APIs, and IoT prototypes. For REST checks, try the SSL Checker when TLS handshakes fail.
Tips for reliable tests
- Public echo services such as
wss://echo.websocket.orgare handy for smoke tests. - Self-signed certificates on
wss://URLs may be blocked by the browser before your code runs. - Send JSON with a trailing newline when the server expects line-delimited messages.
Frequently Asked Questions
Why does the browser hide error details?
WebSocket security rules limit cross-origin error messages. Use server logs when you need the exact TLS or handshake failure.
Can I test local servers?
Yes, as long as the page can reach the host. Mixed content rules apply when the site is HTTPS but the socket URL is plain WS.
Are messages stored?
No. The event log lives in memory until you refresh or clear it.
Does this support subprotocols or custom headers?
Browser WebSocket APIs do not let pages set arbitrary HTTP headers. Use server-side clients when you need custom headers.