{ "v": "2", "ps": "JP Tokyo 01 | VMess WS", "add": "jp-01.edge.demo.example", "port": "443", "id": "ee4f5c6b-1cdf-4f20-b1fb-7416363e3f61", "aid": "0", "scy": "auto", "net": "ws", "type": "none", "host": "jp-01.edge.demo.example", "path": "/ray", "tls": "tls", "sni": "jp-01.edge.demo.example" }
Node Inspector
Inspect a single node, multi-node input, or Base64 subscription content with structured views for protocol, TLS, transport, identity fields, and raw payload details.
1 · Add node content
Paste nodes or a configuration, then analyze. Start with the example if you are unsure.
Import a UTF-8 text file, up to 1 MiB. Its content is not uploaded.
Local analysis; content is not uploaded
Paste or import share links, Base64, Clash YAML or sing-box JSON to explore nodes, distributions and connection configuration. Advanced fields start collapsed. Analysis performs no network checks.
Notes
- Accepts
vmess://,vless://,trojan://, andss://nodes, plus common Base64 subscription bodies. - The page parses nodes with
@changfengoss/v2rayse-helperand does not write the analysis to your database. - Useful before conversion when you need to verify:
- whether the endpoint is correct
- whether TLS / SNI is complete
- whether WebSocket / gRPC transport fields are present
- which raw parameters the helper actually extracted
- With multi-node input, you can switch one node at a time and inspect both the structure canvas and the field panels.
Discussion 2
Ask a question or share something useful for the next reader.
Sign in to comment, reply and vote.
Sign in to join{ "v": "2", "ps": "JP Tokyo 01 | VMess WS", "add": "jp-01.edge.demo.example", "port": "443", "id": "ee4f5c6b-1cdf-4f20-b1fb-7416363e3f61", "aid": "0", "scy": "auto", "net": "ws", "type": "none", "host": "jp-01.edge.demo.example", "path": "/ray", "tls": "tls", "sni": "jp-01.edge.demo.example" }