Press Release

PQ Crypta Launches Enterprise HTTP/3 QUIC & WebTransport Scanner with 100+ Data Points

FOR IMMEDIATE RELEASE
January 31, 2026
Native Rust Implementation Measures Every Layer a Browser Goes Through

Today, PQ Crypta announces the release of its HTTP/3 QUIC & WebTransport Scanner—an enterprise-grade protocol analysis tool built on a native Rust QUIC stack that extracts over 100 data points per scan, identifies 50+ server implementations, and delivers ML-powered security recommendations in under 200 milliseconds.

The Challenge: Protocol Visibility in Modern Infrastructure

As HTTP/3 adoption accelerates (now supported by Cloudflare, Google, Facebook, Fastly, and major CDNs), organizations face a critical visibility gap. Traditional tools can't answer fundamental questions:

Browser DevTools show basic protocol information. Network analyzers require packet capture. Neither provides the deep metadata that security teams and performance engineers need.

"When we built this scanner, we wanted to expose everything the protocols actually negotiate—not just what's advertised. The difference between 'server supports HTTP/3' and 'browsers can actually use HTTP/3' is the difference between Grade A and Grade C. That distinction matters for security and performance."
— Allan Riddel, Founder of PQ Crypta

The Solution: Native QUIC Deep Inspection

Unlike browser-based or curl-based scanners, PQ Crypta's scanner uses native Rust QUIC libraries (quinn, h3, rustls) to establish real QUIC connections and extract metadata directly from the protocol handshake.

Technical Capabilities

One Grade: Adoption and Conformance

The scanner grades a site once, on how much of what it looks for the site has adopted and how closely that conforms to the RFCs. Adoption is the weighted share of what it looks for that the site has deployed: the core counts 6 each (post-quantum key exchange over TLS on TCP, post-quantum key exchange over HTTP/3, HTTP/3 a browser can find and reach and TLS 1.3), the hardening 4 (no TLS version older than 1.3, 0-RTT off, post-quantum key exchange chosen even when a client lists a classical group first, standard ML-KEM without the pre-standard Kyber drafts, a DNS HTTPS record naming h3, DNSSEC and a certificate within its validity period), the frontier 2 (Encrypted Client Hello, encrypted DNS at every name server, post-quantum key exchange on every encrypted DNS answer, post-quantum key exchange at every mail exchanger, where the domain receives mail, an ML-DSA certificate valid for the name in all but the trust of its root and delegated credentials) and the capabilities 1 (QUIC v2, WebTransport and CONNECT-UDP). Conformance is the share of the RFC checks the scan holds what is deployed to that it passes, area by area.

A++ needs at least 95% adopted. Where every item applies the weights total 67, and one item missing leaves at most 91.0% for a core item and 94.0% for a hardening item: A++ needs every core and hardening item, no TLS version older than 1.3 among them, so a site that still accepts TLS 1.2 reaches A+ at best. Of the frontier and the capabilities it may miss items weighing 3 in all (a frontier item weighs 2 and a capability item weighs 1).

The scan also names a common misconfiguration, HTTP/3 half deployed: servers with HTTP/3 enabled on the origin but nothing advertising it, so browsers fall back to HTTP/2 despite the server's capability, and HTTP/3 advertised where no QUIC listener answers.

Comprehensive Metadata Extraction

Each scan extracts detailed metadata across eight categories:

QUIC Transport Parameters (18 fields)

Flow control limits, idle timeout, max UDP payload size, datagram frame support, connection migration settings, and GREASE bit configuration. These parameters reveal server tuning and implementation characteristics.

TLS Extensions (14 fields)

ALPN protocols, key share groups (including X25519MLKEM768 for post-quantum), signature algorithms, ECH support, certificate compression, and GREASE extension usage. Critical for security assessment.

Server Fingerprinting (5 fields)

Implementation identification using 3-tier detection: header analysis (95% confidence), domain analysis (85%), and transport parameter patterns (70%). Identifies Cloudflare, Google GFE, Facebook mvfst, nginx-quic, LiteSpeed, Caddy, Fastly, and 40+ more.

