🔧 TL3 Tools

What This Page Reports

This page shows detailed information about your browser and device by reading properties available in your browser environment. It detects your browser name and version, operating system, device type (desktop, tablet, or phone), screen and viewport dimensions, color depth, language preferences, time zone, and your full user agent string. Your public IP address is detected using a free STUN-based service that requires no server-side code.

Is My Data Private?

Yes. All device information is read directly from your browser's JavaScript environment — nothing is stored or transmitted. Your IP address is obtained through a STUN lookup, which is the same technique used by WebRTC applications to discover public IP addresses without routing traffic through a server. No data from this page is saved or sent to any log.

What Each Field Tells You

• Browser and version — identified from the user agent's product token, e.g. Chrome/126.0.0.0 maps to Chrome 126. Screen scrapes and QA tickets rarely mention the browser version, and this field pins it down.
• Operating system — the Windows NT 10.0 style token maps to Windows 10/11, and Mac OS X 14_5 becomes macOS 14.5. Useful when reproducing an issue that only appears on one platform.
• Screen vs. viewport — screen resolution is your monitor's full size, while the viewport is the area actually visible inside the window (minus toolbars and scrollbars). A 2560×1440 monitor can report a 1519×698 viewport when the window is half-tiled — this gap is a classic cause of "it looked fine on my machine" bugs.
• Color depth — bits per pixel (usually 24). 8-bit or lower values flag environments that will render gradients and shadows poorly.
• Language and time zone — read straight from navigator.language and Intl.DateTimeFormat defaults, so you can verify locale-specific formatting without guessing.
• User agent — the raw string every one of the above derives from, kept visible for manual inspection.

How the IP Lookup Works

Your public IP is discovered through a STUN request — the same mechanism WebRTC uses to establish calls. The browser asks a STUN server "what's my public address?", the server reads the source of the incoming packet, and reports it back. Your traffic never passes through that server afterward, and no custom backend is involved: the lookup is a single request served by infrastructure any WebRTC app already relies on. If the request fails (an ad blocker or strict network policy can block it), the page simply shows the address as unavailable.

What This Page Is Not

• Not a tracker. Everything is read client-side from properties your browser already exposes; nothing is logged or stored on a server.
• Not a fingerprinting tool. It reports the obvious, user-visible facts, not the subtle canvas, font, and timing signals used to build persistent device fingerprints.
• Not a network diagnostic. The IP shown is your public egress address — if you are behind a VPN or proxy, that is the address the internet sees, not your local one.
• Not infallible. User agents can be overridden, and some fields (like screen size) can be faked. Treat the output as a snapshot of what your browser reports, which is exactly what remote sites and analytics see.

Common Questions

Why does an iPhone say "Safari" even though I installed Chrome? On iOS every browser must use Apple's WebKit rendering engine underneath, so Chrome, Edge, and Firefox present the same Safari core while keeping their own interface and bookmarks. The detector reads the engine honestly, which is why an iPhone can report Safari even when the app in front of you is Chrome.

Why does the IP here differ from what another website shows? Different sites may display the address of their own proxy or CDN hop, while this page reports your immediate egress point. Corporate VPNs, carrier-grade NAT, and private relays all change the public address you appear to come from, so mismatches between tools are normal, not errors.

Why does my screen resolution look smaller than my monitor's spec? Browsers report CSS pixels, not physical ones. A 2560×1440 Retina display often reports roughly half that because the operating system scales everything by two; zoom level and display scaling both change the number. The figure is still what layout engines actually use, so it is the honest number for web design.

Is knowing these fields a privacy risk? Alone, each field is trivial; together they narrow you down among thousands of visitors, though not to a personal identity. That combination is what "remember me" and marketing trackers rely on when they pair it with cookies and login state — worth knowing before you share a screenshot of this page.

How Detection Works Under the Hood

The detector reads navigator.userAgent once and scans it left to right with a fixed priority list, because token order is not standardized. It tests for Firefox first and excludes Seamonkey, an old Mozilla descendant that also reports "Firefox" in its string; Chrome is accepted only when Edge (Edg) and Opera (OPR) markers are absent, since those engines began life as Chromium forks. This ordering is the classic source of misread mobile browsers — the same reason the tool shows both the parsed result and the untouched raw string, so you can audit the guess yourself.