← How We Detect Bots (All 180+ Signals) REVERSE-ENGINEERED DATADOME & PERIMETERX VECTORS • TIER 1 (WEIGHT: 85)

Error Stack Trace Inconsistency

Technical forensic specification explaining how BotRefund analyzes browser environments and network invariants to distinguish novel retail browsers from server-side automation.

Authentic Consumer Baseline

Normal Consumer Browser

Authentic consumer browsers maintain strict internal coherence across operating system APIs, physical hardware constraints, and userland execution environments.

Automated Server Fingerprint

Automated Bot & Novel Browser

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.

CHROMIUM & NETWORK PROTOCOL BLUEPRINT

Technical Forensic Specification

Error Stack Trace Engine Inconsistency & Automation Artifacts: Runtime Error().stack inspection revealed automation controller execution frames (puppeteer/playwright/eval) or a JavaScript engine formatting discrepancy (e.g. V8 vs JavaScriptCore syntax) relative to the claimed User-Agent. Genuine consumer browser sessions never expose automation execution frames or formatting discrepancies.

FORENSIC SIGNATURE: `error_stack_trace_inconsistency` / `Error Stack Trace Inconsistency`
ENGINE DISCREPANCY: Signature mismatch detected on invariant check: `error_stack_trace_inconsistency` / `Error Stack Trace Inconsistency`
CORROBORATION RULE: Multi-layer voting engine evaluates alongside hardware entropy & L4 netprobe

DISPUTE DOSSIER VERIFICATION // AD PLATFORM REVIEWERS

For Google Ads & Meta Click Quality Reviewers

Ad Platform Fraud Classification: Under Google Ads Invalid Traffic guidelines (Automated Click Activity) and Meta Advertising Integrity standards, sessions exhibiting Error Stack Trace Inconsistency 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.

FALSE-POSITIVE MITIGATION

Multi-Dimensional Corroboration Engine

Human Baseline & Exception Scenario: None. Native browser engines maintain strict architectural invariants in error call stacks.

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.

Independent Evidence

This signal registers an objective, mathematically verifiable anomaly on the session ledger.

Cross-Checked Context

BotRefund correlates L4 packet timing, GPU silicon, and cursor jerk before finalizing risk.

Carrier-Ready Dossier

Compiled directly into Google Ads and Meta refund packets with verified click IDs and server logs.