Browser Information & User Agent Viewer

Explore live browser-reported information, User-Agent strings, optional Client Hints, privacy signals and passive API exposure without pretending UA labels are verified device identity.

View Browser Information

Reading browser-reported information locally…

These values come from your current browser session, not from hardware inspection. A browser may reduce or spoof its identification data. Sensitive User-Agent Client Hints are optional and requested only after you click.

Current browser snapshot

BROWSER-REPORTED

Browser (UA identification)—

OS (reported / estimated)—

Primary language—

Cookies setting—

Network indicator—

Do Not Track—

Browser/OS labels are interpretations of claims, not independently verified hardware or an internet connectivity test. “Cookies enabled” does not guarantee that every cookie can be stored.

Session & privacy signals

NO PERMISSION PROMPTS

All reported languages—

Global Privacy Control—

Secure context—

Browser platform string—

Display scale (devicePixelRatio)—

Viewport (CSS pixels)—

Preferred color scheme—

Reduced motion preference—

Raw User-Agent string

UNCHANGED VALUE

—

This is navigator.userAgent as exposed to this page. It can be shortened, modified, or spoofed, and may differ from server-observed headers.

User-Agent Client Hints

OPTIONAL DETAIL

Low-entropy hints are displayed automatically where available. Extra hints (architecture, OS version, device model and full browser versions) are requested only if you choose; the browser or its policy may withhold them.

Client Hints API—

Brands reported—

CH platform—

Mobile hint—

ArchitectureNot requested

BitnessNot requested

Platform versionNot requested

Device modelNot requested

WoW64Not requested

Full-version brand listNot requested

Nothing has been requested beyond low-entropy data. Requesting extra hints may expose more identifying details in your local report.

Browser API exposure checks

PASSIVE CHECKS

“Exposed” only means an interface/property exists. It does not confirm permissions, accessible devices or successful API operation. No camera, microphone, location, GPU context or connection is activated here.

Privacy: This checker runs in your browser and does not intentionally transmit its report. Normal website requests, hosting logs and any existing site analytics are separate from the checker. Reports can contain identifiable browser details—review them before sharing.

What Is a Browser Information & User Agent Viewer?

A browser information viewer reads the settings and identity strings that your current browser makes available through web APIs. This page shows the raw navigator.userAgent, language and network indicators, privacy preferences, browser API exposure, and (where supported) User-Agent Client Hints. It does not inspect physical hardware or guarantee a browser or OS identity. Most browser versions intentionally reduce the detail available to websites.

How to Use the Browser Information & User Agent Viewer

Open the tool: the current browser’s reported values populate automatically. No login, installation or permission prompt is required for the main checks.
Read the snapshot: review the browser and OS labels as UA-derived estimates, then check primary language, cookie setting, network indicator and Do Not Track.
Inspect session signals: the panel lists language preferences, Global Privacy Control where exposed, secure-context status, viewport size, color-scheme preference and reduced-motion setting. The online indicator does not perform an internet reachability test.
Check the raw UA: compare navigator.userAgent against the readable labels. Use Copy User Agent if a support form asks for that exact text.
Read Client Hints: browser brands, CH platform and a mobile hint appear automatically only if your browser supports User-Agent Client Hints. Request Extra Hints is optional; use it only if you want details that may include platform version, architecture, model or full browser versions. A browser can withhold any of these values.
Check API exposure: “EXPOSED” means a browser property exists, not that a feature is permitted or fully working. This test does not turn on the camera or microphone or request your location.
Re-check and export: choose Re-check Session after changing settings (this also clears optional high-detail values). Use Copy Technical Report or Download JSON for troubleshooting, and inspect sensitive identifiers before sharing.

How It Works

The raw identification value comes from navigator.userAgent. A small heuristic identifies familiar browser-family and OS tokens, but these labels are explicitly estimates because a browser may change, reduce or impersonate those tokens. Separate navigator properties supply language, cookie and network indicators. A media preference query checks color-scheme and reduced-motion settings. The capability table checks for the presence of browser interfaces without exercising their operations.

