What Is My User Agent - Free Instant Checker

What is my user agent? This free user agent checker shows the user agent string your browser sends to every website and splits it into browser, version, operating system, device type and engine. You can also paste any other string to parse it, which helps developers, QA testers and SEOs who read server logs.

What Is a User Agent String?

A user agent string is a line of text that your browser or app sends with each web request to tell the server what software is asking for the page. It usually names the browser, its version, the operating system and the rendering engine. It travels in the HTTP User-Agent header.

Servers use it to choose a layout, count visits by device and decide how to treat automated traffic. Search engine crawlers send one too, which is how site owners spot Googlebot in their logs.

User agent strings are messy because of history. Almost every modern browser starts with Mozilla/5.0 and mentions words like Safari or Gecko, because old websites checked for those words and browsers kept them for compatibility. Chrome's string says like Gecko and Safari even though it is neither. That is why this tool labels the engine row as a reported compatibility token, not a guaranteed fact.

How to Use the What Is My User Agent Tool

You can read your own user agent in a few seconds, and parsing a different string takes one extra step.

1. Open the page. Your own string appears at once in the results table, with no button to press.
2. Check the rows: User Agent String, Browser, Operating System, Device Type, Reported engine compatibility token, Is Mobile and Is Bot/Crawler.
3. To test another string, click inside the box labeled Parse a Custom User Agent String and paste the text, for example one copied from a server log.
4. Click Parse Custom UA. A second table appears below with the same seven rows for the string you pasted.
5. If you click the button with an empty box, you will see the message "Please enter a user agent string." Paste a string and try again.
6. Copy the string from the first row whenever another app, form or support ticket asks for it.

Worked Example: Reading a Real User Agent String

Here is a realistic desktop string you might see on a Windows laptop running Chrome: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

Paste it into the custom box and the tool returns the following.

• Browser: Google Chrome v124.0.0.0
• Operating System: Windows 10/11 (both versions report the same token, so the tool shows them together)
• Device Type: Desktop (inferred)
• Engine token: WebKit/Blink v537.36
• Is Mobile: No. Is Bot/Crawler: No

Now try a command-line request such as curl/8.4.0. The tool sets Is Bot/Crawler to Yes and Device Type to Bot/Crawler, while Browser and Operating System stay Unknown because the string names neither. That is the correct reading: a script made the request, not a person with a browser.

Try a third string with Android in it, such as a Chrome on Pixel phone string. You get Android with its version number, Device Type set to Mobile and Is Mobile set to Yes.

How to Read and Act on the Results

Each row answers one question about the visitor, and some rows deserve a second look before you act on them.

Browser and version

The tool recognizes Microsoft Edge, Opera, Google Chrome, Chromium, Mozilla Firefox, Apple Safari and Internet Explorer. Edge and Opera strings also contain the word Chrome, so the tool checks for Edge and Opera first and names them correctly. A very old version number, such as an Internet Explorer entry, is a sign to test your site for legacy support or to question the traffic source.

Operating system

Windows 10 and 11 both appear as 10/11. On Macs, current Chrome and Safari often report macOS 10.15.7 no matter which macOS release is installed, so treat that number as a label, not a real version. Chrome on an iPhone reports itself in a way that can show up as Apple Safari, because it runs on Apple's engine.

Device type, mobile and bot flags

Device Type shows Mobile when the string mentions Android, iPhone, iPod, BlackBerry or Windows Phone, and Tablet when it mentions iPad or tablet. An Android tablet that never uses the word tablet will show as Mobile. When none of those words appear but the operating system is known, the tool says Desktop (inferred), since desktop browsers do not announce themselves.

The bot flag turns on when the string contains words such as bot, crawler, spider, scraper, curl, wget, python, java or go-http. Treat it as a quick screen, not proof. Anyone can put Googlebot in a string, so verify important crawlers by checking the requesting IP with a domain to IP lookup or reverse DNS, as Google's Search Central documentation advises.

How Do I Find, Copy or Change My User Agent?

To find your user agent, open this page and copy the first row of the results table. That is the exact text your current browser sends, so it is what you should paste into a support form, a bug report or an app setting that asks for a user agent.

Some people arrive after seeing a user agent field in an app, such as a reader app that lets you set a custom string for its sources. In that case copy the string here and paste it into the app's field. The tool only reads and parses strings. It does not change what your browser sends.

To change your user agent for testing, use your browser's developer tools. Chrome DevTools has a Network conditions panel where you can switch off the automatic setting and pick or type a different string, and Firefox lets you override it in its advanced configuration. After changing it, reload this page to confirm the table shows the new value. Remember that a user agent string does not contain your IP address. If you want that detail, use bulk IP lookup on addresses from your logs.

Who Uses a User Agent Checker?

This checker helps anyone who needs to know what a request claims to be, and each audience uses it a little differently.

• Web developers: reproduce a bug that only appears on one browser version, or confirm that a device detection rule matches the strings you expect.
• SEOs and site owners: decode strings in server logs to separate crawler hits from human visits, and see whether smartphone or desktop agents dominate. For a wider look at your own setup, what is my browser adds screen size and other details.
• QA testers: record the exact browser, version and operating system in a bug report so developers can reproduce it.
• Support teams: ask a customer to open the page and send the first row instead of guessing at version numbers.
• Network administrators: inspect suspicious strings, then trace the source network with an ASN lookup.

Best Practices and Troubleshooting Tips

A few habits keep your readings accurate and stop you from drawing the wrong conclusion.

• Paste the whole string. A cut-off string drops the version or the platform token, and the row shows Unknown. Copy from the opening Mozilla text to the final token.
• Remove extra characters. Quote marks, a log timestamp or the label "User-Agent:" in front of the text can confuse the result. Paste only the string value.
• Do not rely on the string alone. It can be edited by extensions, privacy settings or testing tools. Compare it with real behavior before you block or redirect anyone.
• Expect Unknown for custom apps. Scripts and in-house apps often send short strings like MyApp/2.1, which name no browser or operating system.
• Check your network side too. If traffic from a string looks wrong, run a DNS lookup on the domain involved, and browse the network and IP tools for the next check.

Limitations to Keep in Mind

A user agent string is a claim, not a verified fact. Browsers can freeze or shorten parts of it, and tools can fake it completely, so this page reports what the text says, not what the visitor truly is.

Detection uses the words and version patterns in the string, so very new browsers, niche browsers and unusual builds may show as a better-known browser or as Unknown. Desktop is inferred when nothing marks the request as mobile or bot. Some tablets, including iPads set to request desktop sites, may appear as desktop computers.

Use the tool to read and decode strings quickly, and use logs, IP checks and real device testing when a decision depends on the answer.

Open the page, read your own string in the first table, then paste any string from your logs or bug reports into the custom box and click Parse Custom UA to see exactly what it claims.