VMess server yg1.ygkkk.dpdns.org:443
WEBSOCKET / TLS · 0xRadikal verified downloadable configs
Inactive — did not pass verificationLast result: 2026-10-20 00:03: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
- yg1.ygkkk.dpdns.org:443
- Transport / security
- WEBSOCKET / TLS
- Last verified exit IP
- 47.239.203.111
- Last verified handshake
- 2,353 ms
- Last verified HTTPS first byte
- 2,868 ms
- Download speed
- 2.967 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-10-01 01:22:53 UTC
- Recorded tunnel checks
- 19
- Successful tunnel checks
- 18
- Recorded tunnel success rate
- 94.7%
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.
Check history
Latest 20 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 2,353 ms | 2,868 ms | 47.239.203.111 | |
| Tunnel ok | 1,675 ms | 2,187 ms | 47.239.203.111 | |
| Tunnel ok | 1,524 ms | 2,062 ms | 47.239.203.111 | |
| Tunnel ok | 1,552 ms | 2,084 ms | 47.239.203.111 | |
| Tunnel ok | 1,940 ms | 2,464 ms | 47.239.203.111 | |
| Tunnel ok | 1,911 ms | 2,426 ms | 47.239.203.111 | |
| Tunnel ok | 3,138 ms | 3,652 ms | 47.239.203.111 | |
| Tunnel ok | 2,167 ms | 2,692 ms | 47.239.203.111 | |
| Tunnel ok | 2,307 ms | 2,877 ms | 47.239.203.111 | |
| Tunnel ok | 2,032 ms | 2,550 ms | 47.239.203.111 | |
| Timeout | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,693 ms | 2,249 ms | 47.239.203.111 | |
| Policy blocked | Not measured | Not measured | Not verified | |
| Tunnel ok | 2,247 ms | 2,812 ms | 47.239.203.111 | |
| Tunnel ok | 2,436 ms | 3,057 ms | 47.239.203.111 | |
| Tunnel ok | 2,264 ms | 2,820 ms | 47.239.203.111 | |
| Tunnel ok | 2,065 ms | 2,581 ms | 47.239.203.111 | |
| Tunnel ok | 2,595 ms | 3,166 ms | 47.239.203.111 | |
| Tunnel ok | 2,032 ms | 2,993 ms | 47.239.203.111 | |
| Tunnel ok | 1,682 ms | 2,187 ms | 47.239.203.111 |
No recorded checks match this filter.
How to use this VMess configuration
- Download the current configuration while a fresh verification is available.
- Import it into a VMess-compatible client, preserving all required transport, security and authentication parameters.
- 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.