Which signal groups are checked?
- Device: user agent, viewport, screen, DPR, touch, pointer, and hover.
- Geography: edge country, browser timezone, locale, and optional geolocation.
- Runtime: WebGL, canvas, audio, storage, permissions, and webdriver state.
- Network: ASN, provider, and optional proxy, VPN, Tor, relay, hosting, or mobile flags.
How does scoring work?
Scores are QA heuristics, not identity claims. Device/runtime, geography/network, privacy leak risk, and automation readiness each receive a score. Critical contradictions, such as mobile user agents without touch support or IP country/timezone mismatches, lower the relevant category.
What should be fixed first?
Fix contradictions that make a test result non-repeatable before polishing low-risk differences. Network geography and timezone usually come first, followed by mobile geometry, touch behavior, WebRTC candidates, and automation exposure.
What are the limits?
Cloak Browser reports observable consistency. It does not identify a person, certify a proxy, provide a browser binary, or make bypass recommendations for systems you are not authorized to test.