Trojan server 104.18.37.127:443
WEBSOCKET / TLS · Iran Intranet Access verified configs
WEBSOCKET / TLS · Iran Intranet Access verified configs
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.
Hover or focus a point for check details. Click or tap to keep them open.
Latest 8 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 | 614 ms | 847 ms | 51.158.239.186 | |
| Tunnel ok | 1,845 ms | 2,196 ms | 51.158.239.186 | |
| Tunnel ok | 591 ms | 835 ms | 51.158.239.186 | |
| Tunnel ok | 1,734 ms | 2,112 ms | 51.158.239.186 | |
| Tunnel ok | 1,335 ms | 1,901 ms | 51.158.239.186 | |
| Tunnel ok | 471 ms | 749 ms | 51.158.239.186 | |
| Tunnel ok | 2,808 ms | 3,082 ms | 51.158.239.186 | |
| Tunnel failed | Not measured | Not measured | Not verified |
No recorded checks match this filter.
If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.
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.