MyIP.dogChecking…
Browser fingerprint test
See what your browser reports about its settings, screen and graphics. Inspect locally and compare two snapshots.
Checking…
See what your browser reports about its settings, screen and graphics. Inspect locally and compare two snapshots.
Checking…
Checking…
Inspect the browser signals this page can read. Collection starts only when you choose Inspect browser; the report stays in this tab.
Optional local drawing sample and graphics details. No images are uploaded, and no camera, microphone or location permission is requested.
Ready. No fingerprint report has been collected.
This browser fingerprint test shows selected values that the current page can read from your browser. Choose Inspect browser to create a local snapshot. Collection begins with that action, so opening the page does not immediately create a report. Use this browser fingerprint checker to examine browser claims, screen dimensions, time-zone settings and media preferences without entering an IP address or account identifier.
Start the browser fingerprint test with the optional graphics setting turned off. This records the ordinary browser and display fields while marking the graphics entries as Not requested. Read the source attached to any unfamiliar value. A reported number is an observation from a named API, not an independently verified description of the physical computer behind it.
Use the browser fingerprint test to investigate a specific change, such as a different browser profile, display scale or privacy setting. Keep other conditions stable when comparing results. A changed viewport can alter screen-related observations without indicating that your network connection changed. Similarly, a new public IP does not require your language or graphics configuration to change.
The browser fingerprint test supports a second inspection in the same tab. Choose Inspect again to compare the new snapshot with the immediately preceding completed snapshot. The changed count includes differences in field values or availability states. Collection timestamps are excluded from that comparison, since a later observation necessarily has a different time.
Choose Clear to remove both snapshots and reset the graphics option. The browser fingerprint test also discards its report when the tab becomes hidden, on page-cache navigation, and when you leave this tool. A cancelled or superseded asynchronous result cannot restore a report that you cleared. Copy a report deliberately if you need to retain it outside the tab.
Selecting Also inspect Canvas and WebGL lets the browser fingerprint test draw a small, fixed local sample and read selected graphics properties. The sample uses generic system fonts, rectangles, text and a translucent circle. It does not download a photograph, request a camera stream or upload the resulting pixels. The option is off until you select it.
The browser fingerprint test calculates SHA-256 over the Canvas sample's raw RGBA pixels when Web Crypto is available. The displayed digest describes that particular sample and method. It is not a general browser identifier, an encryption key or a measurement of how many other people have the same output. A canvas fingerprint from another website can use different dimensions, fonts or byte encoding. Different methods cannot be compared just because both produce hexadecimal strings.
For WebGL, the browser fingerprint test reads standard context properties and separately attempts the optional debug-renderer extension. The browser may expose a generic renderer, a software renderer, a more specific driver string, or nothing useful. The tool releases its temporary WebGL context after reading it. It does not try alternate contexts to work around a denied read.
Read each browser fingerprint test observation in context
The browser fingerprint test groups its 46 named entries into browser claims, display measurements, preferences and optional graphics observations. The summary counts how many entries were reported, unavailable, blocked or not requested. These counts describe this collection attempt. A larger number of reported entries is not automatically better or worse for your particular privacy needs.
Reported means the browser fingerprint test obtained a supported value from the named interface. A false boolean, zero touch points or an empty language list remains a legitimate reported value. Unavailable means a value was absent, unsupported or could not be read successfully. This state does not distinguish every possible browser policy, extension or implementation difference.
Read blocked means the browser fingerprint test received a permission-related API error, such as a SecurityError. It does not mean the tool has identified the extension or setting responsible. Not requested applies to the optional graphics fields when their checkbox was off. These states remain separate in copied reports, so missing data cannot be mistaken for a reassuring result.
The browser fingerprint test includes an API source control beside every observation. Open it to see the specific property, media query or rendering method used. When a field changed between two snapshots, the same detail area shows the earlier value or state. This makes a comparison inspectable instead of hiding the underlying evidence behind a single score.
User-agent and platform strings in a browser fingerprint test are claims supplied by the browser. They can be reduced for privacy, altered by compatibility features or overridden by automation. MDN's user-agent documentation explains why these strings are unreliable for deciding which features a browser supports. Use direct feature detection when building an application.
The browser fingerprint test shows low-entropy client-hint brands and the mobile flag only when the interface exposes them. It does not request high-entropy hints such as architecture or detailed operating-system versions. An unfamiliar brand entry is not sufficient evidence of a fake browser. Browsers can deliberately vary these values, and multiple implementations may expose very similar results.
Logical processors and memory values in a browser fingerprint test also need qualification. The processor count can be reduced, while device memory is approximate and clamped. Neither field is a hardware inventory or a performance benchmark. The legacy plugin list can contain standardized PDF compatibility entries rather than an inventory of installed browser extensions. A missing memory value often reflects API support rather than missing physical RAM.
Screen dimensions in the browser fingerprint test use CSS pixels, while the device pixel ratio is reported separately. The available screen area and current viewport are different measurements. Browser chrome, window size, zoom, operating-system scale and external displays can influence these fields. Resizing a window is therefore a useful controlled example for understanding the comparison feature.
The browser fingerprint test reads the browser's reported time zone and the current offset expressed as UTC minus local time in minutes. That sign convention follows Date.getTimezoneOffset. Daylight-saving transitions can change the offset without changing the named zone. A time zone is a configuration clue, not proof of the visitor's physical location or the location of their public IP.
Media preferences in the browser fingerprint test include color scheme, reduced motion, contrast, forced colors, pointer, hover and color gamut. These are browser-reported query matches. They can reflect accessibility choices and hardware capabilities, and some implementations may standardize them. A primary pointer reported as fine does not prove that the user has no touchscreen available.
The WebGL debug fields in the browser fingerprint test may be unavailable even when ordinary WebGL properties work. MDN documents privacy-related restrictions on the debug extension. Standard and unmasked renderer strings are kept as different entries. Neither string is treated as a verified model name, and absent details are not filled with guesses.
This browser fingerprint test has no representative population database against which to measure your snapshot. It therefore cannot calculate a defensible uniqueness percentile, anonymity-set size or probability of recognizing you later. A collection of many fields can still be shared by many devices, while a rare-looking value alone does not establish a person's identity.
A matching browser fingerprint test snapshot is not proof that two sessions belong to the same person. Shared computers, standardized browser configurations and software-rendered graphics can produce similar observations. Conversely, the same person's browser may expose different values after updates, window changes or privacy protections. Identity and cross-session tracking require assumptions this report does not verify.
A browser fingerprint test also covers only selected JavaScript-readable interfaces in this page's context. It does not audit every network protocol, every browser feature, installed software, account cookies or behavior across other origins. The W3C guidance on fingerprinting describes multiple techniques and mitigation limits. Treat this report as a bounded observation, not a complete privacy certification.
A VPN can change the route and address visible to a destination while leaving the browser fingerprint test's language, screen and rendering values unchanged. That is not itself evidence that the VPN failed. Address observations and browser characteristics concern different surfaces. Use the homepage IP check to observe the address received by this website.
For browser network exposure, pair the browser fingerprint test with the separate WebRTC leak test when that measurement answers your question. Read its disclosure before starting: unlike this local report, that tool performs network observations. A difference between addresses needs context, and neither tool can automatically decide whether an entire device follows your intended VPN policy.
Changing many settings at once makes a browser fingerprint test harder to interpret. Start with one controlled variable and preserve the relevant evidence before switching tabs or profiles. Unusual custom settings can sometimes make a configuration more distinctive rather than less. Prefer understanding a browser's documented protections over trying to achieve a particular collection count on one website.
The browser fingerprint test does not send its collected values to a fingerprint service, attach them to analytics events, place them in a URL or write them to browser storage. Its working snapshots stay in component memory. Ordinary page delivery and site analytics still make requests. The tool does not attach its snapshot or Canvas digest to those requests. Analytics can independently receive ordinary browser and device metadata, as described in the privacy policy.
Copying the browser fingerprint test report is an explicit export to your operating-system clipboard. Review user-agent, language, time-zone and graphics details before sharing them publicly. Clipboard history, synchronization, extensions and other applications may have their own access or retention behavior. Clearing this tool does not delete a previously copied report or guarantee erasure of every memory copy.
The browser fingerprint test does not request camera, microphone or geolocation permissions. It does not enumerate installed fonts, render an audio fingerprint, probe connected media devices or scan browser extensions. The documented local Canvas sample and WebGL properties are the optional active graphics surface. Missing values are preserved without attempting to circumvent browser privacy controls.
No. This browser fingerprint test reports selected browser properties and local observations. It does not query an identity directory or request GPS. A time-zone setting and language list are not precise location measurements. Other websites may combine browser observations with accounts or other data, but this tool does not perform that correlation.
A browser fingerprint test can expose the renderer used by its current graphics context. Virtual machines, remote desktops, browser flags, driver failures and browser policy can influence that choice. A software-renderer string does not prove that the underlying computer lacks a GPU. Check the browser's own graphics diagnostics when investigating a rendering or acceleration issue.
The browser fingerprint test hashes one fixed pixel sample. Rendering changes, browser updates, font behavior and privacy-related randomization can affect its bytes. This tool does not distinguish those causes from one changed digest. The Canvas pixel-reading API and Web Crypto digest method are named in the result so its computation remains explicit.
No. The browser fingerprint test reports the Global Privacy Control and legacy Do Not Track properties when available. A reported preference does not audit whether every service honors it. Do Not Track is deprecated, and support for individual preference interfaces varies. Keep an unavailable property separate from a reported false value.
You can copy a report deliberately from each browser and compare the documented fields yourself. The browser fingerprint test's automatic comparison works only between two completed runs retained in this tab. It does not upload or merge reports across devices, and hiding or leaving the page clears its temporary comparison state.
Clear, a changed graphics option, a hidden tab or leaving the tool invalidates the working snapshots. This is deliberate local-state handling. If you need a record for troubleshooting, copy the browser fingerprint test report before making that transition. Stop and late-result handling keep an abandoned collection from unexpectedly repopulating the screen.
Read the per-field API sources, the method identifier in the copied report, and our methodology and data sources. The browser fingerprint test uses direct browser interfaces and a versioned Canvas sample, with no external fingerprinting library or visitor-comparison dataset. Source documentation was checked on September 28, 2026. The IP tools directory separates this local inspection from tools that contact a resolver, registry or remote probe.