AUTONOMY DIRECTORATE

๐Ÿ  Main

๐Ÿงช Interactive Apps

๐Ÿ“ฐ News

๐Ÿ›ก๏ธ PQ Crypta Proxy

๐Ÿ‘ค Account

โŸจ QUANTUM ERROR PORTAL โŸฉ

Navigate the Error Dimensions

๐Ÿš€ Analyze QUIC & HTTP/3 Security, Post-Quantum TLS & Performance

๐Ÿ”What it does: connects to any site over real QUIC and reports what the server actually negotiated, not a simulation.
๐Ÿ…What you get: a grade from A++ to F, with post-quantum key exchange required for the top tier, plus per-scan recommendations.
๐Ÿ“ŠWho it's for: a clear verdict for anyone, deep transport metrics for engineers who want the details.

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.

Full analysis coverage: every metric the scanner extracts

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.

  • HTTP/3 and QUIC protocol detection with native noq/h3 QUIC libraries (multipath-capable); QUIC v1/v2 (RFC 9369) and Version Negotiation detection, TLS 1.3
  • Post-quantum hybrid key exchange detection (e.g. X25519MLKEM768), required for the A++ grade tier
  • Server fingerprinting: Identifies Cloudflare, Google GFE, Facebook mvfst, Fastly H2O, and more
  • QUIC transport parameters: real peer-advertised flow control, stream limits, GREASE bit, connection migration, preferred address
  • HTTP/3 SETTINGS: QPACK dynamic table, Extended CONNECT, WebTransport, datagrams, RFC 9218 Extensible Priorities (real active PRIORITY_UPDATE test)
  • Connection metrics: handshake time, TTFB, RTT (including real minimum), GSO detection, ACK frequency, probe timeout count
  • Certificate chain analysis: OCSP stapling, Certificate Transparency/SCT, root CA, delegated credentials, PQC-signed certs
  • TLS extension analysis: ALPN protocols, key share groups, ECH support, certificate compression, 0-RTT early data
  • WebTransport capability testing: datagram support/size, flow control, stream limits, session-open latency (ports 443, 4433, or custom)
  • MASQUE CONNECT-UDP (RFC 9298) detection with real UDP-over-HTTP/3 relay verification
  • draft-ietf-quic-multipath capability probe with genuine cryptographic second-path validation
  • DNS HTTPS record (RFC 9460 type 65) fully parsed: alpn, port, ECH and IP hints, with the scan following any non-standard UDP port the record steers browsers to
  • Cross-protocol content comparison: the same URL fetched over HTTP/1.1, HTTP/2 and HTTP/3 and SHA-256 hashed, with a control fetch and per-request-token normalization (CSP nonces, CSRF tokens, timestamps) so even dynamic sites get a definitive answer on whether content differs by transport path
  • Alt-Svc header analysis and 0-RTT replay attack risk assessment
  • Intelligent, context-aware recommendations with 3-tier fingerprinting confidence scoring
Enter domain or full URL to scan
Optional
Default: /, /webtransport
Default: 443, 4433

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.comwww.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:

๐Ÿ’ก Three Ways to Use:
Query: ?url=pqcrypta.com
Path: /pqcrypta.com
Manual: Enter URL above

๐Ÿ“Š Scan Results live

๐Ÿ† A++ (0)

Ultimate: HTTP/3 + QUIC + 0-RTT disabled + WebTransport enabled. Maximum security & features.

Loading...

โœ… A+ (0)

Excellent: HTTP/3 with QUIC protocol. 0-RTT disabled for maximum security.

Loading...

โšก A (0)

Good: HTTP/3 with QUIC protocol. 0-RTT enabled (replay attack risk).

Loading...

โš ๏ธ C (0)

Misconfigured: HTTP/3 enabled but not accessible. Missing Alt-Svc header.

Loading...

โŒ F (0)

Failed: No HTTP/3 support detected. Using legacy HTTP/2 or HTTP/1.1 protocols only.

Loading...

What is HTTP/3 and QUIC?

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.

โšก Performance Benefits

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.

๐Ÿ”’ Security & Privacy

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.

๐Ÿ“ฑ Mobile & Reliability

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.

๐Ÿš€ What's Next After HTTP/3 + QUIC + WebTransport?

๐ŸŒ

QUIC v2 (RFC 9369) & Independent Extensions

Active Development

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:

  • QUIC v2 (RFC 9369) shipped supported here โ€“ Anti-ossification version with the identical feature set to v1; new codepoints keep version negotiation alive. This proxy handshakes both v1 and v2 on its HTTP/3 and WebTransport endpoints โ€” scan this site and the QUIC Version row lists v1 and v2.
  • ACK Frequency IETF WG draft supported here โ€“ Lets a receiver send fewer, batched acknowledgements to cut overhead on high-throughput transfers (draft-ietf-quic-ack-frequency).
  • Multipath QUIC IETF WG draft supported here โ€“ Manages multiple network paths (e.g. Wi-Fi + cellular) on one connection for failover and, depending on the scheduler, bandwidth aggregation (draft-ietf-quic-multipath). This scanner tests for it, and as of 2026-07-25 pqcrypta.com's own server implements the full extension (concurrent data-carrying paths, per-path packet-number spaces and loss recovery, and the complete PATH_ACK/PATH_ABANDON/PATH_STATUS lifecycle) via the noq QUIC stack โ€” scan this site and the Multipath field validates a genuine second data-carrying path.
  • Forward Error Correction (FEC) research only โ€“ Proactive recovery without retransmission, useful in theory for lossy links (satellite, 5G mmWave). Google's original QUIC had FEC and removed it; there is currently no IETF standards-track draft.
  • Congestion control (BBRv3, Copa) implementation choice โ€“ RFC 9002 defines a NewReno baseline; endpoints may deploy newer algorithms today. The IETF does not standardize a specific algorithm, and "AI-driven" variants remain research.

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.

