Try
BROWSER TOOLS QUIC uses todaySince 2026-11-07

QUIC / HTTP3 test

HTTP/3 runs on QUIC, and QUIC uses UDP. Many proxies relay TCP only: the browser then either falls back to HTTP/2 or lets QUIC’s UDP packets leave from your own network, so a site sees both the proxy exit and your original address. This page connects to a probe that accepts both TCP and QUIC to show which path the browser actually took and what its QUIC handshake carried.

This connection

Protocol
 
QUIC version
 
Key exchange
 
Round-trip time
 
  • Testing

    A browser first makes a TCP request, learns from the Alt-Svc reply that HTTP/3 is offered and then decides whether to switch to QUIC. Not observing HTTP/3 can come from browser policy, a proxy that does not relay UDP or a network that drops it; this alone does not prove UDP is blocked.

  • Testing

    System and browser proxies usually handle TCP only, so QUIC’s UDP packets leave from your own network and a site sees both the proxy exit and your original address. TUN mode and VPNs carry UDP as well. Exits are compared within one address family.

  • Testing

    QUIC uses TLS 1.3 only. 0-RTT lets a returning connection send a request before the handshake completes, which is faster but exposes early data to replay.

Connection attempts

The browser switches to QUIC only after the first reply’s Alt-Svc
#ProtocolPeer seen by the probeTime

QUIC handshake fingerprints

Computed from the ClientHello inside QUIC
JA4Sorted, then hashed; stable
 
JA4_rJA4 before hashing
 
JA4_oJA4 in offered order
 
JA4_roOffered order, before hashing
 

QUIC carries the TLS 1.3 handshake inside its own packets; a JA4 beginning with q marks that. A browser sends a different ClientHello over QUIC than over TCP, so these fingerprints differ from the TLS page. JA4 does not cover QUIC transport parameters, which are listed below.

QUIC transport parameters

ParameterValue

These are the limits the browser declared in the handshake. The library exposes parsed standard parameters only; private parameters and the original order are not included.

HTTP/3 SETTINGS

IDNameValue

Connection state

Measured on the probe side
Peer addressUDP exit of the QUIC connection
 
Smoothed RTT
 
Minimum RTT
 
Packets in / out
 
Cipher suite
 
0-RTTEarly data sent
 
Datagram extensionRFC 9221
 

Cipher suites and extensions

In offered order
#IDName
1
2
3
#IDName
1
2
3
#IDName
1
2
3
4
5
6

The top row shows cipher suites on the left and key exchange groups on the right; extensions follow. QUIC uses TLS 1.3 only, so there are just the three AEAD suites; the quic_transport_parameters extension is specific to QUIC.

How to use this tool

How this works

Check whether your browser can connect with HTTP/3 over QUIC, compare the UDP exit with the TCP exit, and see the QUIC handshake’s JA4 fingerprint, transport parameters, HTTP/3 SETTINGS and round-trip time.

Steps

  • The test runs when the page opens. Keep the proxy or VPN state you want to inspect.
  • Start with “This connection”: whether HTTP/3 was used and whether the UDP and TCP exits match.
  • When QUIC is used, handshake fingerprints, transport parameters and HTTP/3 SETTINGS are listed below.

What the result tells you

Not observing HTTP/3 does not mean UDP is blocked: browser policy or a proxy that does not relay UDP gives the same result.

The QUIC handshake fingerprint differs from the TLS fingerprint over TCP; the two cannot be compared directly.

This is not a speed test, and using HTTP/3 says nothing about connection speed.

Common questions4

What does a different UDP exit mean?

QUIC traffic did not go through the proxy. System and browser proxies usually handle TCP only; carrying UDP needs TUN mode or a VPN, or QUIC can be turned off in the browser.

Why are the first requests not HTTP/3?

A browser must first receive the server’s Alt-Svc announcement over TCP to learn that HTTP/3 is offered; only later requests may switch to QUIC. That is why the page sends several requests.

Does browsing suffer without HTTP/3?

No. Sites also support HTTP/2 and the browser falls back automatically.

How do I turn QUIC off in the browser?

In Chrome and Edge set Experimental QUIC protocol to Disabled in chrome://flags; in Firefox set network.http.http3.enable to false in about:config.

mimetic
mimetic
mimetic