Connection Control
disconnectedCommon Close Codes
| Code | Description |
|---|---|
| 1000 | Normal Closure |
| 1001 | Going Away (Browser navigating away or refresh) |
| 1002 | Protocol Error |
| 1003 | Unsupported Data |
| 1005 | No Status Received (Expected but missing) |
| 1006 | Abnormal Closure (Connection drop, no close frame) |
| 1009 | Message Too Big |
| 1011 | Internal Server Error |
About This Tool
The WebSocket Close Frame Inspector lets you inspect close frames in real time — showing the close code, reason string, and clean/unclean shutdown status whenever a connection terminates. It's built for debugging unexpected disconnects in production environments.
Connect to any endpoint, then trigger a close from either side. The inspector shows you the exact code and reason the server or browser reported, mapped against a reference table of standard WebSocket close codes so you can quickly understand what happened.
How to Use This Tool
Enter a WebSocket URL
Point it at the wss:// or ws:// endpoint you want to inspect.
Click "Connect"
Establish the connection, then trigger a disconnect from the client or server side.
Inspect the close frame
See the exact close code, reason string, and whether the shutdown was clean.
Common Use Cases
Diagnosing Silent Disconnects: Identify exactly why a connection was terminated instead of guessing from symptoms alone.
Distinguishing Client vs. Server Closures: See whether a disconnect originated from your own client or from the server.
Understanding Abnormal Shutdowns: Tell the difference between a clean close and an abrupt, unclean connection drop.
Debugging Real-Time App Reliability: Use close code patterns to track down recurring disconnect issues in chat or dashboard apps.
Why Use This Tool
Full Close Code Reference
Includes RFC 6455 descriptions for every standard WebSocket close code.
Live Activity Log
See every connection event timestamped as it happens.
Instant Code Lookup
The reference table highlights the exact code your connection just closed with.