Trojan server 172.67.231.254:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-22 17:04:01 UTC
Connection and verification
- Protocol
- Trojan
- Address
- 172.67.231.254:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 51.159.148.230
- Last verified handshake
- 391 ms
- Last verified HTTPS first byte
- 597 ms
- Download speed
- 7.133 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-10-09 10:07:50 UTC
- Recorded tunnel checks
- 12
- Successful tunnel checks
- 8
- Recorded tunnel success rate
- 66.7%
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 12 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 | 391 ms | 597 ms | 51.159.148.230 | |
| Tunnel ok | 358 ms | 545 ms | 51.159.167.67 | |
| Tunnel ok | 374 ms | 563 ms | 51.159.167.67 | |
| Tunnel ok | 326 ms | 598 ms | 51.159.148.230 | |
| Tunnel ok | 390 ms | 578 ms | 51.159.148.230 | |
| Tunnel ok | 406 ms | 619 ms | 51.159.148.230 | |
| Tunnel ok | 355 ms | 539 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 382 ms | 579 ms | 51.159.148.230 | |
| Timeout | Not measured | Not measured | Not verified | |
| Timeout | 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.