Loading
Initializing detection systems...
Loading
Initializing detection systems...
Method and Boundaries
Pixelscan is a browser and network diagnostics tool. It is designed to make the signals behind VPN, proxy, leak, and fingerprint checks visible, not to promise perfect attribution.
Reviewed on July 28, 2026
Pixelscan helps developers, QA teams, security researchers, and privacy-conscious users inspect what a website can learn from one visit. The product is most useful when you need to answer practical questions such as "Is my VPN leaking?", "Do my browser claims line up with my network path?", or "Why did this environment get flagged as suspicious?".
If you want the vocabulary behind these checks, start with the glossary. If you want the live product surface, go back to the dashboard.
The current implementation runs one shared scan session per visit and reuses the same results across the site instead of probing each page independently.
The first server request records Cloudflare edge metadata for the current connection and creates the scan id used across the session.
The client collects browser fingerprint fields from APIs your browser already exposes, such as Canvas, WebGL, screen, locale, and platform hints.
WebRTC and DNS checks run after the public IP is known, so leak findings can be compared against the same visit instead of a generic baseline.
Pixelscan combines reputation signals, privacy flags, leak results, and consistency checks into a trust score with an explicit verdict and findings list.
Pixelscan mixes first-party session data with optional third-party enrichment. Missing providers reduce confidence; they do not silently become fabricated values.
Used for IP, ASN, city/country, HTTP version, TLS version/cipher, edge colo, and RTT when Cloudflare exposes them for the current request.
Used for fingerprint collection and client-side leak testing. If a browser blocks a signal, Pixelscan shows less data rather than inventing a value.
IP enrichment can come from ipinfo and IPBot when those providers are configured and reachable. If they are absent, trust scoring falls back to weaker signals.
/scan/<id> are marked noindex in the app's route metadata.These are visible product explanations for users, not FAQ schema for search engines.
The score depends on the whole session, not only the browser. Switching egress IPs, toggling a VPN, changing WebRTC behavior, or losing an enrichment provider can move the verdict even when the device stays the same.
No. The product reads the current request metadata plus the browser and leak-test signals it collects during this session. It does not become a network monitor for the rest of your browsing.
No. The score is a diagnostic summary for the current scan. If you are making security or business decisions, combine it with your own authentication, behavior, device, and abuse controls.