Live checked VLESS servers

Recently verified VLESS endpoints

Checks expire from this list after three days. UUIDs, subscription URIs and REALITY keys are not embedded in the table or snapshot; an allowlisted URI is fetched only when its download button is used. A successful technical check is not an endorsement of the endpoint operator.

Showing up to 50 matching endpoints per page. Use the next page for more results with the same filters, or retrieve the full list from the JSON API.

VLESS JSON API

Use /api/v1/servers?protocol=vless&status=online to retrieve the same fresh downloadable VLESS rows without scraping this page. API records include stable public IDs, transport and security metadata, the verified exit IP, tunnel timings and the current config download URL.

Read the VLESS API guide or open the complete API v1 documentation.

How downloads work

New to the protocol? Read what VLESS is and how TLS, REALITY, UUIDs and transports fit together before importing a public configuration.

The site does not store UUIDs in its public snapshot. When you request a URI for a recently verified endpoint, the download endpoint retrieves the allowlisted public source over verified HTTPS, matches its sanitized endpoint fingerprint and returns only the current VLESS URI. Downloads stop automatically when the tunnel check expires or the source removes the configuration.

A source can rotate a public UUID after a check without changing the host and transport. If that happens, the current URI may stop working until the next checker pass; the table never treats the download itself as fresh tunnel evidence.

Public endpoints can log traffic or change behavior without notice. Do not use unknown community infrastructure for banking, work accounts, private source code or other sensitive activity. See public VPN risks.