User-Agent Parser & Client Hints Inspector
Dissect User-Agent strings and evaluate modern Client Hints in real time. Identify browser engines, operating systems, hardware architectures, and search engine bots.
🔍 User-Agent Header Input
1. The Mechanics of User-Agent Headers in Web Architecture
A User-Agent (UA) string is a standard HTTP request header sent by web clients—including web browsers, search engine indexers, feed readers, and native mobile apps—to identify their vendor application, rendering engine, and host platform to origin web servers.
Web infrastructures historically utilized the User-Agent header for content negotiation, routing requests between desktop and mobile endpoints, or serving polyfills. However, modern engineering practices favor feature detection (e.g. Modernizr or native CSS @supports) because User-Agent strings can be modified, spoofed, or truncated by client-side privacy tooling.
2. Structural Anatomy of a Modern User-Agent String
| Token Segment | Example Substring | Technical Meaning |
|---|---|---|
| Compatibility Flag | Mozilla/5.0 |
Historic token maintaining backward compatibility with legacy servers |
| Platform & Architecture | (Windows NT 10.0; Win64; x64) |
Indicates the host OS kernel and 64-bit microprocessor architecture |
| Rendering Engine | AppleWebKit/537.36 (KHTML, like Gecko) |
Identifies the primary HTML/CSS document rendering core |
| Vendor & Version | Chrome/128.0.0.0 Safari/537.36 |
Specifies application vendor, release versions, and compatibility tokens |
3. Technical Limitations & User-Agent Reduction
- UA Reduction & Freezing: Modern browser engines freeze legacy UA strings to baseline values to prevent cross-site user fingerprinting. For instance, Chrome on Windows 11 intentionally reports
Windows NT 10.0rather than Windows 11. - Client Hints Dependency: Accurate detection of modern OS revisions, device models, and architecture requires high-entropy Client Hints (
Sec-CH-UA-Platform-Version,Sec-CH-UA-Model) queried over HTTPS. - String Spoofing: User-Agent headers can be altered in browser developer settings, proxies, or HTTP libraries (such as cURL or Python Requests). Never rely on User-Agent strings for sensitive authentication or security boundaries.
4. Client-Side Execution & Privacy Transparency
All pattern matching, regex dissection, Client Hints queries, and JSON generation run purely within your browser memory using JavaScript. Header strings entered into this tool are never sent across external networks or stored in cloud databases.
Standard analytics (Google Analytics) and ad network scripts (Google AdSense) operate on this site for operational metrics and ad delivery in accordance with our Privacy Policy.
5. Explore Related Developer Utilities
6. Frequently Asked Questions
What is User-Agent reduction and why are modern UA strings frozen?
Browser vendors freeze legacy User-Agent strings to prevent passive cross-site browser fingerprinting. Granular hardware details are now requested via User-Agent Client Hints (Sec-CH-UA).
Why do modern Chromium browsers include Safari/537.36 in their header?
Chromium's Blink engine originated as a fork of Apple's WebKit. Chromium includes Safari/537.36 so older web servers continue serving modern standards-compliant layouts.
Are my User-Agent headers or device details logged on remote servers?
No. All regex matching and metadata parsing execute strictly in client-side browser memory via JavaScript.
Can a User-Agent string distinguish between Windows 10 and Windows 11?
No. Due to UA reduction, both Windows 10 and Windows 11 report Windows NT 10.0. Differentiating them requires the high-entropy Client Hint Sec-CH-UA-Platform-Version.