Skip to main content

Protocol guide

What is TUIC? QUIC proxy configuration and safety

TUIC is a proxy protocol that carries TCP and UDP traffic through QUIC. A publishable profile needs complete credentials and TLS settings; a hostname and UDP port by themselves cannot be downloaded as a working configuration.

Checked TUIC servers Compare all protocols Verification method
Fiber optic connections in network hardware illustrating TUIC traffic routing

Quick facts

UDP with QUIC and TLSTransport
UUID and passwordAuthentication
tuic:// linkConfiguration

TUIC in plain English

A TUIC client opens a TLS-protected QUIC connection, authenticates, and multiplexes proxy traffic through that connection. Current clients and servers need compatible protocol versions and congestion-control settings. Full-device routing is supplied by the client, not by the share-link format alone.

Important: encryption protects traffic between the client and endpoint, but it does not make an unknown public operator trustworthy.

How TUIC works

  1. The client reaches the configured UDP endpoint.
  2. QUIC performs its transport and TLS handshake.
  3. The server validates the UUID and password.
  4. TCP streams and UDP packets are relayed through the authenticated connection.

Configuration fields that must be complete

FieldWhy it matters
Server and UDP portQUIC endpoint.
UUID and passwordRequired authentication pair.
SNI and certificateTLS server identity settings.
Version and congestion controlClient options that must be compatible with the server.

PublicVPNList publishes a download only when the exact configuration is still present in an allowed, publication-compatible source and its fresh full-tunnel check succeeds.

Strengths

  • Multiplexes TCP and UDP traffic over QUIC.
  • TLS is integrated into the QUIC connection.
  • Can support a full-device route in clients with TUN mode.

Limits and risks

  • UDP filtering stops the protocol before authentication.
  • Profiles from incompatible TUIC versions may not connect.
  • There are fewer complete publishable public profiles than bare endpoint lists.

Safe setup and verification

  1. Use a maintained client that explicitly supports TUIC.
  2. Inspect the server, transport, identity and authentication fields before importing.
  3. Keep certificate and server-identity validation enabled where the protocol supports it.
  4. Connect without opening sensitive accounts, then verify the visible IP and DNS path.
  5. Disconnect and remove stale public profiles after low-risk testing.
Check public IPRead public VPN risks

Common connection problems

  • Use a client that supports the profile protocol version.
  • Verify UUID, password, SNI and certificate settings.
  • Check that the network permits UDP to the selected port.
  • Confirm the public exit IP changes after connection.

A client “connected” indicator is not enough. A valid test must send real HTTPS traffic through the protocol and confirm that the public exit IP changed.

Official technical reference

For field semantics and protocol behavior, consult the TUIC protocol project. PublicVPNList adds operational testing and publication policy; it does not replace the specification.

Related protocol guides

Frequently asked questions

Is TUIC a VPN?
TUIC is primarily a proxy protocol. It becomes a full-device path only when a compatible client routes all traffic through a TUN or VPN interface.
What does a usable TUIC profile need?
It needs all endpoint, authentication, transport and security fields required by the server. A hostname and open port alone are not a downloadable working configuration.
How does PublicVPNList verify TUIC endpoints?
The checker starts the real protocol client in an isolated VM, sends HTTPS through the tunnel and requires the observed public exit IP to differ from the direct checker IP.
Is a checked public endpoint safe for sensitive accounts?
No technical connectivity test can verify the operator, logging policy or jurisdiction. Avoid banking, private work and identity-sensitive sessions on unknown public infrastructure.

Page history

  • 2026-08-31 — Published the protocol overview, configuration requirements, troubleshooting guidance, safety notes and PublicVPNList verification policy.