Skip to main content
Inactive — did not pass verificationLast result: 2026-10-22 17:28:39 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Trojan server.

Connection and verification

Protocol
Trojan
Address
31.57.190.89:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.158.182.140
Last verified handshake
844 ms
Last verified HTTPS first byte
1,114 ms
Download speed
4.861 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-10-10 09:53:10 UTC
Recorded tunnel checks
11
Successful tunnel checks
9
Recorded tunnel success rate
81.8%

Handshake is tunnel setup time; HTTPS first byte includes the request through that tunnel. Neither is an ICMP ping or a bandwidth measurement. The success rate covers stored full-tunnel attempts only; it is not continuous uptime.

Performance history

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
12590 10-10 09:5310-22 17:28Check time (UTC)
HTTPS first byte (ms)
15970 10-10 09:5310-22 17:28Check time (UTC)

Check history

Latest 11 stored checks, up to 100 per configuration. Checks belong to this configuration’s stable public ID; different configurations on the same host have separate histories. Preflight and policy results do not count as successful tunnels.

Recorded Trojan checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok844 ms1,114 ms51.158.182.140
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok665 ms921 ms51.158.182.140
Tunnel ok591 ms869 ms51.158.182.140
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok677 ms960 ms51.158.182.140
Tunnel ok801 ms1,113 ms51.158.182.140
Tunnel ok686 ms937 ms51.158.182.140
Tunnel ok618 ms841 ms51.158.182.140
Tunnel ok739 ms1,025 ms51.158.182.140
Tunnel ok1,259 ms1,597 ms51.158.182.140

How to use this Trojan configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a Trojan-compatible client, preserving all required transport, security and authentication parameters.
  3. Connect and verify your connection with the IP tool and VPN leak test.

If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.

What does a successful check prove?

The external checker completed a Trojan tunnel, carried an HTTPS request and verified a changed public exit IP. This measures technical availability at that time, not the operator’s trustworthiness or performance from your network.

Read the Trojan guide, our checking methodology and public VPN risks.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.