๐Ÿ”„

HTTP/3 Extensions (Actively Being Designed)

Design Phase

Future HTTP/3 enhancements being discussed in IETF HTTP WG and research communities:

  • Partial Reliability โ€“ Send only what matters, skip corrupted or outdated data. Perfect for live video where old frames are useless.
  • Unidirectional Unreliable Streams โ€“ For gaming telemetry, sensor data, and real-time metrics where loss is acceptable.
  • Server Push Redesign โ€“ HTTP/2 push was deprecated due to poor adoption. New models being explored for predictive resource delivery.
  • Better Prioritization โ€“ Smarter scheduling algorithms that understand application-level importance, not just stream priorities.
  • Native Real-Time Media Support โ€“ Built-in primitives for video/audio streams without needing WebRTC's complexity.
  • Capsule Protocol / MASQUE โ€“ The Capsule Protocol (RFC 9297) and CONNECT-UDP (RFC 9298) are already standardized and supported by this proxy โ€” the scanner verifies a real UDP-over-HTTP/3 relay end-to-end. Ongoing work extends tunneling to CONNECT-IP (RFC 9484) and arbitrary protocols (VPNs, databases, custom protocols).

Source: IETF HTTP WG, draft-ietf-httpbis-*, W3C WebTransport specifications

๐Ÿ›ฐ

Beyond HTTP: New Protocol Families

Research Active

Some research is exploring post-HTTP models entirely, rethinking how the internet routes and delivers content:

  • Content-Centric Networking (CCN / NDN) โ€“ Routing based on content hashes, not server IPs. Request "video/abc123" from the network, get it from the nearest cache automatically.
  • Peer-to-Peer Transport Layers โ€“ Browser-native P2P without WebRTC's overhead. Think BitTorrent-level efficiency for web content delivery.
  • Encrypted-by-Default Object Protocols โ€“ IPFS-like content addressing but standardized at the transport layer. Every object is cryptographically verified.
  • Information-Centric Internet Architecture โ€“ Fundamental redesign where data flows are named and secured, not tied to specific servers or locations.

Source: IRTF ICNRG, ACM ICN workshops, Named Data Networking project

๐Ÿ”ฅ

WebTransport โ†’ WebRTC Replacement

Active Development

WebTransport is already positioned as the successor to WebRTC for many use cases. Future directions include:

  • WebTransport over Multipath QUIC โ€“ Real-time streams that seamlessly use WiFi + cellular simultaneously for maximum reliability.
  • WebTransport with Partial Reliability โ€“ Choose reliability per-stream: reliable for chat messages, unreliable for game positions, partially reliable for video.
  • WebTransport for Real-Time Media โ€“ Native video/audio codec integration, replacing WebRTC's SDP complexity with simpler APIs.
  • Browser-to-Browser WebTransport โ€“ Direct peer connections without STUN/TURN servers, using QUIC's connection migration.
  • WebTransport Pooling โ€“ Share QUIC connections across browser tabs for lower overhead and faster startup.

Source: W3C WebTransport WG, IETF QUIC WG discussions, Chrome/Firefox roadmaps

๐Ÿง 

AI-Optimized Networking

Research Active

Not standards yet, but active research in academia and industry (Google, Meta, Cloudflare):

  • AI-Driven Congestion Control โ€“ Neural networks that learn network behavior patterns and optimize throughput better than traditional algorithms.
  • Predictive Packet Scheduling โ€“ ML models that predict which packets will be needed next based on user behavior and application state.
  • Adaptive Protocol Negotiation โ€“ Automatically switch between QUIC, TCP, or future protocols based on real-time network conditions and application requirements.
  • Smart Connection Migration โ€“ AI decides when to switch networks, pre-warms connections, predicts handoffs before they happen.
  • Traffic Pattern Recognition โ€“ Identify application types (video, gaming, browsing) and apply custom optimizations automatically.

Source: ACM SIGCOMM, Google Research (Remy, PCC Vivace), Meta's Robustness team

๐Ÿงฉ

QUIC for Everything (Beyond Web)

Early Implementations

QUIC is expanding beyond HTTP/3 into databases, microservices, and system infrastructure:

  • Database Protocols over QUIC โ€“ MySQL, PostgreSQL, MongoDB replication using QUIC for better latency and connection migration. Already prototyped by Cloudflare.
  • gRPC over QUIC โ€“ Microservice RPC with 0-RTT reconnection, multiplexed streams, and better mobile support. Google is actively working on this.
  • Service Mesh QUIC Backplanes โ€“ Istio, Linkerd, Consul using QUIC for inter-service communication instead of TCP. Better observability and performance.
  • DNS over QUIC (DoQ) โ€“ RFC 9250 standardized. Faster, more private DNS queries with connection reuse. Cloudflare, Google DNS support it.
  • SSH over QUIC โ€“ Persistent remote shells that survive network changes. No more "connection lost" when switching networks.
  • IoT Protocols over QUIC โ€“ MQTT, CoAP running over QUIC for better reliability on unstable networks (satellites, cellular).

Source: RFC 9250 (DNS over QUIC), gRPC roadmap, CNCF service mesh projects

๐Ÿ

The Complete Roadmap

Summary
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 Next Wave of Innovation

The technologies coming next are:

  • Newer congestion control algorithms beyond RFC 9002's baseline (QUIC v2 itself already shipped as RFC 9369)
  • HTTP/3 extensions with partial reliability
  • WebTransport++ replacing WebRTC
  • AI-optimized transport layers
  • QUIC everywhere (databases, microservices, IoT)

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+)

๐Ÿ“‹

Technology Verification Status

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