Technical forensic specification explaining how BotRefund analyzes browser environments and network invariants to distinguish novel retail browsers from server-side automation.
Legitimate consumer sessions originate directly from residential, cellular (LTE/5G), or corporate office ISPs. Network packets exhibit standard unfragmented Maximum Transmission Units (MTU 1500, TCP MSS >= 1460 bytes) without tunnel encapsulation headers, and domain lookups resolve via local ISP nameservers.
Automated scraping rings route clicks through commercial datacenter servers or residential proxy tunnels. Tunnel encapsulation (WireGuard/SOCKS5) clamps TCP SYN MSS to <= 1420 bytes, leaks residential IPs via WebRTC, or routes DNS queries through discordant overseas resolvers.
HTTP/2 Frame Sequencing & Protocol Inconsistency (Netprobe Port 8443): The client's raw HTTP/2 connection stream exhibited critical RFC 7540 protocol violations or ALPN negotiation anomalies. Prohibited HTTP/1.1 hop-by-hop headers (such as 'Connection', 'Keep-Alive', or 'Upgrade') were detected in HTTP/2 stream frames, or a modern retail Chrome client failed to negotiate HTTP/2 via ALPN and omitted mandatory Sec-CH-UA client hint frames. Retail desktop and mobile browsers enforce strict HTTP/2 protocol frames natively in C++; these anomalies prove the request was emitted by an unpatched custom scraping engine, Python HTTP library (e.g. urllib3/requests), or low-level proxy tunnel.
Ad Platform Fraud Classification: Under Google Ads Invalid Traffic guidelines (Automated Click Activity) and Meta Advertising Integrity standards, sessions exhibiting HTTP/2 Frame Sequencing violate fundamental consumer hardware invariants. They fail deterministic silicon rasterization, protocol compliance, or neuromuscular biometrics.
Why This Proves Non-Human Origin: Genuine consumer browsers on retail operating systems execute this API natively with verified hardware backing. Server software (headless cloud containers, unpatched automation harnesses, and proxy tunnels) cannot replicate this execution environment without incurring prohibitive server hardware costs.
Evidence Dossier Invariants: Each disputed click in our export packet matches an immutable server-side timestamp, landing URL, GCLID/fbclid, and observed IP address with zero client-side tamperability.
Human Baseline & Exception Scenario: None. Retail Chromium and WebKit implementations automatically strip hop-by-hop headers and negotiate ALPN `h2` on TLS connections.
BotRefund operates a multi-vector ensemble model. This signal adds objective forensic weight to the session dossier but never acts in isolation. Positive verdicts require corroboration across network routing, hardware silicon, and cursor kinematics to guarantee 99% precision.
This signal registers an objective, mathematically verifiable anomaly on the session ledger.
BotRefund correlates L4 packet timing, GPU silicon, and cursor jerk before finalizing risk.
Compiled directly into Google Ads and Meta refund packets with verified click IDs and server logs.