Device & System

You are running a browser that misreports these values on purpose (Brave with Shields on, or similar). The resolution and DPR the browser is showing here are decoys, not your real hardware -- that is a good thing. No action needed. If you want to go further, install the Tor Browser for maximum-risk sessions (research, journalism, whistleblowing) where the extra latency is worth the near-perfect anonymity.

Your browser is faithfully reporting your real screen resolution, platform, and touch capability. If fingerprint resistance matters to you, the best moves are: (1) Switch to Brave (Chromium-based, one-click install, misreports screen + hardware values by default). (2) Switch to LibreWolf (Firefox fork, aggressive privacy defaults, no telemetry). (3) In Firefox, set privacy.resistFingerprinting to true in about:config -- this forces a standard 1000x1000 window size and rounds DPR. AVOID relying on Chrome or Edge alone for fingerprint resistance: they expose everything and have no equivalent setting. AVOID Safari on macOS for the same reason -- it exposes a very specific and stable set of values that fingerprinters love.

Either your browser hides these values (Brave misreports them, Firefox never implemented deviceMemory or Battery) or none are exposed. No action needed. If you switch away from this browser in the future, you will lose this protection: Chrome and Edge expose all three by default and there is no setting to disable them short of installing an extension like CanvasBlocker.

This card is red because your browser exposed the full trio: cores + memory + battery. That is Chrome, Edge, Opera, or Vivaldi in a default configuration. To fix it in order of aggressiveness: (1) Switch to Brave -- one click, it misreports cores as 8 and rounds memory, and blocks Battery entirely with Shields up. (2) Switch to Firefox -- Battery is gone entirely, and deviceMemory is not implemented, so two of the three go away for free. (3) Stay on Chrome/Edge but install "Chameleon" or "CanvasBlocker" to spoof the values -- less reliable than switching. AVOID Safari as a "privacy" alternative: it exposes similar hardware hints and does not let you turn them off.

Your browser exposes some but not all of these values -- typically because you are on Firefox or Safari, which implement CPU cores but not memory or battery. Firefox is a solid choice as-is; if you want to hide cores too, set privacy.resistFingerprinting to true in about:config (it will clamp hardwareConcurrency to 2). Safari users: consider Brave or Firefox for stronger protection -- Safari has no equivalent setting.

Only the standard PDF viewer entries are showing, or no plugins at all. That is the expected state on modern Chrome, Edge, Firefox, and Brave. No action needed. If you are on Brave and see zero plugins, that is Shields hiding the whole list -- also fine.

Three or more non-standard plugin entries were found -- this is a strong, stable fingerprint. Do a full extension audit: disable every non-essential extension in chrome://extensions or about:addons, then re-run this test. For anonymous browsing sessions, use a browser profile with ZERO extensions installed (Tor Browser does exactly this by design). If the non-standard entries survive with no extensions, they may be OS-level (Windows PDF handler, corporate policy) -- consider switching to Firefox where fewer OS-level plugins get exposed.

One or two non-standard entries showed up. That is usually a browser extension injecting itself into navigator.plugins. Audit your extensions: open chrome://extensions or about:addons, disable everything you do not actively use, and re-run this test. If the non-standard entries persist, note their names -- searching for the exact name usually reveals which extension is responsible. Consider whether the privacy value of that extension outweighs the fingerprint it adds.