Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 10:57:24 UTC

Connection and verification

Protocol
Trojan
Address
45.205.0.6:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
51.159.148.230
Last verified handshake
386 ms
Last verified HTTPS first byte
569 ms
Download speed
7.244 Mbps
Source
Iran Intranet Access verified configs
First recorded check
2026-09-17 17:58:51 UTC
Recorded tunnel checks
14
Successful tunnel checks
7
Recorded tunnel success rate
50.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)
3860 09-20 02:2410-08 10:57Check time (UTC)
HTTPS first byte (ms)
5690 09-20 02:2410-08 10:57Check time (UTC)

Check history

Latest 14 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 ok386 ms569 ms51.159.148.230
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok350 ms546 ms51.159.148.230
TimeoutNot measuredNot measuredNot verified
Tunnel ok350 ms537 ms51.159.162.83
Tunnel ok362 ms555 ms51.159.162.83
Tunnel ok355 ms540 ms51.159.162.83
Tunnel ok368 ms564 ms51.159.162.83
Tunnel ok355 ms542 ms51.159.162.83
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.