FAQ
How do I see my own UA?
Click the My UA button: it reads the User-Agent string your browser is currently sending and parses it.
How is the WeChat in-app browser detected?
Its UA contains the MicroMessenger token. UC, 360 and Edge have their own tokens and are recognised too.
Can UA be trusted for security decisions?
No. The client sets it and can forge it freely. Use it for analytics and adaptation, never for authorisation or risk control.
Why does Windows 11 show as 10/11?
Because Windows 11 still reports Windows NT 10.0 in its UA - Microsoft froze the token to avoid compatibility breakage. In the same way, iPads on iPadOS 13+ send a desktop macOS UA by default, so the string alone cannot tell you it is a tablet; that needs client-side signals such as touch points.
About this tool
Splits a User-Agent string into four parts - browser, operating system, device type and rendering engine - and flags crawlers separately. The My UA button parses the string your current browser is actually sending, so you do not have to dig through devtools.
UAs are unreliable by design, and that comes first. The client sends it and curl can rewrite it in one line, while browsers keep freezing and trimming its fields for compatibility. Treat the result as input for analytics and adaptation, never for authorisation, risk control or security decisions.
Cases that look like misdetection but are not:
- Windows 11 shows as 10/11: Windows 11 still reports
Windows NT 10.0because Microsoft froze the version token. - iPad shows as macOS desktop: since iPadOS 13 iPads request desktop sites and send a Mac-like UA, so only client-side signals such as touch points can tell them apart.
- Chinese browsers report Blink (Chromium): WeChat (X5/XWeb), QQ and 360 run Chromium in their fast mode and carry
Chrome/in the UA. The engine column reports the real engine, not the brand. - Chrome UAs also contain Safari: Chromium keeps
Safari/537.36for compatibility, so matching must checkEdg/,OPR/andChrome/beforeSafari/- which is the order used here.
Crawlers are detected through tokens such as bot, spider, crawler and slurp, covering Googlebot, Bingbot, Baiduspider, Bytespider, Sogou and Yisou; anything else echoes the raw token. A UA claiming to be Googlebot proves nothing - verifying the visitor IP against the official ranges is the only trustworthy check.
Parsing is local; the UA is not uploaded. It is not sensitive anyway: every site you visit already sees this exact string.