What Browser Am I Using?

See what your browser tells every website about itself; only the user agent reaches our server.

What the server parsed

What your browser told our server about itself, in the User-Agent header it attached to this request plus the client hints it chose to send.

Browser
ClaudeBot 1.0
Engine
WebKit 537.36
Operating system
Not recognised
Device class
bot
Languages
Not sent
Raw User-Agent
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)

Your browser sent no Sec-CH-UA client hints. Firefox and Safari do not implement them, and Chromium sends only the low-entropy ones unless a site asks for more.

What only your browser knows

Read from browser APIs on your device after this page loaded.

Reading the values your browser exposes…

Only the top section reached our server. Your browser sends the User-Agent header and any client hints with every request, so we parse those at the edge. Everything below the line is read in your browser and written straight into this page. No request carries it back.

What we send to the server and what we do not

The only value the server sees is the User-Agent header, because your browser attaches it to the request for this page. We parse it at the edge and render the result. Every other row on this page is filled in by JavaScript reading the browser API and writing the value into the DOM. No fetch carries it back.

Why some rows say “unavailable”

Firefox with resistFingerprinting enabled, the Tor Browser, and Safari with Lockdown Mode all block or normalize several of these APIs on purpose. A blank or generic value there is the privacy feature working, not a failure of the page.

The advanced section

The WebGL renderer string names your GPU, which is one of the more identifying signals a page can read. It is useful when you are debugging graphics problems and useless otherwise, so it stays behind a click. Reading it does not send it anywhere.

About this tool

This page shows what your browser reports about itself. The server parses only your User-Agent header, which names the browser, its version, and the operating system. Everything else is read on your device by JavaScript and stays there, including screen size, languages, timezone, and touch support. The WebGL renderer sits behind an opt-in click. Several are frozen or spoofed by design, so read them as claims.

How to read the result

Browser, version, engine
The name and version of your browser and the engine that draws the page, parsed from the User-Agent string and the Sec-CH-UA client hints where the browser sends them. Chromium freezes parts of the legacy UA string, so the client hints are the more accurate source.
Operating system and platform
The system your device runs, from the UA string plus Sec-CH-UA-Platform. This field can be wrong by design: macOS reports a frozen version, and iPadOS identifies itself as macOS in desktop mode.
Screen, viewport, device pixel ratio, color depth
Your screen size, browser window size, and pixel density, read from window.screen and window.innerWidth/innerHeight. Together they are a moderately identifying combination, which is why some privacy browsers round or spoof them.
Languages
The languages you told your browser you read, in order of preference. The same list is navigator.languages, and it goes out as the Accept-Language header on every request.
Timezone mismatch flag
We compare the timezone from Intl.DateTimeFormat().resolvedOptions().timeZone against the timezone we infer from your IP. A mismatch is normal when you travel or use a VPN, and it is one of the cheapest VPN detection signals a site can run.
DNT and GPC
Two signals that ask sites not to sell or share your data. Global Privacy Control counts as a valid opt-out under CCPA/CPRA and with some EU regulators, while the older Do Not Track header binds nobody and most sites ignore it.
Cookies enabled, touch support
Whether your browser accepts cookies, from navigator.cookieEnabled, and whether the device reports touch events or a coarse pointer. Touch support does not prove a touchscreen is in use.

Questions people ask

What is a user agent string?
It is a text header your browser sends with every request, naming itself, its version, and the operating system. It exists so servers can adapt responses. It is also trivially spoofed, so treat it as a claim rather than a fact.
Can a website see my exact device model?
Not from the browser on desktop. On Android, the UA string often contains the marketing model name, so the model is visible. On iOS every iPhone reports the same string, and the model can only be guessed from the screen size and pixel ratio.
Does this page fingerprint me?
No. Fingerprinting means combining many signals into a stable identifier and storing it. We read the values, render them, and store nothing. Canvas and audio hashing are not run at all, and the WebGL renderer is behind an explicit opt-in click.
Why does my Mac report macOS 10.15 when I am on a newer version?
Safari and Chromium both froze the macOS version in the user agent for privacy reasons. Every recent Mac reports the same value, which removes one identifying bit. The real version is not exposed to web pages.
How do I change my user agent?
Browser developer tools let you override it per tab, and extensions can set it globally. Be aware that a UA which does not match your other signals, such as claiming iPhone while reporting a 2560-pixel wide screen, is more identifying than the honest one.

Related

Last reviewed 2026-09-05.