Live checked VMess servers — Page 4
Fresh VMess proxy endpoints verified through a complete tunnel, HTTPS request and changed public exit IP.
Fresh VMess proxy endpoints verified through a complete tunnel, HTTPS request and changed public exit IP.
Each source catalog applies its freshness and publication checks. A row requires a real protocol tunnel, successful HTTPS traffic and a public exit IP different from the checker’s direct IP. Reachable ports and source-reported status are excluded.
| Endpoint | Connection | Exit IP / country | Performance | Checked / stability | Source | Config |
|---|---|---|---|---|---|---|
TCPNONE |
129.146.143.80United States |
Speed3 MbpsHandshake503 msHTTPS819 ms |
66.7% successful 2/3 checks · last 7d · small sample | VestraNet VMess candidates | Download | |
WEBSOCKETNONE |
172.111.146.64Japan |
Speed—Handshake1152 msHTTPS1694 ms |
50% successful 1/2 checks · last 7d · small sample | Freedom V2Ray tested configs | Download | |
TCPNONE |
143.20.38.57Japan |
Speed5 MbpsHandshake785 msHTTPS1160 ms |
100% successful 1/1 checks · last 7d · small sample | v2go hourly full-tunnel tested configs | Download | |
WEBSOCKETTLS |
47.243.65.243Hong Kong SAR China |
Speed—Handshake2214 msHTTPS2672 ms |
100% successful 1/1 checks · last 7d · small sample | Proxy-Hunter tested candidates | Download | |
TCPNONE |
81.168.109.165Hong Kong SAR China |
Speed5 MbpsHandshake366 msHTTPS730 ms |
100% successful 1/1 checks · last 7d · small sample | v2go hourly full-tunnel tested configs | Download | |
TCPNONE |
143.20.38.61Japan |
Speed5 MbpsHandshake1331 msHTTPS1691 ms |
7d history unavailable | VestraNet VMess candidates | Download |
Use /api/v1/servers?protocol=vmess&status=online to retrieve the same fresh, downloadable and full-tunnel-verified rows without scraping this table. The response includes stable public IDs, transport metadata, the observed exit IP, checker timings and the current config download URL.
Open the VMess API guide or read the complete API v1 documentation.
A VMess client authenticates with a UUID and carries proxy requests over the configured transport. Deployments may add TLS and use TCP, WebSocket or gRPC. Every layer must match the server. Client and server clocks also need to be reasonably accurate for compatible authentication behavior.
VMess connection details are transport-specific; the client must preserve TLS, host, path and transport settings.
Connection material is quarantined and never printed in tables or logs. A download is returned only for a fresh full-tunnel result whose exact URI is still present in an allowlisted public source permitted by the publication policy.
Unknown public infrastructure may observe or manipulate traffic. Do not use community endpoints for banking, work accounts, private source code or other sensitive activity. Read the public endpoint risk guide.
Read the complete VMess protocol, configuration and troubleshooting guide.