Why does my Windows 11 PC show Windows 10 / 11?

The string reports Windows NT 10.0 for both versions, so it alone cannot tell them apart. On Chrome and Edge the Client Hints block reads platformVersion and the parser shows Windows 11 when that value is 13 or higher. Firefox does not expose Client Hints, so it stays at 10 / 11.

Can I change my User-Agent?

Yes. Browser developer tools have a device emulation mode that overrides it, extensions can set it per site, and command-line tools accept it as an option. Because it is so easy to change, never base security decisions on it.

What are User-Agent Client Hints?

Values that Chromium browsers expose through navigator.userAgentData in place of the frozen string. The low-entropy ones (brands, platform, mobile) are always available. The high-entropy ones (platformVersion, architecture, bitness, model, full version list) are requested by this page with getHighEntropyValues. Browsers without the API show no Client Hints block.

Why does the device type say Unknown?

The parser found no recognised operating system token and the string matched no known bot. Scripted clients, embedded app webviews and heavily customised strings land here. If you pasted a log entry, check that you copied the whole header. A truncated string often loses the parenthesised platform section.

Is my User-Agent private information?

Every site you visit receives it, and it is one of the most widely logged headers on the web. Combined with screen size, time zone and language it narrows your identity, which is why browsers froze most of the string. This page reads those values locally and does not store or transmit them.

How do I tell whether a Googlebot visit is genuine?

The string cannot prove it, because anyone can send one. Google documents that its crawlers' reverse DNS names end in googlebot.com or google.com, and Bing's end in search.msn.com. Look the visitor's address up with the [IP Lookup](/ip-lookup) and check the hostname before you trust the header.

Browser Identity

User-Agent Viewer

Your browser sends a User-Agent header with every request. This page shows yours as soon as it loads and breaks it into browser, version, rendering engine, operating system and device type. On Chromium browsers it also reads User-Agent Client Hints, which carry the platform details the frozen User-Agent string no longer includes. Paste any User-Agent from a server log to decode it instead. Everything runs in your browser.

Your browser's User-Agent

…

Or parse another User-Agent string

Loading User-Agent Viewer...

Querying live edge resolvers and network infrastructure...

How to use the User-Agent Viewer

Read your User-Agent string in the first box and click Copy if you need to paste it into a bug report.
Check the parsed fields below it: browser and version, rendering engine, operating system, device type and, for crawlers, the bot name.
On Chrome, Edge or another Chromium browser, read the Client Hints block for the real platform version, CPU architecture and device model.
To decode a different string, paste it into the parse box. The parsed panel switches to that string until you clear it.

What to look for

Frozen Windows version

Browsers report Windows NT 10.0 for both Windows 10 and Windows 11, so the parser shows 10 / 11 for that token. On Chromium browsers the Client Hints platformVersion value settles it: a major number of 13 or higher means Windows 11, and the operating system row is updated to say so.

Bot and client detection

The device type becomes Bot when the string matches a known crawler or HTTP client: Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot, CCBot, Bytespider, curl, Wget, Python and Go HTTP clients, headless Chrome and others. Anything else containing bot, crawler or spider is reported as a generic bot.

What a User-Agent string contains and how the parser reads it

Anatomy of a User-Agent string

A desktop Chrome string reads Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Most tokens are historical: Mozilla/5.0 dates from the Netscape era, AppleWebKit and Safari remain because Chrome forked WebKit, and like Gecko was added so servers written for Firefox would send Chrome the full version of a page.

The parser works through the tokens in a fixed order so that browsers built on Chromium are not misreported as Chrome. Edg/ is checked first for Microsoft Edge, then OPR/ for Opera and SamsungBrowser/, and only then Chrome/ or CriOS/. Firefox and FxiOS come next, Safari is recognised by its Version/ token, and MSIE or Trident/ marks Internet Explorer.

The engine row follows the same logic: Trident, Gecko when Firefox is present, Blink for Chrome, Chromium, Edge and Opera, and WebKit otherwise. Any browser on an iPhone or iPad is reported as WebKit (all iOS browsers), because third-party browsers there have had to use Apple's engine.

Why the operating system row can be vague

Browsers froze most of the User-Agent string to limit fingerprinting. Windows 11 still reports Windows NT 10.0, Chrome on macOS reports 10_15_7 whatever the installed version, and Chrome on Android reports Android 10 with K in place of the device model. The parser shows what the string says and marks the Windows case as 10 / 11.

User-Agent Client Hints are the replacement. Chromium browsers expose navigator.userAgentData, and this page asks it for the high-entropy values platformVersion, architecture, bitness, model and fullVersionList. The result appears as the Client Hints block with Brands, Platform, Architecture, Mobile and, on phones, Model. Firefox and Safari do not implement the API, so the block is absent there.

When you paste a different string into the parse box, the Client Hints and the environment panel are hidden, because they describe your own browser rather than the one that produced the pasted string.

Reading the device type and bot rows

Device type is derived from the string, not the hardware. Tablet means an iPad, a string containing Tablet, or Android without the Mobile token; Mobile means Mobi, iPhone, iPod or Android with Mobile; Desktop is anything else with a recognised operating system; Unknown means no operating system was found, which is common for scripted clients.

If the string matches the crawler list, the device type is Bot and a Bot / client row names it. The list covers search engines (Googlebot, Bingbot, DuckDuckBot, YandexBot, Baiduspider, Applebot), AI crawlers (GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, CCBot, Bytespider), social preview fetchers, SEO crawlers and command-line clients. The check is a substring match, so anyone can send a Googlebot string.

Where the parsed result is useful

Support teams ask for the User-Agent because a bug that appears only on Samsung Internet or Safari on iPadOS is easier to find once the exact browser and version are known. Copy the string from the first box and paste it into the ticket.

Server logs are the other common source. Paste a log line's User-Agent into the parse box to see whether a burst of traffic came from a search crawler, an AI training bot or a script, then decide whether to allow or block it with the Robots.txt Generator & Tester. For a crawler that claims to be Googlebot, look the visiting address up with the IP Lookup and check its reverse DNS name before trusting the header.

What the header cannot tell you

A User-Agent is self-declared. Developer tools, extensions, privacy browsers and every HTTP library let the sender set it to anything, so it is fine for statistics and debugging and useless for access control. Serve the same content to every client and rely on authentication where it matters.

The parser recognises the browsers and bots listed above. An unfamiliar client falls through to Unknown with whatever operating system tokens it can find. Nothing on this page is sent to DNSfinder's servers: the string, the Client Hints and the environment details are read and displayed locally. To see the address your browser connects from, use What Is My IP.

Knowledge Base & FAQ