A browser version checker is a page that reads the identity fields your browser chooses to expose and shows them to you in plain, copyable form. The honest version of this tool does not pretend to map a long compatibility string to a single product name with absolute confidence, because the modern web treats user-agent strings as opaque historical tokens that often mention several browser names at once. Instead, the What Browser Am I Using tool shows the browser-reported brand list from User-Agent Client Hints, the platform, the mobile hint, the language, the cookies-enabled flag, and the complete raw navigator.userAgent string, and it explicitly says "Browser name not exposed" when the browser does not provide meaningful brand data. Every field is read locally after the page loads, nothing is uploaded, and the only thing that touches your clipboard is the report you choose to copy. Used that way, the tool is a fast way to check what your browser is actually telling a website about itself, which is exactly the information support teams need when reproducing a bug.
What the browser version checker shows
The What Browser Am I Using page is organized into a small set of clearly labeled fields. Each one comes from a different browser API and carries a different meaning, so reading them as a single answer would be misleading.
The reported brand list comes from navigator.userAgentData.brands when the browser implements that interface. Browsers may include a GREASE placeholder called "Not A Brand" designed to prevent code from assuming a fixed brand list or order. The widget filters only that placeholder-like name and preserves the remaining brand and version pairs in the order the browser provides them. When the interface is missing or no meaningful brands remain, the page prints "Browser name not exposed" rather than inventing a result from fragile token order in the legacy user-agent string.
Platform uses the client-hint platform when available and otherwise falls back to navigator.platform. Both values can be reduced, legacy-formatted, frozen, or chosen for compatibility reasons, so a platform label alone is not strong evidence of the exact operating system build. Mobile hint is shown only when the client-hint interface supplies a boolean, and it is not a screen-size guess, device model, touch-capability test, or proof that the browser runs on a phone.
Language comes from navigator.language and may differ from your content preferences, physical location, keyboard layout, or account settings. Cookies enabled reflects navigator.cookieEnabled and indicates the browser's general reported setting, not that every cookie write will succeed. Third-party cookie restrictions, partitioning, storage access policy, private mode, expiration, domain and path rules, consent choices, extensions, and enterprise controls can still block a specific cookie. The page does not create a test cookie or infer tracking availability.
How to read the report step by step
- Open the What Browser Am I Using tool in the same browser window you want to inspect.
- Review the reported brand list and note when the page honestly says the browser name is not exposed.
- Compare platform, mobile hint, language, cookie setting, and the raw compatibility user-agent string side by side.
- Select Copy browser report and attach it with reproduction steps when troubleshooting, without treating it as authenticated identity.
Field-by-field: what each one actually means
| Field | What it shows | What it does not prove |
|---|---|---|
| Reported brands | Brand and major version pairs from navigator.userAgentData.brands | Installed application, security state, or feature support |
| Platform | Client-hint platform, or navigator.platform as a fallback | Exact OS version, kernel, or architecture |
| Mobile hint | Boolean from the client-hint mobile field | Screen size, device model, or touch capability |
| Language | navigator.language | Content preferences, account locale, or physical location |
| Cookies enabled | navigator.cookieEnabled general flag | That a specific cookie can be stored |
| Raw user-agent | The full navigator.userAgent string | Authenticated identity, update channel, or patch level |
Reading these fields together matters because each one is a different signal. A support engineer looking at a report that says "Brand: Chrome; Platform: Windows; Mobile: false; Language: en-US; Cookies: true" can tell that the browser is reporting a desktop Chrome on Windows with English as a primary language, but they cannot tell from the report alone whether the browser is fully updated or whether an extension is interfering with the page. For a quick check of whether your screen layout matches what the browser reports, the Screen Resolution Checker reads the screen, viewport, and device pixel ratio separately.
Why the page sometimes says "Browser name not exposed"
Some browsers do not implement the navigator.userAgentData interface at all, and some that do only return the GREASE-style "Not A Brand" placeholder. A growing number of privacy-focused browsers also choose to reduce the brand information they expose. The tool deliberately avoids maintaining a large user-agent pattern table, because traditional user-agent strings often include historical compatibility tokens and several browser names at once. A Chrome-family string can mention Mozilla, AppleWebKit, Chrome, Safari, and other tokens without meaning that five separate products are running, and mapping those strings to a confident product and exact version requires a maintained parser that can still be defeated by reduction, spoofing, embedding, or privacy settings.
When the interface is absent, or when filtering the placeholder leaves nothing meaningful, the page prints "Browser name not exposed" rather than guessing. That fallback is part of the reliable contract: show browser-supplied fields transparently, remove only the known meaningless brand placeholder, preserve raw values, and use an honest fallback when a product name is not exposed.
What the raw user-agent string can and cannot tell you
The raw user-agent value is preserved because support teams and bug reports often request it. Treat it as an opaque compatibility string, not authenticated identity. Automation, webviews, privacy tools, proxies, extensions, developer overrides, and remote browser services can change it. The report cannot prove the installed application, executable signature, update channel, security patch level, device owner, or whether the string has been modified.
That is also why the FAQ for the tool answers the question "Why can the user-agent string contain several browser names?" with the straightforward explanation that it is a compatibility string with historical tokens, and those tokens are not a reliable list of installed or running browsers. If a support thread asks for the user-agent, paste the raw value, not a one-word summary, and add the surrounding context.
Using the copied report for troubleshooting
When a website is misbehaving, copy the browser report and attach it together with the failing URL, the time of the attempt, the steps to reproduce, screenshots, the extension state, and whether private mode changes the behavior. Pasting the report into a private scratch buffer such as the Online Notepad makes it easy to annotate each field before sending it to a support thread.
If an exact supported-browser decision matters, the report alone is not enough. Use feature detection for the required Web API and consult the product's own About or update screen in a separate step. A reported brand alone does not demonstrate support for a particular feature or security state. The narrow, reliable contract of the What Browser Am I Using tool is to show browser-supplied fields transparently, filter only the known meaningless brand placeholder, preserve raw values, and use an honest fallback when a product name is not exposed, and that contract is what makes the copied report trustworthy enough to attach to a real bug report.