Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 09:36:16 UTC

Connection and verification

Protocol
VMess
Address
yg1.ygkkk.dpdns.org:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
47.239.203.111
Last verified handshake
2,369 ms
Last verified HTTPS first byte
2,927 ms
Download speed
2.97 Mbps
Source
Matin VMess
First recorded check
2026-10-01 17:09:02 UTC
Recorded tunnel checks
9
Successful tunnel checks
4
Recorded tunnel success rate
44.4%

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)
32250 10-06 12:2010-09 09:36Check time (UTC)
HTTPS first byte (ms)
43530 10-06 12:2010-09 09:36Check time (UTC)

Check history

Latest 9 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 ok2,369 ms2,927 ms47.239.203.111
Tunnel ok2,176 ms2,729 ms47.239.203.111
Tunnel ok3,225 ms4,353 ms47.239.203.111
Tunnel ok2,515 ms3,080 ms47.239.203.111
Tunnel failedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.