When an automated script loads SannySoft, the site instantly analyzes client-side JavaScript attributes. The results are categorized as either or failed . Test Category Key Attributes Checked Target Value for Success WebDriver navigator.webdriver Must return false or undefined Chrome Variables window.chrome leaks Must mirror genuine Google Chrome footprints Permissions Notification.permission query consistency Must not mismatch user-agent claims Plugins & MimeTypes navigator.plugins.length Cannot be 0 (standard headless giveaway) Hardware Fingerprints WebGL Vendor & Renderer, Canvas elements Real graphics cards, not simulated drivers The WebDriver Check
: The simplest method is to replace your automation library with a stealth-hardened fork. bot.sannysoft
It acts like a dedicated . Before you launch your bot against a heavily protected target (like a bank or a social media site), you can run it through SannySoft to see where it might be leaking information. It’s the go-to first step for hardening your automation stack against detection from major anti-bot systems like Cloudflare and DataDome. When an automated script loads SannySoft, the site
It detects if essential window objects, such as window.chrome , are missing, which naturally occurs in standard headless environments. It acts like a dedicated
// Go to the test page await page.goto("https://bot.sannysoft.com/");
After running the script, open sannysoft_test.png . The page contains a series of colored boxes and status indicators:
Google)", "ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)" ], "multimediaDevices": { bot.sannysoft.com