PQ CRYPTA
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.
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.
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.
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.
Each scan extracts detailed metadata across eight categories:
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.
ALPN protocols, key share groups (including X25519MLKEM768 for post-quantum), signature algorithms, ECH support, certificate compression, and GREASE extension usage. Critical for security assessment.
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.
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.
Retry packet usage, address validation, anti-amplification limits (3x standard), stateless reset support, and rate limiting detection.
QPACK configuration, WebTransport enablement, DATAGRAM support, and RFC 9218 priority support.
Alt-Svc, Server-Timing, Priority, Accept-CH client hints, NEL (Network Error Logging), Report-To, and 103 Early Hints detection.
Session limits, stream types, datagram support, flow control, authentication requirements, and session establishment latency.
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.
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.
pqcrypta.com/http3-quic/?url=example.compqcrypta.com/http3-quic/example.comcurl -X POST https://api.pqcrypta.com/http3-scanner/scan \
-H "Content-Type: application/json" \
-d '{"url": "https://cloudflare.com"}'
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).
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