Check Your Browser User Agent

Instant live inspection of your browser User-Agent string, modern Client Hints (Sec-CH-UA), OS, and rendering engine, with an interactive custom UA string parser.

Chrome 125

Running on Windows 10 / 11 • Engine: Blink

BrowserChrome v125

Platform / OSWindows 10 / 11

Device Classdesktop

Privacy Guarantee100% In-Browser

Active Browser User-Agent Header

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36

Browser Details

NameChrome

Full Version125.0.0.0

Major Version125

Agent Typebrowser

Operating System

OS NameWindows

Kernel / Version10 / 11

FamilyWindows

Rendering Engine

Engine NameBlink

Engine Version537.36

CompatibilityStandard Web

Hardware & Device

Device Typedesktop

Vendor / MakePC

ModelWorkstation

CPU Architecturex86_64

Technical Specifications & Deep Dive

A standard User-Agent header is a formatted string structured as a succession of product identifiers and optional comments:

Mozilla/5.0 (Platform; OS-Version; CPU) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36

Mozilla/5.0: Historic token originally representing Netscape Navigator compatibility, retained by all modern browsers.
System Information: Enclosed in parentheses, specifies the operating system (e.g. Windows NT 10.0) and CPU architecture.
Platform Engine: AppleWebKit/537.36 indicates WebKit/Blink layout rendering engine.
Browser Version: Chrome, Edge, Safari, or Firefox version numbers.

Diagnostic Audit Receipt

Copyable plaintext audit summary and standardized JSON specification.

================================================== BROWSER USER AGENT DIAGNOSTIC RECEIPT ================================================== Detected At (UTC) : 2026-01-01T00:00:00.000Z Browser Name : Chrome Browser Version : 125.0.0.0 Rendering Engine : Blink (537.36) Operating System : Windows (10 / 11) Device Classification: desktop CPU Architecture : x86_64 Mobile Device : False Bot / Crawler : False Raw User-Agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Client Security : 100% In-Browser Memory (Offline) ==================================================

Understanding User-Agent Headers & Client Hints

Every HTTP request your web browser initiates includes a User-Agent header that identifies your software, operating system version, layout rendering engine, and device type to web servers.

With modern browser fingerprinting defenses, major vendors are freezing legacy UA strings and migrating to User-Agent Client Hints (UA-CH). Our diagnostics workstation allows developers, QA testers, and privacy researchers to inspect both legacy strings and high-entropy Client Hints with 100% on-device privacy.

Key Capabilities

•100% On-Device Privacy: Zero headers, IP addresses, or hardware fingerprints are transmitted to any server.
•Modern Client Hints Support: Inspects navigator.userAgentData brands, architecture, and bitness.
•Bot & Web Crawler Detection: Identifies Googlebot, Bingbot, Twitterbot, and HTTP libraries like cURL and Wget.
•One-Click Presets: Test 10 realistic device configurations including iPhone 15 Pro, Galaxy S24, and Windows 11 Chrome.

🛠️

Mouse Test

Test your mouse buttons, scroll wheel, and polling rate online.

🛠️

Keyboard Test

Test your keyboard keys, check ghosting, and verify functional keys online.

🛠️

Device Information

Get detailed information about your device, OS, screen, battery, and network.

Frequently Asked Questions

A User-Agent (UA) string is a header transmitted by your web browser in HTTP requests that informs web servers about your browser brand, version, layout engine, and host operating system. It allows servers to optimize content, format media, and troubleshoot compatibility issues.

User-Agent Client Hints (UA-CH) is a modern web standard developed to replace the legacy, unencrypted User-Agent header with granular, privacy-focused headers (Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform). Instead of broadcasting a comprehensive hardware fingerprint passively, browsers only send low-entropy basic data unless a server explicitly requests high-entropy values like architecture or kernel version.

Major browser vendors (Chrome, Safari, Edge, Firefox) have frozen parts of the legacy User-Agent string to curb cross-site digital fingerprinting and tracking. For instance, Chrome freezes minor build versions (reporting 0.0.0), Windows 11 reports as Windows NT 10.0, and macOS reports version 10_15_7 regardless of the actual OS release.

Yes! Switch to the 'Custom UA Tester' mode using the segmented toggle. You can paste any arbitrary User-Agent string (e.g. from Apache/Nginx logs, automated test runners, or mobile apps) or choose from 10 pre-loaded device presets to inspect browser names, engine types, and bot classifications.

The built-in parser evaluates known signatures for major search engine crawlers (Googlebot, Bingbot, Baiduspider, YandexBot, DuckDuckBot), social media scrapers (Twitterbot, FacebookExternalHit, LinkedInBot, WhatsApp, Discordbot), and command-line automation tools (cURL, Wget, Postman, Python Requests) with heuristics that eliminate false positives from standard desktop browsers.

No, absolutely not. All parsing, Client Hints inspection, and diagnostic receipt generation execute 100% locally inside your browser's JavaScript runtime. Zero IP addresses, headers, or device telemetry are ever sent to any remote server or external analytics service.