Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 17:08:03 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
www.nextkyc.com:8443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
207.244.230.92
Last verified handshake
10,040 ms
Last verified HTTPS first byte
10,556 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 22:53:05 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)
100400 2026-09-04 22:53:05 UTC: 2,187 ms2026-09-07 22:59:47 UTC: 4,347 ms2026-09-10 16:53:35 UTC: 10,040 ms09-04 22:5309-10 16:53Check time (UTC)
HTTPS first byte (ms)
105560 2026-09-04 22:53:05 UTC: 2,660 ms2026-09-07 22:59:47 UTC: 5,227 ms2026-09-10 16:53:35 UTC: 10,556 ms09-04 22:5309-10 16:53Check 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 VMess checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Policy blockedNot measuredNot measuredNot verified
Tunnel ok10,040 ms10,556 ms207.244.230.92
Policy blockedNot measuredNot measuredNot verified
Tunnel ok4,347 ms5,227 ms207.244.230.92
Tunnel ok2,187 ms2,660 ms207.244.230.92

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.