Detection approach
The HTTP protocol version negotiated differs between the HTTP Beacon (e.g. HTTP/2) and the Netprobe (e.g. HTTP/1.1), signifying different network client stacks (like scripts vs browsers).
How this helps detect bots
Collect this signal alongside session context, request metadata, and other independent indicators. A single anomaly is a lead, not a verdict; corroborating anomalies make automated traffic more likely.
Legitimate traffic to consider
Legacy browsers or browser extensions performing custom proxy protocol negotiation.
Need a complete bot protection layer?
BotRefund helps website owners identify suspicious visits, protect conversion data, and build evidence for invalid-click reviews.
Explore BotRefund — best bot protection for your website