ToolAtlas
FavoritesRecent

User-Agent parser

Processed in this browser

Text limit: 2000000 characters

This tool never uploads your input.

A log line that starts Mozilla/5.0. We decode what we can. We do not fetch Client Hints from your users.

A support ticket with a UA blob and a “it works on my machine.” This page tokenizes the string. Frozen Chrome UAs and hint-based versions mean the OS/browser pair can be a year behind reality.

Status codes: HTTP reference. IPs: IPv4 subnet (math, not geo).

One support ticket

The UA pasted in a “cannot reproduce” bug. Hints only — UAs lie, and this is not analytics or bot scoring. Client Hints are not a full replacement here. Status codes are the HTTP reference.

How to use it

  1. Paste the UA from a log or DevTools.
  2. Read family / OS / device guesses.
  3. If you need the real Chrome major, look at Client Hints on the request — not this box.

Honest limits

Not a bot score. Not a legal device inventory. Not a tracking pixel.

FAQ

Why does Chrome look like an older version?

Desktop Chrome freezes parts of the UA. Real version lives in Client Hints (Sec-CH-UA). This page only sees the string you paste.

Can I detect bots reliably?

No. UAs are trivial to spoof. Do not build access control on this parse.

Do you log my visitors?

No visitors. You paste one string.

HTTP status lookup?

Different page — HTTP status & MIME.

Is the string uploaded?

No.

Related tools