Node Connectivity Check

Workflow

Paste URI, Base64, Clash YAML or sing-box JSON, explicitly parse and select up to 20 nodes. Review endpoints and settings before checking them one at a time. Stop at any time; there are no automatic retries.

Reading results

TCP success only means the server established a port connection. Latency is measured from this site server, not your device. TLS success requires a trusted chain and matching server name. No TLS, failed TCP and unsupported handshakes are distinguished. UDP protocols are skipped; Reality receives a TCP check only.

No proxy passwords or UUIDs are used. This does not verify proxy authentication, forwarding, throughput or client runtime, and is not publication evidence for free nodes.

Privacy and limits

Original input stays in page memory. Only explicitly selected endpoints, ports, TLS and SNI are sent for checks; passwords, UUIDs, transport paths and complete configurations are never sent. Results are not stored in the database. Account/language changes and leaving clear the workspace.

Up to 256 Ki input characters, 1 MiB per local file, 100 candidates and 20 selected nodes per run; one target per request. DNS has a 3-second deadline, TCP/TLS each 1–10 seconds. Only public IPs or domains with entirely public DNS results are admitted, pinned for both connections. Real transport is disabled in ordinary development; deployments must explicitly enable it and configure a shared ingress limit.