CPU Core Fingerprinting: Protect hardwareConcurrency
Websites use navigator.hardwareConcurrency to fingerprint your CPU core count. Learn how to control core reporting across Workers, iframes, and all execution contexts with engine-level protection.
The blog is for education, comparisons, and commentary. The docs center is for setup, reference, validation, and responsible-use material.
Start with these guides to explore the tag before browsing the full list.
Font rendering differences between Windows, macOS, and Linux expose your real OS in browser fingerprints. Learn how to maintain consistent CJK font output across all platforms.
Run the same browser fingerprint profile on any OS and get identical Canvas, WebGL, font, and navigator output. Engine-level consistency that extensions and JS patches cannot achieve.
Additional guides with this tag.
Websites use navigator.hardwareConcurrency to fingerprint your CPU core count. Learn how to control core reporting across Workers, iframes, and all execution contexts with engine-level protection.
Installed fonts and text metric measurements create unique browser fingerprints with 8+ bits of entropy. Learn engine-level techniques to control font identity and prevent font-based tracking.
WebGL exposes your GPU model, driver version, and rendering output as high-entropy fingerprint signals. Learn how to control all WebGL parameters at the engine level for consistent protection.
Canvas fingerprinting uses HTML5 rendering differences to track users across sessions without cookies. Learn how engine-level control produces consistent, authentic Canvas output on every platform.
Browser fingerprinting tracks you without cookies using Canvas, WebGL, fonts, and 30+ signals. Learn how each technique works and how to protect your privacy with engine-level fingerprint control.
The guides cover the model first, then move into cross-platform validation, isolated contexts, and scale-ready browser deployment.