What is my Browser v2.0

About What is my Browser

What Is My Browser is a free detection dashboard that reads the signals your browser exposes the moment a page loads, then explains in plain English what each one reveals about you. Most browser checkers stop at four fields: browser name, version, platform, and the raw user agent string. This one reads dozens of signals grouped into seven categories covering your device, display, network, language settings, and privacy configuration. ToolsPivot built it for anyone who needs to see exactly what a website learns about them, without installing an extension or creating an account.

What the What Is My Browser Tool Detects

The tool reads seven groups of signals directly from your browser as the page renders. There is no button to press and no URL to paste, because every value comes from the session you are already in.

• Browser: Name, version, rendering engine, the full user agent string, and User-Agent Client Hints where your browser supports them.
• Operating system: Name, version, and CPU architecture, including the 64-bit or ARM distinction that a plain user agent string often hides.
• Device: Type, vendor, model, logical CPU cores, approximate device memory, and maximum touch points.
• Display: Full screen size, available screen area, browser viewport, color depth, device pixel ratio, and orientation.
• Location and network: Public IP address, IP version, ISP, ASN, approximate city, connection type, and the local network IP surfaced through a WebRTC probe.
• Language and time: Preferred languages, time zone, locale, and your current local time as the browser reports it.
• Privacy and fingerprint: Cookie status, Do Not Track, Global Privacy Control, the WebGL GPU string, a canvas fingerprint hash, a short fingerprint ID, and an identifiability rating.

Every field carries a short note explaining what that value tells a website about you. If you want the same network-level view from the server side instead, the HTTP header checker shows what a site actually receives with each request.

How ToolsPivot What Is My Browser Works

1. Open the page. JavaScript reads the navigator, screen, Intl, and WebGL objects as soon as the page renders. Results appear without any interaction.
2. Parse browser and system details. The user agent string is parsed for browser, version, engine, and operating system, then enriched with Client Hints for architecture, platform version, and device model where the browser exposes them.
3. Read hardware and display values. CPU cores, device memory, touch points, screen and viewport dimensions, color depth, pixel ratio, time zone, and languages are read directly from browser APIs.
4. Look up your public IP. A browser cannot see its own public address, so the tool calls a keyless HTTPS geolocation service from your browser. That service sees your real IP and returns ISP, ASN, and approximate city.
5. Build the privacy profile. Cookie state, Do Not Track, Global Privacy Control, the WebGL renderer string, and a canvas hash combine into a fingerprint ID and an identifiability rating.
6. Copy or export. Results render into grouped cards with copy buttons on individual values, a full-report copy, and JSON or TXT download.

Key Benefits of the What Is My Browser Tool

• Every value is explained. A device pixel ratio of 2 means nothing on its own. The plain-English note next to it tells you what a site infers from that number.
• Machine-readable export. JSON and TXT downloads drop straight into a bug report, a support ticket, or a QA environment matrix without retyping anything.
• No account and no upsell. There is no sign-up wall, no email gate, and no affiliate product pushed alongside your results.
• Accurate on modern Chromium. Client Hints keep architecture and platform version accurate even as Chrome continues reducing the detail in its user agent string.
• Available in 18 languages. The same detection runs for readers who would otherwise have to interpret technical values in a second language.
• Honest about what it cannot know. Fields that a browser withholds are marked as unavailable rather than filled with a confident guess.

Reading Your Fingerprint Identifiability Rating

The identifiability rating estimates how much your combination of signals makes you stand out, and names the specific values doing the work. Browser fingerprinting does not rely on any single value. It works because the combination of your GPU string, screen dimensions, time zone, language list, and canvas rendering output is far rarer than any one of those on its own.

The rating deliberately avoids a precise "one in X users" figure. Producing an honest number requires a live comparison set of millions of recent visitors, which this tool does not maintain, and quoting one without that data would be guesswork dressed up as a statistic. What you get instead is a rating plus the named signals that pushed it higher, which is the part you can actually act on.

If your rating is high, the usual culprits are an unusual screen resolution, a distinctive GPU model in the WebGL string, or a language list with several entries. Standard hardware in a common configuration produces a lower rating. Checking whether trackers can reach you through other channels is a related exercise, and the email privacy tester covers the equivalent problem in your inbox.

