SOCKS5 QUIC support checker

QUIC (HTTP/3) runs over UDP, so it only works through a SOCKS5 proxy that actually relays UDP. Paste your proxy below and the tool sends a real QUIC packet through it to a QUIC server and waits for the reply.

Free, anonymous, takes about 5 seconds.

QUIC / HTTP-3 check

SOCKS5 proxies only

Format: IP:Port:User:Pass

Why this matters

QUIC is the transport behind HTTP/3. It is built on UDP, not TCP. A SOCKS5 proxy carries QUIC only if it implements the UDP ASSOCIATE command from RFC 1928 and actually relays the datagrams. Most "SOCKS5" providers skip UDP, so QUIC silently fails through them.

You only notice when a browser, a QUIC-based client or an HTTP/3 API stops responding through the proxy with no useful error.

What needs QUIC through a proxy

HTTP/3 browsing. Modern browsers prefer QUIC where the server offers it
Low-latency APIs. Services that expose HTTP/3 endpoints
Media and real-time. QUIC-based streaming and transport
Anti-blocking transports. Some tunnels use QUIC to blend with normal HTTP/3 traffic

This is a real QUIC round-trip, not a configuration check. The tool sends a QUIC Initial packet with an unsupported version through your proxy; a real QUIC server must answer with a Version Negotiation packet. If that reply comes back through the proxy, QUIC works.

What the result includes

Returned fields

Field Description
QUIC support Yes if the QUIC server's reply came back through the proxy. No with reason if it failed
Exit IP The IP address sites see when you connect through this proxy
Geo Country and city of the exit IP
Type Residential or Hosting (datacenter), based on ASN/org keywords
ISP The organization that owns the exit IP block

FAQ

Why "No" if my proxy works for browsing?

Plain browsing falls back to HTTP/1.1 or HTTP/2 over TCP. Your proxy supports TCP. QUIC is a separate UDP capability that most proxies do not relay.

Does it work for HTTP or HTTPS proxies?

No. UDP relay (and therefore QUIC) is a SOCKS5-only feature. HTTP and HTTPS proxies have no comparable mechanism.

How is this different from the UDP checker?

The UDP checker sends a DNS query over UDP. The QUIC checker sends a real QUIC packet and expects a QUIC-protocol reply, testing the exact path an HTTP/3 client would use.

Do you store my proxy credentials?

No. Credentials pass through the server in memory only. Nothing is logged.

Geekproxy SOCKS5 with UDP & QUIC

UDP ASSOCIATE works on every endpoint, so QUIC works too.

Get SOCKS5 proxies