Browser family and version token
Parses Chrome, Edge, Firefox, Safari, Brave and DuckDuckGo identifiers when those identifiers are present. Brave detection also uses its optional browser API.
Browser identity test
This browser version check reads the identity information your current browser exposes to websites. The live panel reports the browser family, version token, operating-system family and complete user-agent string from this session.
A result such as Chrome 140 or Firefox 148 describes what the browser reports. Modern browsers may reduce, freeze or generalize parts of the user agent, so this is not a guarantee that every patch number or device detail is available.
The values below come from this browser session and update locally after the page loads.
Parses Chrome, Edge, Firefox, Safari, Brave and DuckDuckGo identifiers when those identifiers are present. Brave detection also uses its optional browser API.
Reads broad Windows, macOS, Linux, ChromeOS, Android or iOS/iPadOS markers. It does not inspect the device or operating system directly.
Shows the exact user-agent value and language list made available to JavaScript, which helps explain how the browser was classified.
The major browser version is commonly present, while minor or patch values may be omitted. Use the browser's own About or Update screen when exact patch verification matters.
A browser opened inside a social, email or search app may add tokens or report the underlying engine instead of the product name you see in the interface.
Privacy tools, developer settings and automation can override the reported user agent. BrowserCheck reports the exposed value; it does not bypass that choice.
Browser vendors increasingly reduce version detail to limit passive fingerprinting. The major version can remain while minor and patch values are frozen or omitted.
Not by itself. Release channels and patch schedules change quickly. Use the browser vendor's built-in update page as the authoritative check.
Brave uses Chromium and a Chrome-compatible user agent. BrowserCheck uses Brave's optional detection API when it is available, but privacy settings may prevent that distinction.
After identifying the browser, inspect its privacy signals, fingerprint surface, observable settings or WebRTC address exposure.