Why Your User Agent No Longer Tells the Whole Story

Chrome has been progressively reducing the detail in its user agent string, freezing version numbers and generalizing platform information. A user agent that once reported "Windows NT 10.0; Win64; x64" with a precise build number now returns a flattened value that no longer distinguishes Windows 10 from Windows 11. Tools that parse only the user agent string report stale or wrong operating system versions as a result.

User-Agent Client Hints are the replacement mechanism. Instead of broadcasting everything in one string, Chromium browsers expose structured values through navigator.userAgentData, and high-entropy details like architecture, bitness, platform version, and device model are available on request. This tool reads both, so the Client Hints panel fills in the accuracy that the reduced user agent string has lost.

Firefox and Safari do not implement Client Hints the way Chromium does. Apple has argued the mechanism adds fingerprinting surface rather than removing it. On those browsers the Client Hints fields show as unavailable rather than being padded with values inferred from the user agent string. If you are testing how a crawler sees your site with a substituted user agent, the spider simulator handles that side of the check.

When to Use What Is My Browser

The tool earns its place whenever you need to describe an environment precisely rather than approximately. "It's broken in Chrome" costs a developer an afternoon. "Broken in Chrome 138 on Windows 11 at 1440x900 with a 1.5 pixel ratio" usually costs ten minutes.

• Filing a bug report. Export the JSON and attach it, so nobody has to ask follow-up questions about your setup.
• Opening a support ticket. Paste the full report instead of guessing at your browser version from memory.
• Auditing your own privacy exposure. See which signals make your browser distinctive before deciding what to change.
• Checking a VPN or proxy. Confirm the public IP and approximate location match what your VPN provider claims.
• Building a QA device matrix. Open the tool on each test device and export a consistent record for every one.
• Verifying a browser update. Confirm the version actually changed after an update, especially on a managed corporate machine.

Real-World Use Cases

Diagnosing a Layout Bug Nobody Can Reproduce

A front-end developer receives a report that a pricing table overflows on one client's laptop but renders correctly everywhere in the team. Asking the client to open this tool and send the JSON export reveals a device pixel ratio of 1.25 and a viewport width that falls between two breakpoints. The bug is reproducible in five minutes once those numbers exist. Testing the fix across other widths is faster with the screen resolution simulator than with physical devices.

Confirming a VPN Is Actually Routing Traffic

A remote contractor connects through a VPN before accessing a client system and wants to verify the connection took effect. The public IP, ISP, and ASN fields show whether traffic exits through the VPN provider or the home ISP. The WebRTC local IP field flags the separate question of whether the browser is leaking a private network address. Anyone comparing exit points across several servers can cross-check them with the bulk geo IP locator, and the free proxy list is useful when testing routes before committing to a provider.

Cutting Support Ticket Round-Trips

An IT help desk repeatedly asks users what browser they are on and receives answers like "the blue e" or "Google." Sending a link to the detection page and asking for the copied report replaces that exchange entirely. The full report includes the operating system version and device model that agents would otherwise need two or three messages to establish. When the reported problem turns out to be connectivity rather than the browser, the internet speed test narrows it down quickly.

Checking Compatibility Before an Enterprise Rollout

Enterprise platforms publish minimum browser requirements, and employees on personal machines often do not know which build they are running. A single page load returns the browser version, operating system version, and architecture needed to compare against those requirements. Teams verifying that internal tools are reachable on mobile hardware can pair the device readings with the mobile-friendly test for rendering behavior.

How This Tool Compares to Other Browser Checkers

Established browser detection sites already report your IP address, ISP, approximate location, screen size, and Do Not Track setting, so those are table stakes rather than points of difference. Dedicated fingerprinting sites go deeper than this tool does on entropy analysis, media device enumeration, and TLS-level signals.

Where this tool differs is in three narrower places. Explanations sit next to each value rather than behind a separate link, so you do not leave the page to understand a field. Results export as structured JSON or TXT files, while most alternatives offer a shareable link or an email form instead of a machine-readable download. And the interface carries no advertising slots or affiliate placements alongside your data, which is not the norm in this category. For an independent read on your public address by itself, the IP address checker covers that in isolation.

Limitations of What Is My Browser

