Trojan server 185.114.72.31:2053
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Inactive — did not pass verificationLast result: 2026-09-09 23:16:36 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
- 185.114.72.31:2053
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.158.99.112
- Last verified handshake
- 634 ms
- Last verified HTTPS first byte
- 864 ms
- Download speed
- 4.245 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-04 07:14:16 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
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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 634 ms | 864 ms | 51.158.99.112 | |
| Tunnel ok | 1,936 ms | 2,299 ms | 51.158.99.112 |
No recorded checks match this filter.
How to use this Trojan configuration
- Download the current configuration while a fresh verification is available.
- Import it into a Trojan-compatible client, preserving all required transport, security and authentication parameters.
- 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.