MyDevice.info
Guide and glossary

What browser and device parameters mean

This glossary explains the most important values shown by MyDevice.info. It is written for technically curious users who know the basics of browsers, devices, and networks, but want practical examples instead of raw jargon.

Network and location parameters

Public IP address

The public IP is the address websites see when your browser connects to them. It may belong to your home internet, mobile carrier, workplace, VPN, proxy, or cloud gateway.

Example: 203.0.113.42 or 2001:db8::8a2e:370:7334

ISP, country, city, region

These are inferred from public IP geolocation databases. They are useful for checking whether your VPN exits in the expected country, but they are not GPS-grade location.

Example: ISP "Orange Polska", Country "Poland", City "Warsaw"

WebRTC local IP

Older WebRTC behavior could reveal local network IPs. Modern browsers often hide or randomize this value to reduce leaks.

Example: "Hidden by browser privacy protections" or 192.168.1.23

DNS leak indicator

Browsers do not directly expose your DNS resolver. A DNS leak test usually compares resolver location with your expected VPN or network path. MyDevice.info explains the limitation instead of inventing a false result.

Example: "Browser DNS servers are not exposed"

HTTP and TLS information

JavaScript can see whether the page is loaded with HTTPS and sometimes the negotiated protocol, such as HTTP/2 or HTTP/3. It cannot read your exact TLS version in normal browser APIs.

Example: HTTPS, H2

VPN or datacenter heuristic

This is a best-effort signal based on the IP owner or ASN. It can flag cloud hosting and known proxy-like networks, but it cannot prove whether a VPN is active.

Example: "Possible VPN/proxy/datacenter ASN"

Device and system parameters

Device type

Device type is inferred from user agent hints, viewport, touch support, and pointer type. It helps explain why a site may serve a mobile or desktop layout.

Example: Desktop, Mobile, Tablet

OS and version

The operating system comes from browser-provided user agent data. Some browsers intentionally reduce exact version detail for privacy.

Example: Windows 10/11, macOS 14, Android 15

CPU architecture and logical cores

Architecture hints can show whether the device is ARM or x86. Logical cores indicate parallel processing capacity available to the browser.

Example: arm64, 8 cores

Approximate RAM

Some browsers expose rounded device memory. It is deliberately coarse, so it should be treated as an estimate, not an exact hardware specification.

Example: 8 GB (rounded)

GPU renderer

WebGL may reveal GPU vendor and renderer strings. These help diagnose graphics issues, WebGL support, and rendering differences.

Example: ANGLE (NVIDIA GeForce RTX 3060 Direct3D11)

Battery state

If supported, the Battery API can show charging status and approximate level. Many browsers removed or restrict it because battery data can contribute to fingerprinting.

Example: 87%, charging, charge time unknown

Screen and display parameters

Screen resolution

The total device screen size in CSS pixels. It can differ from physical pixels because high-density displays use scaling.

Example: 1920 x 1080

Window size

Outer and inner window dimensions show the browser chrome and the actual page viewport. This is useful for responsive layout debugging.

Example: outer 1440 x 900; inner 1424 x 782

Device pixel ratio

The ratio between CSS pixels and physical display pixels. High values usually mean a Retina or high-DPI screen.

Example: 1, 1.5, 2, 3

Color depth and HDR

Color depth describes how many bits are used for color. HDR support indicates whether the browser and display may handle high dynamic range content.

Example: 24-bit, standard dynamic range

Browser parameters

User agent

The user agent is a long browser identification string. It is still useful, but many browsers reduce or freeze parts of it to limit passive fingerprinting.

Example: Mozilla/5.0 ... Chrome/126.0.0.0 Safari/537.36

Browser name and version

Modern browsers may expose structured brand and version data through User-Agent Client Hints. This is usually more reliable than parsing the old user agent string.

Example: Google Chrome 126, Chromium 126

Languages

Browser languages influence date formats, spell checking, localization, and sometimes search or content targeting.

Example: en-US, en, pl-PL

Cookies and third-party cookies

Cookie status shows whether browser storage can persist small values. Third-party cookie behavior is increasingly restricted by browsers and privacy settings.

Example: Cookies enabled; third-party status not directly exposed

Do Not Track

DNT is a browser preference that asks sites not to track. It is only a signal; websites decide whether to respect it.

Example: 1, 0, unspecified

Private mode heuristic

Private or incognito mode is not officially exposed. Tools can only infer weak signals such as unusual storage quotas or blocked storage.

Example: No strong private-mode signal

Fingerprinting parameters

A fingerprint is not one magic identifier. It is a combination of many small signals. The more unusual the combination, the easier it can be to distinguish one browser from another.

Canvas fingerprint

The browser draws text and shapes into a hidden canvas, then hashes the image. Differences in fonts, GPU, antialiasing, and OS rendering can change the hash.

Example: f4a6c1e7b2d09a31...

WebGL fingerprint

WebGL output and renderer strings can vary by GPU, driver, browser, and operating system. This can be useful for debugging and also contributes to fingerprint uniqueness.

Example: h7d3a9c2

Audio fingerprint

Offline audio processing can produce tiny differences across browsers and hardware. The result is usually shown as a hash rather than raw audio data.

Example: 9c822a71e4b8c2ad...

Installed fonts

Font detection compares text measurements. It cannot list every font perfectly, but common fonts can be inferred.

Example: Arial, Consolas, Segoe UI, Verdana

Uniqueness score

This is a local richness score showing how many signals were populated. It is not a global anonymity score unless compared against a large population.

Example: 71/100 richness

Browser capability parameters

WebRTC, WebGL, WebGPU

These indicate support for real-time communication and graphics APIs. They matter for video calls, games, 3D scenes, GPU compute, and advanced web apps.

Example: WebGL 1 yes / WebGL 2 yes; WebGPU supported

Geolocation permission

Permission status says whether location is granted, denied, or promptable. MyDevice.info does not request location automatically.

Example: prompt

Media device counts

Camera, microphone, and speaker counts may be hidden until the user grants permission. This protects privacy while still allowing diagnostics.

Example: camera 1, mic 2, speaker 0

Storage APIs

IndexedDB, localStorage, sessionStorage, CacheStorage, and Service Worker support tell you whether modern offline-capable web apps can run properly.

Example: IndexedDB yes, LocalStorage yes, CacheStorage yes

Ad blocker heuristic

A hidden bait element with ad-like class names can indicate whether cosmetic filtering is active. It is only a heuristic.

Example: Possible ad blocker

Sensors and input parameters

Touch support

Maximum touch points and pointer type help web apps choose the right interaction model for buttons, drag controls, and gestures.

Example: 5 max touch points

Device motion and orientation

Accelerometer and gyroscope events may be available on mobile devices, often behind permissions. They matter for games, AR, fitness, and motion-aware interfaces.

Example: motion events yes, orientation events yes

Performance parameters

Page load, DNS, TCP, response time

Navigation timing breaks down how long it took to load the page. It helps diagnose slow DNS, connection setup, server response, or rendering.

Example: DNS 3 ms, TCP 28 ms, response 74 ms

Memory usage

Chrome-based browsers may expose JavaScript heap usage. This helps detect memory-heavy pages but does not represent all system RAM usage.

Example: 42 MB used / 76 MB total / 4096 MB limit

Connection type

The Network Information API can report effective connection type, downlink, RTT, and Save-Data status where supported.

Example: 4g effective, 10 Mbps, 50 ms RTT