Skip to main content
Inactive — did not pass verificationLast result: 2026-09-06 06:38:31 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Trojan server.

Connection and verification

Protocol
Trojan
Address
hu2.vpnjantit.com:4443
Transport / security
TCP / TLS
Last verified exit IP
46.29.142.57
Last verified handshake
468 ms
Last verified HTTPS first byte
662 ms
Download speed
Not measured
Source
Anonymous tested configs
First recorded check
2026-09-06 06:22:23 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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

Tunnel handshake (ms)
4680 2026-09-06 06:22:23 UTC: 318 ms2026-09-06 06:38:31 UTC: 468 ms09-06 06:2209-06 06:38Check time (UTC)
HTTPS first byte (ms)
6620 2026-09-06 06:22:23 UTC: 584 ms2026-09-06 06:38:31 UTC: 662 ms09-06 06:2209-06 06:38Check time (UTC)

Check history

Latest 2 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 ok468 ms662 ms46.29.142.57
Tunnel ok318 ms584 ms46.29.142.57

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.