Connection Metrics (20 fields)

Handshake time, time-to-first-byte, RTT estimates, congestion window, packets sent/lost, loss rate percentage, path MTU discovery status, and a passive server-side congestion-controller estimate (loss-based CUBIC/Reno vs rate-based BBR families) inferred from the server's response to packet loss — reported only when the path actually exercises loss, otherwise marked indeterminate.

Security Features (10 fields)

Retry packet usage, address validation, anti-amplification limits (3x standard), stateless reset support, and rate limiting detection.

HTTP/3 Settings (12 fields)

QPACK configuration, WebTransport enablement, DATAGRAM support, and RFC 9218 priority support.

HTTP/3 Headers (11 fields)

Alt-Svc, Server-Timing, Priority, Accept-CH client hints, NEL (Network Error Logging), Report-To, and 103 Early Hints detection.

WebTransport Capabilities (17 fields)

Session limits, stream types, datagram support, flow control, authentication requirements, and session establishment latency.

ML-Powered Recommendations

The scanner uses machine learning (RandomForest classifier with 100 trees) trained on historical scan data to provide contextual, actionable recommendations:

Recommendations include effectiveness scores and are filtered by context—no redundant advice for sites that already implement best practices.

Real-World Results

Every scan joins the public directory on the analyzer's page, where each grade's domains and the figures across every domain measured are live. The most revealing result is HTTP/3 half deployed: servers whose operators believe HTTP/3 is working while browsers silently fall back to HTTP/2, because nothing advertises it, or because what advertises it points at a QUIC listener nothing can reach.

Try It Now

Free Public Scanner

API Access

curl -X POST https://api.pqcrypta.com/http3-scanner/scan \
  -H "Content-Type: application/json" \
  -d '{"url": "https://cloudflare.com"}'

Technical Specifications

Scanner Engine

Performance

Data Extraction

What's Next

The HTTP/3 scanner is part of PQ Crypta's broader mission to provide visibility into modern protocol adoption and post-quantum readiness. Upcoming features include:

Since launch, the scanner has shipped certificate chain analysis with explicit PQC/composite-signature detection (subject, issuer, validity, key size, root CA, OCSP stapling, must-staple, Certificate Transparency SCT count), a real active test for RFC 9218 Extensible Priorities, and an experimental capability probe for the draft-ietf-quic-multipath-21 extension (informational only — it's still an active IETF draft, not a ratified standard, so it isn't factored into the grade).

About PQ Crypta

PQ Crypta builds enterprise-grade tools for the post-quantum era. Our platform implements NIST-standardized algorithms (ML-KEM-1024, ML-DSA-87, SLH-DSA), provides HTTP/3 QUIC infrastructure analysis, and delivers production-ready quantum-resistant encryption. We're committed to making advanced cryptography accessible and interoperable.

Website: pqcrypta.com
HTTP/3 Scanner: pqcrypta.com/http3-quic/
Email: contact@pqcrypta.com
GitHub: github.com/PQCrypta

Related Links

Media Contact:
Allan Riddel
Founder, PQ Crypta
contact@pqcrypta.com
pqcrypta.com
Keywords: HTTP/3, QUIC, WebTransport, Protocol Scanner, Server Fingerprinting, TLS 1.3, Post-Quantum Cryptography, X25519MLKEM768, ML-KEM, Security Analysis, Performance Testing, CDN Analysis, Rust, quinn, h3, RFC 9114, RFC 9000
Hashtags: #HTTP3 #QUIC #WebTransport #ProtocolAnalysis #WebSecurity #PostQuantum #TLS13 #CDN #Cloudflare #WebPerformance #Rust #OpenSource #CyberSecurity #NetworkSecurity #DevOps #SRE #WebDev #PQCrypta

⟨ QUANTUM ERROR PORTAL ⟩

Navigate the Error Dimensions