Detection is only as honest as the browser reporting it, and there are several cases where the results deserve caution.

• Values can be spoofed. Extensions, developer tools, and privacy browsers can substitute any user agent string or block individual APIs. The tool reports what your browser claims, not what is verifiably true.
• The IP lookup is a third-party call. Detection itself runs entirely in your browser and none of it reaches ToolsPivot servers, but the public IP lookup is an outbound request to an external geolocation service, which necessarily sees your IP address.
• Geolocation is approximate. IP-based location typically resolves to a city or ISP hub, and can be wrong by a considerable distance on mobile networks or corporate VPNs.
• Client Hints are Chromium-only. Firefox and Safari return unavailable for most high-entropy hints, so those panels will look sparse on non-Chromium browsers.
• Private browsing skews results. Incognito and private windows change cookie behavior and can alter storage-dependent readings, so a private session is not a reliable baseline.
• The fingerprint is not an identity. The fingerprint ID describes this browser configuration on this device. It changes when you update your browser, change your screen setup, or switch devices.

Two adjacent checks worth running separately: the DNS lookup tool for resolution behavior your browser will not show you, and the SSL checker for certificate validity on any site you are diagnosing.

Frequently Asked Questions

Is the What Is My Browser tool free?

Yes, it is completely free with no usage limits. There is no account to create, no email to submit, and no paid tier holding back any of the seven detection groups.

Does ToolsPivot store the data this tool detects?

No. All detection runs in your browser and none of the readings are sent to or stored on ToolsPivot servers. The single exception is the public IP lookup, which is an outbound request to a third-party geolocation service that sees your IP in order to return your ISP and approximate city.

Why does the tool need an external service to find my IP address?

A browser cannot see its own public IP address, because that address is assigned by your network and only visible to servers you connect to. The tool calls a keyless HTTPS geolocation service from your browser so that the service observes your real address directly.

What is a browser fingerprint?

A browser fingerprint is a combination of signals such as your GPU, screen size, time zone, and language settings that together can distinguish your browser from others. No single value identifies you, but the combination is often rare enough to be recognizable across sites without cookies.

Why does the tool not tell me I am one in a million?

An accurate uniqueness ratio requires a live database of millions of recent visitors to compare against, which this tool does not maintain. Rather than publishing a number it cannot verify, the tool gives an identifiability rating and names the specific signals making your browser stand out.

Why are the Client Hints fields empty in Firefox or Safari?

User-Agent Client Hints are a Chromium feature, so Chrome, Edge, Brave, and Opera expose them while Firefox and Safari largely do not. Those fields show as unavailable instead of being filled with values guessed from the user agent string.

Why does my user agent string mention browsers I am not using?

User agent strings carry compatibility tokens from older browsers for historical reasons, which is why Chrome's string references Mozilla and Safari. Servers once used those tokens to decide which version of a page to send, and removing them would break older sites.

What does the local IP address field mean?

The local IP is the private address your device holds on its own network, usually something in the 192.168 or 10.x range. It is surfaced through a WebRTC probe, and seeing it while connected to a VPN can indicate the browser is exposing network details the VPN was meant to mask.

Can websites see everything this tool shows me?

Almost all of it, yes. Every value here comes from APIs and headers available to any site you visit, which is the point of showing them. The one addition is the IP geolocation detail, which any site can obtain just as easily by looking up the address you connect from.

Does this tool detect my browser extensions?

No. Browser security policies prevent websites from enumerating installed extensions directly, so extension detection is outside what any page-based tool can do reliably. Some extensions are indirectly detectable through the changes they make to a page, but that is not something this tool attempts.

Why do my results change between visits?

Browser updates, window resizing, connecting through a different network, and switching between private and normal windows all change one or more readings. The fingerprint ID describes a configuration rather than a person, so it shifts whenever that configuration does.

Does the tool work on phones and tablets?

Yes, and mobile devices often return more detail than desktops through Client Hints, including the specific device model on Android. Touch points, orientation, and pixel ratio are read the same way on mobile as on desktop. If you are checking whether a site you visit is safe on mobile, the website safety checker is the tool for that.

Related Tools You Might Like

Flag Counter Text to Binary Change Text Case Binary Translator Website Hit Counter HTML Compressor