Fingerprint Spoofing

Each rayobrowse session is assigned a real-world device profile from a database of thousands of fingerprints. These profiles are collected using the same techniques that major anti-bot companies use.

What’s spoofed

Signal	Description
User Agent	Matches target OS and Chrome version
OS / Platform	Windows, Android (thoroughly tested); macOS, Linux (experimental)
Screen resolution	Realistic display dimensions
WebGL	GPU renderer, vendor, and extensions matching real hardware
Canvas	Noise-adjusted canvas fingerprint with realistic variance
Fonts	Font list matched to target OS
WebRTC	Leak protection for local/public IP
Timezone	Auto-matched to proxy geolocation via MaxMind GeoLite2
hardwareConcurrency	Realistic CPU core count
Audio	AudioContext fingerprint noise
Locale	Language and region matching

How fingerprints are selected

• Profiles are selected dynamically based on the os and browser_version_min/max parameters
• Each session gets a unique combination from the profile database
• For deterministic environments, you can load a static fingerprint file (contact support@rayobyte.com for templates)

Chromium fork

rayobrowse tracks upstream Chromium releases and applies a focused set of patches:

• Normalize and harden exposed browser APIs
• Reduce fingerprint entropy leaks
• Improve automation compatibility
• Preserve native Chromium behavior where possible

Updates are continuously validated against internal test targets before release.

OS recommendations

os value	Status	Notes
windows	Recommended	Most thoroughly tested, best detection avoidance
android	Recommended	Well tested for mobile fingerprints
linux	Experimental	Available but not primary focus
macos	Experimental	Available but not primary focus

Version matching

For optimal results, set browser_version_min and browser_version_max to match the current Chromium version (currently 146). Using a mismatched version may trigger detection on some sites.