Trojan server 172.67.217.240:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-22 17:16:44 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 172.67.217.240:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.159.148.230
- Last verified handshake
- 333 ms
- Last verified HTTPS first byte
- 518 ms
- Download speed
- 7.185 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-10-08 10:15:57 UTC
- Recorded tunnel checks
- 9
- Successful tunnel checks
- 9
- 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
Hover or focus a point for check details. Click or tap to keep them open.
Check history
Latest 13 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 | 333 ms | 518 ms | 51.159.148.230 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 364 ms | 546 ms | 51.159.167.67 | |
| Tunnel ok | 367 ms | 552 ms | 51.159.148.230 | |
| Tunnel ok | 344 ms | 523 ms | 51.159.148.230 | |
| Tunnel ok | 403 ms | 609 ms | 51.159.148.230 | |
| Tunnel ok | 1,422 ms | 1,622 ms | 51.159.148.230 | |
| Tunnel ok | 443 ms | 638 ms | 51.159.148.230 | |
| Tunnel ok | 373 ms | 556 ms | 51.159.148.230 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 341 ms | 523 ms | 51.159.148.230 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Policy blocked | Not measured | Not measured | Not verified |
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.