WebSocket Debug Tool
Connect to ws or wss endpoints, send messages, and inspect realtime responses for WebSocket integration and troubleshooting.
Connect to a ws or wss endpoint, send messages, and inspect realtime responses and connection state changes in one page.
Useful for frontend-backend integration, auth troubleshooting, message format checks, and gateway pass-through validation.
Debug ws/wss connections, send messages, and inspect realtime server responses.
When ws/wss Is Blocked
- If the page is HTTPS, browsers block ws:// mixed content. Use wss:// instead.
- Untrusted TLS certificates break wss handshakes. Use a valid cert and correct server time.
- If your server validates Origin, add the current site domain to the allowlist.
- Browser WebSocket cannot set custom handshake headers. Use query params, cookies, or Sec-WebSocket-Protocol for auth.
- If proxies/CDN block upgrade, enable WebSocket pass-through (Upgrade/Connection) on Nginx/gateway.
Was this tool helpful?
Your feedback helps us decide which tools to improve first.
If you can, tell us the main reason:
Common use cases
- Use this page when you need to confirm that a WebSocket service will connect at all and whether a sent message actually gets a reply.
- It is useful for `ws://` and `wss://` troubleshooting, subprotocol checks, and browser-side connection failures where visual send and receive logs save time.
- When working with backend teammates on subscriptions, push events, or chat-style flows, sending plain text from the browser is often faster than writing temporary client code.