What is HTTP/3? QUIC, UDP and how browsers find it

By TechCompare · Updated · How we check

HTTP/3 is HTTP over QUIC, which runs on UDP port 443 and always uses TLS 1.3. A browser only tries it after the site advertises it, so a site needs both the advertisement and a server that really answers QUIC.

HTTP/3 is the third major version of HTTP, published as RFC 9114 in 2022. It keeps the same requests, headers and status codes, but it sends them over QUIC, a transport built on UDP, instead of TCP. QUIC brings its own encryption based on TLS 1.3, so the connection and its security get set up in one step.

Topic
HTTP/3 and QUIC
HTTP/3 and QUIC
Category
HTTP versions
HTTP/2, HTTP/3 and QUIC

How this is calculated

With HTTP/1.1 and HTTP/2, a browser opens a TCP connection and then runs a TLS handshake on top of it. QUIC (RFC 9000) folds both into one exchange, so a new connection is ready after one round trip, and a returning visitor can send data right away with 0-RTT. QUIC also gives each request its own stream. When a packet goes missing, only the stream it belonged to waits. Over TCP, every request on the connection waits until the lost packet arrives again.

Browsers don't try HTTP/3 out of the blue. The first visit usually goes over TCP, and the server answers with an Alt-Svc header like h3=":443". The browser remembers that and uses QUIC the next time. A DNS HTTPS record (RFC 9460) with h3 in its alpn list lets a browser that reads it skip that first TCP visit.

Advertising HTTP/3 isn't the same as serving it. A firewall that drops UDP, a load balancer that only passes TCP or a server built without QUIC all leave the header in place while every QUIC attempt fails. Browsers notice and quietly fall back to TCP. The site still loads and nobody sees an error, which is how the problem goes unnoticed for months.

The SSL Checker looks at both sides. It reads Alt-Svc from the site's answer and the HTTPS record from DNS, then opens a real QUIC connection to port 443 and reports whether the handshake worked.

Verdict

Turn HTTP/3 on at your CDN or server, open UDP port 443 in every firewall in front of it, and send the Alt-Svc header. Then check the site. Advertised but not working means something on the path drops UDP or the server can't finish a QUIC handshake, and browsers will keep using HTTP/2.

More SSL scenarios

Frequently asked questions

Is HTTP/3 faster than HTTP/2?
Often on slow or lossy networks, like mobile data, where QUIC's quicker setup and per-stream loss recovery help most. On a fast, clean wired connection the difference is small. HTTP/3 doesn't change what a page loads, so a heavy page stays heavy.
Does HTTP/3 need a different certificate?
No. QUIC uses the same certificate as HTTPS over TCP. It does need TLS 1.3, which QUIC builds in, so the server's QUIC stack has to support it even if its TCP setup still allows TLS 1.2.
Why does my browser still use HTTP/2 on a site with HTTP/3?
The first visit usually goes over TCP, since the browser hasn't seen the Alt-Svc header yet. After that, a network that blocks UDP or a failed QUIC attempt can keep it on HTTP/2. Reload the page and look at the protocol column in the browser's network tools.