Open, explainable privacy diagnostics

Browser Fingerprint Checker & IP Risk Analysis

Understand what websites can observe about your browser and network. CreepJS turns dozens of weak signals into a readable report—without pretending coverage is identity or a fraud probability.

Run browser checker Check an IP

Browser evidence

Live fingerprint

Initializing...0/1

Open the full checker

Network evidence

Your public IP

Open IP risk checker

What is CreepJS?

CreepJS is the privacy diagnostic and API at creepjs.org. It reveals browser and IP-risk signals, explains coverage and privacy resistance, and only reports population context after anonymous-sample thresholds are met. It is distinct from Abraham Juliot's separate open-source CreepJS research project.

One page, evidence first

From exposed signal to useful decision

Browser fingerprinting does not depend on one magical value. Sites combine rendering behavior, device hints, locale, storage support, accessibility preferences, privacy resistance, and network context. CreepJS keeps those dimensions visible so you can inspect why a conclusion exists.

Browser exposure

Run standards-based collectors locally and inspect the returned values, hashes, timing, failures, and consistency warnings.

Network context

Separate free geolocation and ASN context from optional proxy, VPN, hosting, and abuse-risk enrichment.

Honest interpretation

Treat coverage as completion, not uniqueness. Population rarity stays suppressed while the baseline is too small.

Built for investigation and learning

Start with a browser or single-IP check, then move to the token API, playground, or SDK when the same evidence needs to fit a product or security process. Tokens remain in the client session; CreepJS does not sell fingerprint profiles.

For privacy-conscious people

See which browser and network signals are exposed, separate collector coverage from uniqueness, and learn where anti-fingerprinting defenses change the evidence.

Check this browser

For security teams

Investigate an IP, review proxy and datacenter context, and move into the documented token API when a repeatable operational surface is required.

Open IP tools

For developers

Integrate the small browser SDK, inspect live response contracts in the playground, and build on explicit signals instead of an unexplained black-box probability.

Read developer docs

Privacy is a data boundary

The browser collector and diagnostic ID run locally. The full raw report is not uploaded by the homepage. The own-IP card requests the existing public endpoint, where Cloudflare request metadata supplies free geolocation and paid risk data may gracefully degrade.

When a checker requests population context, only a bounded subset of derived or coarse browser values is used. Aggregate buckets are protected by k-anonymity suppression, and a small sample is never presented as a convincing rarity percentage.

Open signal reference

Inspect the evidence, not just the score

Every technique links to a crawlable, task-focused explanation. The registry below is the same source used by CreepJS metadata and signal pages, so the homepage cannot drift into a second, hand-maintained collector catalog.

Graphics

5 signals

Hardware

11 signals

Browser

16 signals

System