Live checked VMess servers
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 |
|---|---|---|---|---|---|---|
WEBSOCKETNONE |
132.145.80.230South Korea |
Speed2 MbpsHandshake954 msHTTPS1464 ms |
62.5% successful 5/8 checks · last 7d | Au1rxx verified downloadable configs | Download | |
WEBSOCKETNONE |
145.239.55.210France |
Speed1 MbpsHandshake3757 msHTTPS4118 ms |
100% successful 6/6 checks · last 7d | 0xRadikal verified downloadable configs | Download | |
WEBSOCKETTLS |
47.239.203.111Hong Kong SAR China |
Speed2 MbpsHandshake2369 msHTTPS2927 ms |
50% successful 4/8 checks · last 7d | Matin VMess | 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.