Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 19:52:50 UTC

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

Connection and verification

Protocol
VMess
Address
168.138.43.75:80
Transport / security
WEBSOCKET / NONE
Last verified exit IP
168.138.43.75
Last verified handshake
1,032 ms
Last verified HTTPS first byte
1,556 ms
Download speed
1.255 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 17:27:57 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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)
10930 2026-09-04 17:27:57 UTC: 1,093 ms2026-09-07 22:11:54 UTC: 1,078 ms2026-09-09 19:52:50 UTC: 1,032 ms09-04 17:2709-09 19:52Check time (UTC)
HTTPS first byte (ms)
16230 2026-09-04 17:27:57 UTC: 1,623 ms2026-09-07 22:11:54 UTC: 1,589 ms2026-09-09 19:52:50 UTC: 1,556 ms09-04 17:2709-09 19:52Check time (UTC)

Check history

Latest 3 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 VMess checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok1,032 ms1,556 ms168.138.43.75
Tunnel ok1,078 ms1,589 ms168.138.43.75
Tunnel ok1,093 ms1,623 ms168.138.43.75

How to use this VMess configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VMess-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 VMess 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 VMess guide, our checking methodology and public VPN risks.