Full-stack QUIC & HTTP/3 analysis โ post-quantum hybrid TLS, QUIC v1/v2, multipath, WebTransport, MASQUE, certificate chain & performance metrics
HTTP/3 with QUIC and WebTransport delivers faster page loads and mandatory TLS 1.3 encryption. Our scanner uses native QUIC libraries to extract real peer-advertised metadata, from transport parameters and HTTP/3 SETTINGS to certificate chains and post-quantum key exchange, and grades every site on a 5-tier scale (A++, A+, A, C, F). Curious how a scan actually works on the wire? Read Anatomy of a QUIC Connection, our whitepaper that replays one real scan packet by packet.
The scanner extracts detailed metadata including real peer-advertised QUIC transport parameters, HTTP/3 SETTINGS (QPACK, Extended CONNECT, datagrams), server implementation fingerprinting (identifying Cloudflare, Google GFE, Facebook mvfst, Fastly H2O, and more), connection metrics (handshake time, TTFB, RTT, GSO, probe timeouts), certificate chain analysis (OCSP stapling, Certificate Transparency, root CA), and TLS extension analysis. The 5-tier grading requires post-quantum hybrid key exchange for the top tier and produces intelligent per-scan recommendations.
Analysis target: by default, the exact hostname you enter — the analyzer grades that host's own response and does not follow redirects. If a site redirects (e.g. example.com → www.example.com, or to a different domain), HTTP/3 may live on the target, not the apex. Enable Follow redirects — the checkbox above — to instead analyze the final destination; the result clearly shows which host was actually analyzed.
Try these examples:
?url=pqcrypta.com
/pqcrypta.com
Enter URL above
Ultimate: HTTP/3 + QUIC + 0-RTT disabled + WebTransport enabled. Maximum security & features.
Excellent: HTTP/3 with QUIC protocol. 0-RTT disabled for maximum security.
Good: HTTP/3 with QUIC protocol. 0-RTT enabled (replay attack risk).
Misconfigured: HTTP/3 enabled but not accessible. Missing Alt-Svc header.
Failed: No HTTP/3 support detected. Using legacy HTTP/2 or HTTP/1.1 protocols only.
HTTP/3 is the latest version of the Hypertext Transfer Protocol (RFC 9114), standardized by the IETF in June 2022. Unlike HTTP/1.1 and HTTP/2 which run over TCP, HTTP/3 uses QUIC (Quick UDP Internet Connections) as its transport layer. QUIC operates over UDP with mandatory TLS 1.3 encryption built directly into the transport protocol, delivering 30-50% faster page loads, improved mobile performance, and enhanced security compared to traditional TCP-based protocols.
Faster Connections: QUIC combines the cryptographic handshake with connection establishment (1-RTT), compared to TCP+TLS requiring 2-3 round trips. 0-RTT resumption enables instant reconnection for repeat visitors. Zero Head-of-Line Blocking: Independent streams prevent one slow resource from blocking others, critical for modern web applications with hundreds of assets.
Mandatory Encryption: Unlike HTTP/2 where TLS is optional, HTTP/3 requires TLS 1.3, the most secure version with forward secrecy and modern cipher suites. Transport Metadata Protection: QUIC encrypts packet numbers, connection IDs, and other transport metadata that TCP exposes in plaintext, defending against traffic analysis, fingerprinting, and network-level attacks.
Connection Migration: Unique connection IDs allow seamless handoff when switching networks (Wi-Fi โ cellular) without dropped connections or re-authentication. Improved Loss Recovery: Per-stream acknowledgments and more accurate RTT estimation provide better performance on lossy networks (mobile, satellite, public Wi-Fi). WebTransport: Bidirectional streaming over QUIC enables real-time applications like gaming, video conferencing, and collaborative editing.
QUIC v2 (RFC 9369, 2024) is an anti-ossification revision, not a feature release. It has the same capabilities as QUIC v1 (RFC 9000) but changes version codepoints, salts, and TLS labels so endpoints and middleboxes keep exercising version negotiation instead of hard-coding "QUIC = v1." It adds no new transport features. The genuinely new capabilities below are separate extensions, each on its own track โ they are not part of QUIC v2:
Sources: IETF QUIC Working Group โ RFC 9369 (QUIC v2), RFC 9002 (loss recovery / congestion-control baseline), draft-ietf-quic-multipath, draft-ietf-quic-ack-frequency. See the Technology Verification Status table below for per-feature standardization state.
Future HTTP/3 enhancements being discussed in IETF HTTP WG and research communities:
Source: IETF HTTP WG, draft-ietf-httpbis-*, W3C WebTransport specifications
Some research is exploring post-HTTP models entirely, rethinking how the internet routes and delivers content:
Source: IRTF ICNRG, ACM ICN workshops, Named Data Networking project
WebTransport is already positioned as the successor to WebRTC for many use cases. Future directions include:
Source: W3C WebTransport WG, IETF QUIC WG discussions, Chrome/Firefox roadmaps
Not standards yet, but active research in academia and industry (Google, Meta, Cloudflare):
Source: ACM SIGCOMM, Google Research (Remy, PCC Vivace), Meta's Robustness team
QUIC is expanding beyond HTTP/3 into databases, microservices, and system infrastructure:
Source: RFC 9250 (DNS over QUIC), gRPC roadmap, CNCF service mesh projects
| Layer | Current Cutting Edge | Next / Future | Status |
|---|---|---|---|
| Transport | QUIC v1 & v2 (RFC 9369), Multipath, ACK Frequency | FEC, newer congestion control (BBRv3/Copa) | v1+v2 live here drafts live here |
| HTTP | HTTP/3 (RFC 9114) | Partial reliability, better prioritization | Design Phase |
| Real-Time | WebTransport | Multipath + media + P2P | Active Dev |
| Architecture | Client/Server | Content-centric, P2P | Research |
| Performance | TLS 1.3 + QUIC | AI-optimized transport | Research |
| Beyond Web | HTTP/3 + WebTransport | QUIC for databases, RPC, IoT | Early Impl |
The technologies coming next are:
Timeline: QUIC v2 RFC 9369 (2024) โ live on this server's HTTP/3 and WebTransport endpoints as of 2026-07-25; Multipath QUIC still an active IETF WG draft industry-wide (this site's own server already implements full real server-side support - see the Verification Status table below); HTTP/3 extensions (2026-2027), AI-optimized (2027-2030), Content-centric networks (2030+)
Current standardization and implementation status of emerging technologies. The "supported here" badge means this scanner has genuine testing/validation capability for that technology on any site you scan. As of 2026-07-25, pqcrypta.com's own server also genuinely implements every "supported here" technology below (QUIC v2, CONNECT-UDP, ACK Frequency, and full Multipath QUIC) - scan this site and you'll see all four validate as real, not just the scanner's probing capability.
| Technology | Status | Evidence |
|---|---|---|
| QUIC v2 supported here | โ Standardized | RFC 9369 |
| Multipath QUIC supported here | โ Not standardized | draft-ietf-quic-multipath-21 |
| QUIC FEC | โ Research only | No RFC |
| HTTP/3 partial reliability | โ Research only | No active I-D |
| WebTransport multipath | โ Not implemented | No browser support |
| AI congestion control | โ Research only | SIGCOMM papers |
| DNS over QUIC | โ Standardized | RFC 9250 |
| MASQUE CONNECT-UDP supported here | โ Standardized | RFC 9298 |
| QUIC ACK Frequency supported here | โ ๏ธ Draft | draft-ietf-quic-ack-frequency |
| QUIC for databases | โ ๏ธ Experimental | Cloudflare prototypes |
| QUIC service mesh | โ ๏ธ Experimental | CNCF projects |
| Content-centric networking | โ Research only | ICNRG |