How to use
- Review the analysis of your current browser, loaded automatically.
- Paste any other User-Agent string, such as one from server logs.
- Check the detected browser, engine, OS, device type and CPU.
Use cases
- Investigating bugs reported on specific browsers or devices.
- Analyzing access logs to understand your user base.
- Checking the User-Agent sent by apps, bots and HTTP clients.
Technical concepts
Anatomy of a User-Agent
For historical reasons, almost every browser starts with Mozilla/5.0 and includes tokens from other engines (AppleWebKit, KHTML, like Gecko, Safari) for compatibility. The real browser is identified by the combination and order of these tokens.
Reduced User-Agent and Client Hints
Chrome and Edge froze parts of the User-Agent, such as the minor version and OS version, in favor of User-Agent Client Hints (Sec-CH-UA). That is why Windows 11 and Android versions may look generic.
Prefer feature detection
To decide front-end behavior, prefer feature detection (if ('share' in navigator)) over inferring capabilities from the User-Agent, which can be spoofed or change with any release.
Frequently asked questions
Why does my Windows 11 show up as Windows 10?
The Windows 11 User-Agent is identical to Windows 10 (Windows NT 10.0). Only Client Hints tell the versions apart.
Is the User-Agent reliable?
Not for security: any client can send whatever string it wants. Use it only for statistics and diagnostics.