J-Kit
Português

detect browser from user agent

Detect browser from User-Agent

Identifying the browser from the User-Agent is a classic debugging task: server logs, error reports, analytics and user support often require knowing exactly which browser is being used. This tool parses the UA string and exposes each field.

Why do all browsers look like Mozilla?

  • The historical convention of including "Mozilla/5.0" at the start of the UA comes from a compatibility strategy: when Netscape Navigator dominated, servers returned rich content only for UAs with that prefix, so other browsers copied it to avoid being blocked.

Common User-Agents

Chrome on Windows

Input
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36
Expected output
Chrome 120 · Blink · Windows 10/11

Includes WebKit/Safari references for historical compatibility reasons.

Safe use

Input
context + tool result
Expected output
interpreted with limits and next steps

Use the result as technical or educational support, keeping the tool limits explicit in the workflow.

Full tool FAQ

It is an HTTP header sent by the browser with every request, in the format: "BrowserName/Version (OS; Architecture) Compatibility/1.0 Engine/Version". The syntax is defined by RFC 7231 and was originally created so servers could adapt responses for different clients.

Frequently asked questions

How do I identify a bot from the User-Agent?

Legitimate bots usually declare their identity: Googlebot, Bingbot, AhrefsBot, etc. Look for tokens like "bot", "crawler", "spider" or known names. Note that malicious bots can impersonate legitimate browser UAs.

Does this page replace official or professional review?

No. It helps explain the scenario and use the tool more safely, but real decisions should consider official sources, full context and qualified guidance when needed.