Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:55:45 UTC

Connection and verification

Protocol
Trojan
Address
www.hcaptcha.com:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.158.239.186
Last verified handshake
1,319 ms
Last verified HTTPS first byte
1,595 ms
Download speed
1.319 Mbps
Source
Iran Intranet Access verified configs
First recorded check
2026-10-05 10:54:39 UTC
Recorded tunnel checks
5
Successful tunnel checks
4
Recorded tunnel success rate
80.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.

Tunnel handshake (ms)
18700 10-05 10:5410-09 06:55Check time (UTC)
HTTPS first byte (ms)
28160 10-05 10:5410-09 06:55Check time (UTC)

Check history

Latest 5 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 ok1,319 ms1,595 ms51.158.239.186
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok385 ms566 ms51.158.239.186
Tunnel ok1,870 ms2,121 ms51.158.239.186
Tunnel ok1,825 ms2,816 ms51.158.239.186

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.