What My Browser Reveals About You
Your user agent, headers, screen, time zone and more: what any page can read without asking
Reading your browser
Reading what your browser hands over ...
Permissions and sensors
Reading permissions and sensors ...
Learn more
Guide and answers to common questions about What My Browser Reveals
What your browser tells every website
You do not have to log in, accept a cookie banner or press an allow button for a website to learn a lot about you. The moment a page opens, your browser sends headers with the request, and the page's scripts can read dozens of properties: which browser and system you run, which languages you prefer, how big your screen is, which time zone your clock uses and more. This page shows those values for your own browser, in cards, with one line each on what a site can do with the value.
Reading these values is normal, and most sites use them for ordinary things such as picking a language or a layout. The point is to show how much is readable without permission, because the same values, combined, are what browser fingerprinting is built from.
What the user agent string is
The user agent is a line of text your browser sends with every request, and that scripts can read as navigator.userAgent. It names the browser, its engine and your operating system. It looks odd because of history: browsers started copying each other's strings so that sites written for one browser would still work in another, which is why almost every user agent begins with "Mozilla/5.0" and a Chrome string mentions Safari and Gecko too.
The string has also been a rich source for tracking, so browsers are reducing it. Chrome cuts the version to the major number followed by 0.0.0, macOS is written as 10_15_7 whatever version is installed, Windows 10 and 11 both appear as "Windows NT 10.0", and Android shows a placeholder device name. Safari and Firefox freeze similar parts. The parser on this page says "unknown" instead of guessing when nothing matches.
The details moved. In Chromium browsers, User-Agent Client Hints split the information into basic values sent by default and high-entropy values (full version, architecture, device model) that a site has to ask for. The client hints card asks for them the way any script would.
What each card reveals
Every row on the page is one value. Here is what the groups are and what they are typically used for, by sites and by trackers.
- Seen by the server: your IP address, the country our network provider derives from it, and the request headers our server received, such as the user agent, accept-language and the client hint headers. Any server that serves you a page sees the same kind of information before it sends a single byte back.
- Browser and system: the parsed browser and operating system, the platform string, your language list, Do Not Track and Global Privacy Control, the number of logical processors, a rounded memory class, touch points, and the automation flag that bot detection looks at.
- Screen and window: screen size, colour depth, pixel ratio, the window size and orientation, and settings such as dark mode and reduced motion. Sites use them for layout; fingerprinting scripts use the combination.
- Time and locale: your time zone, UTC offset, locale and number and date formats. A time zone that does not match the country of your IP address is a classic sign that a VPN is in use.
- Connection and battery: connection type, downlink and round-trip time, charge level and charging state, in browsers that expose them.
- Client hints: the detailed values described above, in browsers that support them.
What fingerprinting does with it
A fingerprint is a stable identifier computed from many small values. Each value on its own is shared with many other people; a language list, a screen size, a number of processors and a time zone together may be shared with very few. A tracker that computes the same fingerprint on many sites can recognise you without any cookie, so clearing cookies does not remove it. Scripts usually add values that are not on this page, such as how your graphics and audio hardware render test signals and which fonts are installed, which adds more.
How unique your browser looks depends on the people you are compared with, so a single page cannot give an honest uniqueness percentage, and this one gives no score. It shows the inputs. A rare value, such as an unusual language list, a custom window size, or a Linux user agent with a macOS platform string, makes you easier to pick out; a value most people share makes you harder to pick out.
What the server sees and what JavaScript sees
A site learns about your browser in two ways. The server reads the headers of each request and the IP address it came from. Those arrive before any script has run, and turning JavaScript off does not block them. The user agent, the language list and the default client hints are in them.
JavaScript on the page can read much more: the screen, the window, the time zone, the battery, the connection, the processor count and the high-entropy client hints. Blocking scripts hides those but leaves the headers. A privacy tool that changes only one of the two leaves the other as it was, so the two views can disagree on this page. If the header user agent differs from navigator.userAgent, something is changing one view and not the other.
This page makes one request to our own server to show you its view. It reads the allow-listed headers in the card, your IP address and the country our network provider derived from it, and sends them straight back. Cookies and other headers are never read, and nothing is stored or logged. Everything else is read in your browser and goes nowhere.
How to reduce what your browser reveals
You cannot hide everything, since a site must receive some information to work at all. You can reduce how unusual you look, and block the scripts that collect the values.
- Firefox: the privacy.resistFingerprinting setting (in about:config) makes Firefox report common values, for example a rounded window size and a generic time zone. It can break sites that expect real values. Enhanced Tracking Protection can also block known fingerprinting scripts.
- Brave: Shields block many trackers and fingerprinting scripts and, for some APIs, return slightly randomised values so that the same fingerprint does not repeat across sites.
- Tor Browser: it aims to make all its users look the same, with one user agent and window sizes rounded to fixed steps. It is the strongest option; the price is a slower connection and sites that may ask for extra verification.
- Do Not Track and Global Privacy Control: both are only requests. Do Not Track is ignored by most sites. Global Privacy Control is legally meaningful in some places, but nothing technical enforces it.
- A VPN changes your IP address and the country derived from it, not your user agent, language, screen or time zone. Use the IP Leak Test and the WebRTC Leak Test to check what your address looks like.
- Fewer extensions and settings: every unusual extension or setting can add to your fingerprint, and a privacy extension few people use can make you stand out more than it hides.
Permissions and sensors
The Permissions API lets a page ask the browser what state a feature is in, without triggering a prompt. Granted means this site may use the camera, microphone, location, notifications or clipboard without asking again; prompt means the browser would ask first; denied means it was refused. Some names are not known to every browser, and the page then says so. This page only reads the states and never requests a permission.
Some sensors need no permission at all. On Android Chrome, a page can read motion and orientation events with no prompt, while iOS Safari asks first. Research has suggested that such readings can reveal taps and typing patterns, and that sensor imperfections can serve as a fingerprint, so browsers have been restricting access. Whether a given page abuses them is a separate question.
Media device lists are another case: without a permission a page can still count cameras, microphones and speakers, but the names stay empty. Whether WebUSB, WebHID, Web Serial and Web Bluetooth exist is also readable, but each one shows a chooser, and a site sees only the device you pick.
Related tests on Exposy
This page covers what your browser hands over by design. The Cookie & Tracker Test checks whether your browser blocks third-party cookies and well-known trackers, and what canvas, audio and font probing can read. The IP Leak Test shows the public IPv4 and IPv6 addresses sites see, and the WebRTC Leak Test checks whether the browser reveals an address outside your VPN.
Frequently asked questions
What is my user agent?
It is the first long string in the Browser and system card, and the first header in the Seen by the server card. It is the text your browser sends with every request to say which browser and operating system it claims to be. Copy it with the Copy as text button if a site or a support team asks for it. The string is whatever the browser chooses to claim, so it can be reduced, frozen or changed.
Why does my user agent say Mozilla, Safari and Gecko when I use Chrome?
For historical reasons. Browsers copied parts of each other's strings so that sites that only served content to a certain browser would still work, and the old words stayed. Today "Mozilla/5.0" is at the start of almost every user agent, and none of those words says which browser you use. The browser name and version are the parts near the end.
Why does it say macOS 10.15.7 or Windows NT 10.0 when I run something newer?
The browsers decided to stop telling sites the exact version. Safari and Chrome write macOS as 10_15_7 whatever macOS you have, and Windows 10 and Windows 11 both appear as "Windows NT 10.0". Sites that need the real version can ask for it as a client hint, in browsers that support them, as shown in the last card.
Can websites see my battery?
Only in browsers that still expose the Battery Status API, which are mostly Chromium based ones, and only on secure pages. Firefox and Safari do not. No permission prompt is involved. Level and charging state together were once used to recognise the same device for a short time.
Does incognito or private mode change any of this?
Almost nothing here. Private mode stops the browser from saving history and cookies after you close the window. It does not change your IP address, user agent, languages, screen, time zone or client hints, so a site sees the same values as in a normal window.
Can a website see my real location?
Not your precise location. Reading your position needs a permission prompt, and this page does not ask for it. A site can estimate a region from your IP address, which is wrong for VPN users and often only right to the city or region, and it can see your time zone and language.
Is anything on this page sent to or stored by Exposy?
Our server sees the one request the page makes to it, answers with the headers it received, your IP address and the derived country, and keeps nothing. Everything else is read in your browser and stays there. The Copy as text button uses your clipboard and sends nothing anywhere.
Can I change my user agent?
Yes, with developer tools or an extension. It only changes what the user agent says and often leaves the client hints and platform string untouched, which creates a mismatch that is itself unusual and makes a fingerprint more distinctive. For a quick compatibility test that is fine; as a privacy tool it works poorly.
Does this page ask for my camera, location or other permissions?
No. It only reads the state of each permission, which needs no prompt, and it counts media devices without asking for them. On iOS, motion readings need a permission, so there is a button that you press yourself; nothing is requested otherwise.
Does Do Not Track protect me?
Hardly. It is a request, and a site is free to ignore it, which most do. Global Privacy Control is the newer signal, and it is backed by law in some places, but it is also only a request. For real protection, block trackers and third-party cookies, and reduce what scripts can read.