Full-device VPNs and proxy/tunnel protocols solve different routing problems. Every live row must pass a protocol-specific full tunnel, HTTPS request and changed exit-IP check; port reachability is never counted as a working VPN.
UDP or TCP VPN tunnel
Mature full-device VPN with broad client and router support; current catalog rows include downloadable .ovpn profiles.
UDP VPN tunnel
A relay hostname and port are not a usable WireGuard profile. A publishable client key, peer key and allowed-IP configuration are required.
Gate: 0/14 qualifying days · zero usable rows seven days
IKEv2/IPsec
IKEv2 requires credentials or certificates and a separate strongSwan checker; an open UDP port is not proof of a working VPN.
Gate: 0/14 qualifying days · zero usable rows seven days
TCP, WebSocket, gRPC or XHTTP with TLS/REALITY
Proxy tunnel protocol whose transport and TLS/REALITY settings must be preserved by a compatible client.
Gate: 14/14 qualifying days · indexable
TCP with TLS
Use a current client that supports Trojan over TLS and verify the SNI before importing any public configuration.
Gate: 15/14 qualifying days · indexable
TCP, WebSocket or gRPC
VMess connection details are transport-specific; the client must preserve TLS, host, path and transport settings.
Gate: 14/14 qualifying days · indexable
Encrypted TCP/UDP proxy
Outline access keys use the Shadowsocks protocol family, so Outline is covered here instead of being counted as a separate tunnel protocol.
Gate: 14/14 qualifying days · indexable
UDP/QUIC
Hysteria2 requires UDP reachability and valid TLS parameters; a TCP port probe cannot verify it.
Gate: 13/14 qualifying days · indexable
UDP/QUIC
TUIC requires a complete UUID/password pair and UDP-capable checking; incomplete metadata is never listed as working.
Gate: 0/14 qualifying days · insufficient qualified history
A protocol catalog can be indexed only after it has at least 10 unique verified endpoints from 3 independent sources on 7 days within the last 14. Seven consecutive zero-result days force noindex,follow and sitemap removal; a documented outage can retain eligibility for at most 72 hours.
Endpoint counts, configuration counts and stored quarantine records are shown separately. Handshake and HTTPS first-byte values are milliseconds measured by checker infrastructure. Survival is a percentage over the stated window and is not shown until enough history exists.