Raw evidence JSON
Includes input UA, parsed result, Client Hints, navigator fields and server header parity for reports and evidence packages.
{}
Inspect the readable UA string beside Client Hints and runtime navigator fields.
Live navigator, Client Hints and server-observed request fields help compare the input UA with this browser environment.
Following BrowserScan and ToDetect style pages, UA, OS, engine, device, Client Hints and request headers are broken into reviewable fields.
| Field | Parsed value | Source | Status | Note |
|---|
Includes input UA, parsed result, Client Hints, navigator fields and server header parity for reports and evidence packages.
{}
Parse UA, Client Hints, browser, OS and bot clues.
Regular UA strings often still show Windows NT 10.0; Windows 11 needs Client Hints platformVersion context.
Chrome / Edge can expose brands, platform, architecture, bitness and full versions; some fields are async.
UA keywords such as bot, crawler, spider, Headless or Selenium move the result to review or fail.