Privacy diagnostic · runs automatically

Browser Fingerprint Checker

See the browser, device, rendering, and privacy signals that websites can combine into a fingerprint—then inspect every result without surrendering the page to a loading screen.

View my live scan

Live report

Your browser, one signal at a time

Collection starts after the page becomes idle. You can continue reading while the scan fills this fixed task region.

Collecting browser fingerprint

The scan runs locally and keeps the rest of this page available.

Progress0 / 1

Initializing...

What does the CreepJS checker report?

CreepJS reports which browser APIs respond, the values or hashes they expose, collection timing, consistency warnings, and a coverage score. It groups those observations into readable signal cards so you can distinguish ordinary configuration data from privacy resistance or automation indicators. It does not identify a person or claim a fraud probability.

Manifest-derived taxonomy

The signal surface

A fingerprint becomes useful only when many weak observations are combined. The checker’s collector manifest currently covers the eight families below. Each live card shows the actual value, collector timing, and available context rather than collapsing everything into one unexplained score.

Graphics rendering

6

Canvas, WebGL, SVG, text metrics, and CSS rendering.

Canvas · WebGL · Emoji Rendering · SVG Rendering · CSS Styles · +1

Device surface

10

Screen, color, memory, CPU concurrency, and touch support.

Screen · Screen Frame · Screen Resolution · Color Depth · Color Gamut · +5

Browser capabilities

18

Navigator, storage, plugins, platform, and feature support.

Navigator · Languages · HTML Element · DOM Rectangle · MIME Types · +13

System context

9

Fonts, locale, timezone, architecture, and math behavior.

Fonts · Timezone · Date/Time Locale · Math Precision · Console Errors · +4

Media and audio

4

Audio processing, media devices, and speech voices.

Audio Context · Media Devices · Speech Voices · Audio Base Latency

Display preferences

6

Contrast, reduced motion, forced colors, and related settings.

Inverted Colors · Contrast · Forced Colors · Reduced Motion · Reduced Transparency · +1

Privacy resistance

4

Anti-fingerprinting signals, blockers, and consistency checks.

Anti-Fingerprinting Detection · Privacy / Ad Blockers · Private Click Measurement · Lies Detection

Network surface

2

WebRTC, service workers, and network-exposed capabilities.

WebRTC · Service Worker

1. Observe

Collectors ask standards-based browser APIs for rendering, environment, capability, and preference signals. A blocked or missing API is itself recorded as coverage context.

2. Normalize

The browser normalizes and hashes selected values into a compact diagnostic ID. Small environment changes can alter that snapshot, so the ID is not treated as permanent identity.

3. Explain

The report keeps individual evidence visible. Coverage measures completed collectors; population rarity appears only when anonymous sample counts clear the configured privacy threshold.

Privacy, stated precisely

The full fingerprint is collected and its diagnostic ID is computed in your browser. CreepJS does not upload the raw canvas image or the complete collector result from this page. Local history stays in this browser.

The optional uniqueness baseline sends a bounded comparison subset—Canvas hash, WebGL renderer, timezone, font count, and screen tuple—to the CreepJS API. The service stores coarse, hashed aggregate buckets and suppresses population estimates below the k-anonymity threshold. This boundary is why the report distinguishes live evidence, coverage, and rarity.

Common questions

Fingerprinting without the mythology

No. A cookie is a stored identifier that you can delete. A fingerprint is derived from browser and device characteristics that may remain similar across sessions. It is probabilistic context, not proof of a person’s identity.

No. Coverage only reports how many collectors completed successfully. Uniqueness requires a sufficiently large comparison population. CreepJS suppresses rarity estimates while the anonymous baseline is below its k-anonymity threshold.

Private browsing mainly isolates history, cookies, and storage. It does not necessarily standardize rendering, hardware, locale, or feature signals. Browser-level anti-fingerprinting defenses and a common configuration usually matter more.

Browser updates, display changes, font changes, privacy tools, permissions, and collector failures can alter individual signals. Treat the ID as a diagnostic snapshot rather than a permanent identity.

Keep exploring browser privacy signals

After the live checker, compare individual fingerprint collectors, IP risk signals, API docs, and integration examples.