nicetool.dev logo

My User Agent

Your user agent is sent with every request. Paste any other UA below to analyse it.

Your user agent

...

User-Agent Client Hints

The modern, structured replacement for the UA string. Chromium browsers expose it to scripts; high-entropy values may need permission from the site.

Analyse any user agent

Samples:

Browser

Safari 18

Engine

WebKit

Operating system

iOS 18.0

Device type

Mobile

Bot / crawler

No

What is a user agent?

A user agent (UA) string is a line of text your browser sends in the User-Agent header of every HTTP request, such as "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36". Servers and analytics tools read it to guess the browser, operating system and device. For historical reasons almost every UA starts with "Mozilla/5.0" and mentions several engines, which makes it hard to read by eye. Browsers are now freezing parts of the string for privacy (Windows 11 still reports "Windows NT 10.0", macOS is capped at 10.15.7) and moving detailed data to User-Agent Client Hints.

Features

  • • Shows your exact user agent string with one-click copy
  • • Parses browser and major version, rendering engine, OS and version, device type
  • • Reads User-Agent Client Hints: brands, platform version, architecture, bitness, model
  • • Analyses any pasted UA, with samples for iPhone, Android, Windows, macOS and Googlebot
  • • Flags bots and crawlers such as Googlebot or headless browsers

Runs in your browser

The user agent and Client Hints are read and parsed locally with JavaScript. Nothing you paste into the analyser is uploaded or stored.

100% client-side parsing.

How to use the My User Agent

  1. 1

    Open the page: your user agent string is read from the browser and shown at the top, with the browser, engine, OS, device type and bot status parsed below it.

  2. 2

    Copy the string when a bug report or support ticket asks for your browser details, so nobody has to guess versions.

  3. 3

    Check the Client Hints card in Chrome, Edge or Opera: it shows the real platform version (for example Windows 11) and CPU architecture that the frozen UA string hides.

  4. 4

    Paste any other UA, for example from a server log, into the analyser, or pick a sample, to see how it is interpreted.

Practical examples

Reproducing a user bug

Ask the reporter to open this page and send the copied string: you get the exact browser build and OS, and can test in the same environment.

Reading access logs

Paste a UA from Nginx or Apache logs to tell real visitors from crawlers, uptime monitors and scripts that send curl or python-requests.

Testing responsive behaviour

Switch device emulation in DevTools and reload: the parsed device type and OS show what your server-side detection will see.

Verifying a crawler

Check that a bot claiming to be Googlebot has the expected UA, then confirm with a reverse DNS lookup, because the UA alone can be faked.

Frequently asked questions

Why does Windows 11 show as Windows 10/11?+

Browsers froze the UA token at "Windows NT 10.0" for both versions. Chromium browsers expose the real version through Client Hints, which this page reads to show Windows 11 when it can.

Can I trust the user agent?+

No, it is sent by the client and can be changed by extensions, DevTools or any script. Use it for statistics and compatibility hints, never for security decisions.

Why does every UA start with Mozilla/5.0?+

In the 1990s servers sent better pages to Netscape (Mozilla), so other browsers copied the token to get them. The habit stuck and now every major browser includes it.

Should I use UA sniffing in my code?+

Prefer feature detection (checking if an API exists) and responsive CSS. Use the UA or Client Hints only for analytics or for known bugs in specific versions.