On browsers that expose navigator.userAgentData, low-entropy brand, platform and mobile hints are displayed as reported. More detailed UA Client Hints require a deliberate button click and use getHighEntropyValues(). This method can return only a subset because of browser support or Permissions Policy; a missing value is shown as missing rather than guessed. The exported JSON is assembled locally from the visible snapshot.

Understanding Your Results

Browser and OS: these are UA-derived estimates or a platform claim from Client Hints. They are not independent verification and may be misleading on browser wrappers, desktop-mode iPads or spoofed UA strings.
Language list: the preference order reported by the browser, not proof of physical location.
Cookies Enabled: a browser setting indication. Site-specific storage restrictions, private browsing and third-party cookie blocking can still apply.
Online Status: a connectivity hint based on browser/OS reports, not a ping or speed test. It can say online during an internet outage.
Do Not Track / Global Privacy Control: separate preference signals where a browser exposes them. A missing signal is not proof a privacy setting is disabled.
Client Hints: “Not exposed,” “Not requested,” and “Not returned” are distinct. An empty model or withheld full version is not an error or a reason to invent information.
API exposed: indicates a JavaScript interface exists only. Permission, connected devices, working hardware and secure-context restrictions may still determine usability.

Browser Limitations

Modern User-Agent reduction and privacy defenses intentionally omit or generalize OS versions, device models and browser build information. UA Client Hints have limited cross-browser support and high-detail values may be restricted by Permissions-Policy. Some browsers masquerade as another for compatibility. Do not use a UA-based guess as proof of hardware, security posture or exact browser identity. Screen and interface values can change when a page is resized or browser preferences change, so use Re-check when necessary.

Common Mistakes to Avoid

Reading “Chrome-family” as verified Google Chrome: several Chromium-based browsers use compatible tokens; detection is heuristic.
Assuming “Online” confirms internet access: this page does not contact an external test service.
Assuming API exposure equals permission: a present geolocation or media interface may still be blocked or unavailable.
Treating absent high-entropy hints as a browser bug: unsupported browsers and permission policies can withhold them intentionally.
Sharing a detailed report carelessly: user-agent strings and optional high-detail hints may reveal identifiable environment details.

Frequently Asked Questions

Why might my detected browser be wrong?

The readable name comes from User-Agent patterns, which are not guaranteed to identify the actual browser. Compatibility tokens, privacy-reduced strings, custom User-Agent overrides and embedded browser wrappers can all change the result. Check actual behavior with feature tests instead of assuming the label is definitive.

Is my user agent string sent to a server by this tool?

The checker’s JavaScript does not intentionally upload its report or request an external identification service. However, normal page requests already reach the hosting server, and browsers ordinarily send a User-Agent header during HTTP requests. Hosting logs, site analytics and other site code are separate from this tool. Copying or downloading a report does not upload it from the checker.

Why does the user agent string look so long and technical?

Compatibility tokens accumulated over decades, so a modern UA string can contain names associated with multiple browser families. Newer browsers also replace some detailed tokens with reduced values to limit fingerprinting.

What does "Do Not Track" actually do?

It is a historically voluntary preference signal that some browsers exposed; website support and requirements vary. It is not a guarantee that tracking stops, and a missing Do Not Track value does not imply that all privacy controls are off.

Can websites see more about my browser than what's shown here?

Potentially yes. Other sites can check additional APIs or receive information in ordinary HTTP requests, subject to browser protections and permissions. This page focuses on a limited, privacy-aware set of signals and does not attempt an exhaustive fingerprint.

Conclusion

This viewer helps you copy what your browser reports for troubleshooting, compare UA and Client Hints, and see basic capability exposure without activating sensitive hardware. Treat browser and OS labels as claims and estimates rather than proof. To test specific APIs, use Browser Feature Detection.