Browser Info Detector

-
Language
-
Platform
-
Screen

What does your browser actually tell the websites you visit? This page gathers every piece of client-side info your browser exposes, user agent, rendering engine, version, OS, device category, viewport and screen size, timezone, language preferences, do-not-track setting, and your public IP, and lays it out so you can see exactly what is being fingerprinted on every request.

How the detector gathers info

  1. 1

    Read navigator object

    userAgent, platform, language, languages, cookieEnabled, doNotTrack, hardwareConcurrency and more are queried directly from the browser.

  2. 2

    Parse user agent string

    The UA string is matched against a current browser/engine/OS database to extract brand, version and family.

  3. 3

    Query screen and window

    window.innerWidth/Height, screen.width/height, screen.colorDepth, devicePixelRatio for pixel density.

  4. 4

    Detect IP via echo service

    A single request to an IP-echo endpoint returns the public IPv4/IPv6. Nothing is stored: the detection happens fresh every visit.

What the detector shows

Field Source Example
Browser + version UA string + Client Hints Chrome 122.0.6261
Rendering engine Derived from UA Blink
OS + version UA + platform Windows 11, 64-bit
Device type UA + touch support Desktop / Tablet / Mobile
Viewport window.innerWidth / innerHeight 1440 × 820 px
Screen screen.width / screen.height 2560 × 1440 px
Pixel ratio window.devicePixelRatio 2
Color depth screen.colorDepth 24 bits
Primary language navigator.language en-GB
All languages navigator.languages en-GB, en, fr
Timezone Intl.DateTimeFormat Europe/Madrid (UTC+2)
Do Not Track navigator.doNotTrack unset / 1 / 0
Cookies enabled navigator.cookieEnabled true
Public IP Echo endpoint 203.0.113.42

Why this matters

  • Fingerprinting: the combination of these values is often unique enough to identify your browser across sessions even without cookies. See the EFF’s Cover Your Tracks project for a quantified entropy estimate.
  • Privacy leakage: some fields (fonts, WebGL renderer, audio context) add more entropy. Firefox’s “resistFingerprinting” and Tor Browser’s standardised profile reduce these signals.
  • Debugging: when someone reports “it does not work in my browser”, grabbing these fields is the first step in reproducing the issue.

Limitations

  • UA parsing depends on patterns that change with each browser release. A new Edge version might momentarily show up as Chrome until the parser updates.
  • Private relay (iCloud, Warp) masks your real IP; the detector shows the relay IP in that case.
  • Client Hints supersede the UA on Chromium browsers; the displayed UA may be the “reduced” frozen string.

Frequently Asked Questions

No. Every field is detected on page load and discarded when you navigate away. The IP echo service does not persist requests.

User agent and timezone can be spoofed with dev tools or extensions. Screen size, fonts and WebGL renderer are harder to fake without breaking page rendering. Privacy-focused browsers spoof most at the cost of some compatibility.

If you use iCloud Private Relay, Cloudflare Warp, a VPN or a corporate proxy, the detected IP is that intermediary. Different IP-echo services sometimes see different intermediaries if your browser multi-paths.

Even with spoofed UA, servers can often guess via TLS fingerprinting, feature detection (which CSS properties work) and timing quirks. Full anonymity requires something like Tor Browser, not just UA tweaks.

Related Tools