Server-side checkTCP + TLSOne by oneWaiting
What it can answer
Useful for filtering nodes with closed ports, timeouts, refused connections, or obvious TLS issues.
It is not a real speed test
The value shown here is server-to-target TCP connect time, not proxy download speed.
It does not prove final usability
It does not fully validate vmess, vless, trojan, or ss auth, transport parameters, or outbound access.
Instructions：Node Connectivity Check
Notes
- Accepts
vmess://,vless://,trojan://, andss://nodes, plus common Base64 subscription bodies. - Nodes are parsed with
@changfengoss/v2rayse-helper, then sent to the server one by one for TCP connectivity checks and TLS handshake checks. - The current results are useful for answering:
- whether the target port is reachable
- whether server-to-entry TCP connects time out, get refused, or look unstable
- whether TLS handshake succeeds and whether certificate issuer or expiry looks suspicious
- The current results do not directly answer:
- the node’s real download speed or final throughput
- whether it behaves the same from your local network
- whether
vmess / vless / trojan / sscan complete full protocol validation - whether
ws / grpc / reality / auth / outbound accessall work correctly
- Treat it as an entry health-check tool, not a final speed test or final usability validator.
- All checks run server-side; the browser never connects to target nodes directly.
Comments
0 comments
Up to 3 images, 5MB each
Log in to comment, like, and reply.