User-Agent parser

User-Agent Header Decomposition and Client Classification

The User-Agent Parser analyzes client identification strings transmitted in the HTTP User-Agent request header. It decomposes legacy compatibility tokens, vendor flags, and version numbers to identify the visitor's web browser family and version, operating system release and architecture, layout rendering engine, and device form factor (desktop, mobile, tablet, or automated bot). Web analytics platforms and security teams rely on User-Agent classification to segment audience hardware and separate genuine human visitors from automated web scrapers.

Worked Example: Deconstructing Modern Client Telemetry

Examining a composite User-Agent string shows how multiple historical compatibility layers coexist:

Raw User-Agent Header

Parsed client telemetry breakdown:

• Browser Identity: Google Chrome version 129.0.
• Operating System: Apple macOS running on 64-bit architecture. (Note: Modern browsers freeze this string at 10_15_7 across all macOS releases to reduce device fingerprinting).
• Rendering Engine: Blink layout engine (derived from the Apple WebKit fork).
• Device Category: Desktop workstation.
• Compatibility Legacy Tokens: The tokens Mozilla/5.0, like Gecko, and Safari/537.36 originate from historical browser competition, where new browsers spoofed older identifiers so web servers would deliver full-featured HTML rather than degraded fallback layouts.

Client Detection Traps and Modern Alternatives

Engineers should avoid common mistakes when interpreting User-Agent headers:

• Browser version freezing: Major web browsers now practice User-Agent reduction. Chrome, Edge, and Firefox freeze minor version digits and operating system details in the legacy string to protect user privacy. Accurate operating system detection on modern browsers requires inspecting User-Agent Client Hints (Sec-CH-UA-Platform headers).
• Browser sniffing instead of feature detection: Altering website functionality or blocking features based on browser string matching is an antipattern. Always use feature detection in JavaScript (such as testing whether window.fetch or CSS container queries are supported) rather than checking the browser version string.
• Trusting User-Agent for bot filtering: Malicious scrapers, content thieves, and automated bots routinely send genuine Chrome or Safari User-Agent strings. True bot filtration must correlate IP addresses, Autonomous System Numbers (ASN), and behavior metrics rather than relying exclusively on self-declared User-Agent headers.

Related Header Diagnostics and Intelligence

Inspect all incoming request and response headers with our HTTP Headers Checker. To view real-world browser market share trends captured across the public websites in the BYOViral network, review our research publication on Browser Share 2026. To audit visitor IP address geolocation and network provider details, use the IP Lookup Tool.