curl-http2

curl driving raw HTTP/2 with a browser User-Agent — its header order, TLS and TCP stack all contradict the claimed Chrome.

botverdict

1.00score

7/185checks fired

Convicting tells 7

net.accept_encoding_vs_uaUA claims a modern browser but Accept-Encoding omits Brotli (scripted client)

net.h2_header_order_vs_uaChromium UA but the HTTP/2 regular-header order is not chromium-shaped (JA4H)

net.h2_unknown_vs_uaModern-browser UA but the HTTP/2 stack matches no known browser engine

net.no_js_executionPage request with a TLS fingerprint but no browser layer (no JS ran — scripted client)

net.sec_fetch_vs_uaUA claims a modern browser but the request omits Sec-Fetch metadata headers

net.tcp_os_vs_uaTCP/IP-stack OS kernel contradicts the OS the User-Agent claims

net.tls_grease_vs_uaUA claims a GREASEing-engine browser (Chromium/Safari) but the TLS ClientHello has no GREASE