Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 03:45:44 UTC

Connection and verification

Protocol
VLESS
Address
185.253.96.117:443
Transport / security
TCP / REALITY
Last verified exit IP
185.253.96.117
Last verified handshake
384 ms
Last verified HTTPS first byte
582 ms
Download speed
5.706 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-10-02 10:45:01 UTC
Recorded tunnel checks
8
Successful tunnel checks
8
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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
8580 10-02 10:4510-09 03:45Check time (UTC)
HTTPS first byte (ms)
11540 10-02 10:4510-09 03:45Check time (UTC)

Check history

Latest 8 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 VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok384 ms582 ms185.253.96.117
Tunnel ok387 ms589 ms185.253.96.117
Tunnel ok368 ms561 ms185.253.96.117
Tunnel ok411 ms601 ms185.253.96.117
Tunnel ok359 ms557 ms185.253.96.117
Tunnel ok858 ms1,154 ms185.253.96.117
Tunnel ok495 ms734 ms185.253.96.117
Tunnel ok413 ms619 ms185.253.96.117

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-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 VLESS 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 VLESS 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.