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

Zero-Chrome Taskbar Anomaly

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

Novel automation engines and server-side browsers exhibit detectable structural inconsistencies when evaluated against physical client hardware baselines.

CHROMIUM & NETWORK PROTOCOL BLUEPRINT

Technical Forensic Specification

Zero-Chrome Taskbar Desktop Framebuffer Anomaly: Desktop window metrics indicate screen.availHeight equals screen.height and outerHeight equals innerHeight without native fullscreen mode. Genuine consumer operating systems consume physical display margins (Windows taskbar, macOS menu bar); identical screen and window bounds confirm a headless virtual display (Xvfb / Docker container).

FORENSIC SIGNATURE: `zero_chrome_taskbar_anomaly` / `Zero-Chrome Taskbar Anomaly`
ENGINE DISCREPANCY: Signature mismatch detected on invariant check: `zero_chrome_taskbar_anomaly` / `Zero-Chrome Taskbar Anomaly`
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 Zero-Chrome Taskbar Anomaly 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: Genuinely borderless kiosks or native fullscreen apps that do not report fullscreenElement.

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.