ShowIP.net
Menu

Request tool

User agent parser

Look up a user-agent string from a log or request header. Decode browser, engine, operating-system and device hints, and see whether the string contains known bot tokens.

Your request's user agent is shown by default. Paste another string and select Parse, then compare the fields with the original. Copy the result, download it as text, or copy a link to share the lookup.

Browser
Googlebot
Mobile
No
Bot
Yes
Raw user agent
Googlebot/2.1

Reference

Browser, engine and bot hints

Browser
The recognizable browser or client family from the string, when one is detectable.
Engine and OS
Rendering engine and operating-system hints found in the user-agent value.
Mobile and bot
Parser hints based on known tokens, not proof of device type or automation.
Raw user agent
The original string is shown so parsed fields can be compared with the log value.

Examples

Example strings

Browser

Mozilla/5.0 ... Chrome/148.0.0.0 Safari/537.36 Identifies Chrome from the Chrome token; the Safari token in the same string does not mean this is Safari. Parse browser example

Bot

Googlebot/2.1 Recognizes a bot token. This does not verify that the request came from Google. Parse bot example

Boundaries

Limits

User-agent strings can be spoofed, shortened or frozen. Use parsed values to interpret logs or investigate compatibility, and compare them with the raw string. Do not use them as the only fraud, rate-limit or access-control signal. The user-agent guide explains these limits.

For developers

Parse user agents in your code

Use a parser in your application to turn request headers or log entries into browser, OS, and device hints. These libraries have different rules, fields, and update schedules, so their results may differ from this tool. Test against strings from your own traffic and keep the parser's detection data up to date.

JavaScript / TypeScript

UAParser.js works in browsers and Node.js and includes TypeScript definitions. Install ua-parser-js with npm, then import UAParser and call UAParser(userAgent). The ESM / TypeScript quickstart shows the setup.

Version 2 is available under AGPL-3.0 or commercial licenses; check the project's license options before choosing an edition.

Python

ua-parser is useful for scripts and log processing. Install with pip install 'ua-parser[regex]', then use from ua_parser import parse and parse(user_agent) for browser, OS, and device results.

Go

mssola/useragent exposes browser, OS, mobile, and bot hints. Add github.com/mssola/useragent with go get, import it, and create a parser with useragent.New(userAgent). Read fields with methods such as Browser() and OS().

PHP

uap-php parses browser, OS, and device fields. Install with composer require ua-parser/uap-php, load Composer's autoloader, and create UAParser\Parser::create(). Call $parser->parse($userAgent) on that instance.

Java

YAUAA offers detailed analysis of user agents and Client Hints. Add the Maven dependency nl.basjes.parse.useragent:yauaa, create a UserAgentAnalyzer, and call parse(userAgent). Its integration guide covers instance reuse, logging setup, and limiting fields to reduce memory use.

C# / .NET

UAParser for .NET provides browser, OS, and device data. Install the UAParser NuGet package, create UAParser.Parser.GetDefault() once, and reuse it with Parse(userAgent) for each request.

A parsed user agent does not verify a visitor's identity or prove that a request is from a bot. Use browser feature detection for compatibility checks, and read the user-agent guide for spoofing and reduced browser strings.

Next steps

Advertisement