User Agent Finder
Read a User-Agent string: browser, engine, operating system, device, bot or tool, and what looks inconsistent or suspicious.
Runs in your browser Your input never leaves your device.
What stands out
Technical details
A User-Agent is text the client chooses, so everything here is a reading of that text, not proof of what sent it. Nothing you paste leaves your browser.
Report a problem with this tool
About this tool
A User-Agent is the text a browser or program sends to say what it is. This tool reads it. The browser or app, its version, the operating system and the device come from the ua-parser database (uap-core), the same data many analytics and security products use, which recognises thousands of browsers, apps, phones and tablets. Known crawlers and bots are found with the crawler-user-agents list (about 1,500 patterns), and command-line tools and libraries such as curl, Python requests, Go and OkHttp are named separately. The engine (Blink, WebKit, Gecko and so on) and a device type (phone, tablet, desktop, smart TV, console, bot or tool) are read from the text; the device type is an estimate. Below the results, a list shows what stands out. These are explicit checks, not guesses: a User-Agent that names two operating systems, Firefox together with AppleWebKit, Chrome together with Firefox, Chrome on an iPhone without CriOS, Chromium Edge without Chrome, a Windows desktop that says Mobile, a Windows NT version that does not exist, a very short or very long value, control characters, or text that looks like markup, SQL, a path traversal or a log4j lookup (User-Agents often end up in logs and web pages, so attackers put probes in them). It also explains values that look odd but are normal: macOS always says 10_15_7, Windows 10 and 11 both say NT 10.0, Chrome sends a reduced version such as 120.0.0.0, and Android may hide the model as "K". Internet Explorer and legacy Edge are flagged as end-of-life, and headless and automation browsers are named. A User-Agent is only a claim, so a crawler match does not prove the request is genuine: search engines document verifying their bots with a reverse DNS lookup. We checked the parser by running the ua-parser project's own test cases through it (3,696 browser, operating system and device cases, all matching), checked the example strings of the crawler list (all are recognised except those of five patterns we removed because they also match ordinary phones, such as a phone model named Butterfly or an Android build number), ran every Android phone in the ua-parser fixtures through the bot check to confirm none is flagged, confirmed that ordinary browsers are not flagged as bots, and tested each consistency check on crafted strings and on genuine ones. Some things cannot be read from the text: Safari on an iPad in desktop mode sends the same User-Agent as Safari on a Mac. The first time you use the tool it loads about 360 KB of data (the pattern lists) in your browser; the User-Agent you paste is never sent anywhere.
How to use it
- Paste a User-Agent, or press the button to use your own browser's.
- Read the browser, engine, system, device and type.
- Check the list of things that stand out.
- Open the technical details if you need the raw values.
Example
The consistency checks catch User-Agents that were put together by hand.
Mozilla/5.0 (iPhone; CPU iPhone OS 17_1 like Mac OS X; Windows NT 10.0) AppleWebKit/537.36 Chrome/120.0.0.0 Firefox/121.0 Safari/537.36
Operating system: iOS. Check: names more than one operating system (Windows and iOS); contains both Chrome and Firefox; says iPhone with Chrome/ but not CriOS/.
How to find your user agent
- On this page
- Press the button to load your own browser's User-Agent into the box and read it.
- Browser console
- Open developer tools (F12), go to Console and type navigator.userAgent.
- Network tab
- In developer tools, open Network, click any request and look for User-Agent under Request Headers.
- Chrome
- Open chrome://version and read the User agent line.
- Firefox
- Open about:support and read User Agent under Application Basics.
- Command line
- Run curl -v with any URL to see the User-Agent curl sends, or set your own with -A.
Reading a User-Agent string
Take Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Mozilla/5.0 is a historical token almost every browser sends. The part in brackets names the platform: Windows NT 10.0 on 64-bit. AppleWebKit, KHTML and Gecko are compatibility tokens. Chrome/120.0.0.0 is the real browser and version. Safari/537.36 is there for old sites that check for Safari.
Because browsers copy each other's tokens, the order and the combination matter more than any single word. That is why a parser and a list of patterns are needed.
Why the User-Agent says less than it used to
Chrome and other Chromium browsers now send a reduced User-Agent: the minor version is 0.0.0, Windows 10 and 11 both say NT 10.0, and Android may hide the phone model. More detail is available to sites through User-Agent Client Hints (Sec-CH-UA headers and navigator.userAgentData in JavaScript). This tool reads only the User-Agent text, so it shows what that text says and explains values that are frozen on purpose.
Common problems
- It says Unknown for my browser
- The database does not know it, or the string is shortened. New or rare browsers and apps appear in updates; the string may also not be a real User-Agent.
- It does not show my exact Windows or macOS version
- Modern browsers hide it on purpose: Windows 10 and 11 both say NT 10.0, macOS always says 10_15_7. The User-Agent cannot tell them apart.
- A bot was not recognised, or a real visitor was flagged
- No list is complete, and a User-Agent can be faked in both directions. For important decisions, verify by IP address (reverse DNS for search engines) rather than by the text.
Frequently asked questions
How do I change my user agent?
In Chrome or Edge, open developer tools, open the Network conditions panel and untick Use browser default to pick or type another one. Extensions can do this too. For scripts, curl -A and most HTTP libraries let you set the header.
Can a website identify me by my user agent?
Not on its own, because many people send the same string. It is one of the signals used in browser fingerprinting, together with things like screen size, fonts and IP address.
Is this tool a user agent lookup for bots?
Yes. Paste the User-Agent from your server log and it names known crawlers and command-line tools. A matching name does not prove the visitor is that bot, so verify important ones by IP address.