A user agent is a text string a browser sends with web requests. It historically identified the browser, operating system, and rendering engine. Modern browsers increasingly reduce or standardize parts of this string for privacy, so it should be treated as a compatibility hint rather than a complete device fingerprint.
What this tool parses?
The page shows the raw string received by the server and a simple interpretation of browser family, operating system, and broad device type. The parser is intentionally lightweight; it is not designed for billing, security decisions, or analytics attribution.
Why results can look strange?
Chrome-based browsers often contain tokens for Safari and Mozilla for historical compatibility. iPad browsers may identify themselves differently depending on desktop-site settings. Privacy browsers can deliberately reduce identifying detail. Browser extensions and automated clients can also modify the header.
Use feature detection for development
If you are building a website, test whether the browser supports the feature you need rather than relying only on the user-agent string. That approach survives browser updates much better than a long list of name/version checks.
Why user-agent strings look strange?
Browser user-agent strings contain historical compatibility tokens that no longer map cleanly to product names. Privacy reduction and deliberate spoofing make exact hardware identification even less reliable. Use the raw string as a debugging clue, then prefer feature detection when building a website.
Useful troubleshooting cases
A user-agent check can confirm whether a request is coming from a mobile browser, an embedded web view, automation, or an unexpected browser family. It should not be used as the only security control because the value is client supplied.