Skip to main content

Multi-protocol VPN config validator

Paste one VLESS, VMess, Trojan, Shadowsocks, Hysteria2, TUIC or AnyTLS configuration. The browser recognizes share URIs, JSON and common YAML fields used by sing-box, Xray/V2Ray and Clash/Mihomo, then checks required connection and security parameters.

Validate a configuration locally

Processed locally. The configuration was not sent from this browser.

Live catalogs

Ready. Maximum input size: 256 KB.

Checks and supported formats

The parser validates host, port, UUID or password, transport, TLS, SNI, ALPN, REALITY public key, short ID and fingerprint, WebSocket path, gRPC service name and XHTTP compatibility. It flags disabled certificate verification, conflicting or missing values and unknown format-specific fields.

JSON support covers common sing-box and Xray/V2Ray outbound shapes; YAML support performs conservative structural checks for Clash/Mihomo-style proxy entries. A clean structural result does not prove that an endpoint works or that its operator is trustworthy.

Advertisement

Use the result

VLESS guideTrojan guideVMess guideShadowsocks guideHysteria2 guideTUIC guideAnyTLS guide

Only import public configurations for low-risk testing. Compare the parsed protocol and transport with a fresh live catalog row and keep certificate validation enabled.

Frequently asked questions

Is my UUID or password sent to PublicVPNList?
No. Parsing happens in browser memory. The page does not send the configuration, hostname, UUID, password or REALITY material to the backend or analytics.
Does this validator prove that a server works?
No. It checks configuration structure and known compatibility risks. Only a separate full-tunnel checker can verify connectivity.
Why are some YAML fields reported as unknown?
Clash, Mihomo, sing-box and Xray evolve independently. Unknown fields are informational and should be checked against the client version documentation.