Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 10:39:43 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
mtckundigepwu3up.v.3dns.vip:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
47.243.92.155
Last verified handshake
3,591 ms
Last verified HTTPS first byte
4,111 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-07 00:52:32 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)
35910 2026-09-07 00:52:32 UTC: 1,939 ms2026-09-10 01:07:54 UTC: 2,647 ms2026-09-11 10:39:43 UTC: 3,591 ms09-07 00:5209-11 10:39Check time (UTC)
HTTPS first byte (ms)
41110 2026-09-07 00:52:32 UTC: 2,457 ms2026-09-10 01:07:54 UTC: 3,497 ms2026-09-11 10:39:43 UTC: 4,111 ms09-07 00:5209-11 10:39Check 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 ok3,591 ms4,111 ms47.243.92.155
Tunnel ok2,647 ms3,497 ms47.243.92.155
Tunnel ok1,939 ms2,457 ms47.243.92.155

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.