WebSocket Tester
Enter an endpoint and choose Connect. Nothing connects or uploads until you start it.
Only connect to services you trust. Messages go directly to the endpoint you entered after you choose Connect.
The target service controls its own authentication, origin policy, and server-side access rules. A browser connection succeeding here does not make that service safe or publicly reachable.
On an HTTPS page, browsers may block ws:// as mixed content. Use wss:// or an HTTP development page when your local service supports only ws://.
Idle — enter an endpoint to begin.
A QUICK WALKTHROUGH
How to use this tool
- Enter a ws:// or wss:// endpoint and connect deliberately.
- Send text messages and inspect open, message, error, and close events.
- Disconnect or clear the local event log when finished.
Only connect to services you trust. Messages go directly to the endpoint you entered after you choose Connect.
The target service controls its own authentication, origin policy, and server-side access rules. A browser connection succeeding here does not make that service safe or publicly reachable.
Browser note
On an HTTPS page, browsers may block ws:// as mixed content. Use wss:// or an HTTP development page when your local service supports only ws://.
Privacy
No automatic connection, upload, proxy, or telemetry is performed. Endpoint and log stay in this page memory until you leave or clear them.
GOOD TO KNOW
Common questions
Is this a WebSocket proxy or CORS bypass?
No. It connects directly from your browser after your action. WebSocket origin and server access behavior belong to the target service; they are not equivalent to ordinary fetch CORS rules.