Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 14:24:41 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
188.42.145.180:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.158.236.235
Last verified handshake
3,096 ms
Last verified HTTPS first byte
3,364 ms
Download speed
3.14 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-08 22:52:31 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
Recorded tunnel success rate
100.0%

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

Tunnel handshake (ms)
30960 2026-09-08 22:52:31 UTC: 377 ms2026-09-09 14:24:41 UTC: 3,096 ms09-08 22:5209-09 14:24Check time (UTC)
HTTPS first byte (ms)
33640 2026-09-08 22:52:31 UTC: 586 ms2026-09-09 14:24:41 UTC: 3,364 ms09-08 22:5209-09 14:24Check time (UTC)

Check history

Latest 2 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 ok3,096 ms3,364 ms51.158.236.235
Tunnel ok377 ms586 ms51.158.236.235

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.