bot.sannysoft.com is a popular, open-source diagnostic page used to test how "stealthy" a web browser or automated bot is. It runs various tests to check if a visitor looks like a real human using a browser or a script (like Puppeteer or Selenium) that might be trying to hide its identity. Core Tests and What They Mean
The page evaluates your browser's fingerprint through several key checks:
User-Agent: Checks if the reported browser and operating system match typical human setups. Fake User-Agents, like a mobile agent on a desktop browser, are often flagged.
WebDriver Check: This is a major "bot-killer." Standard automation tools often leave a navigator.webdriver flag set to true. Sannysoft checks for this to see if the browser is being controlled by a script.
Chrome vs. Headless Chrome: It detects differences in how "headless" (windowless) browsers behave compared to full versions, such as missing plugins or specific WebGL renderer names (e.g., "SwiftShader" often signals a virtual/bot environment). bot.sannysoft
Permissions & Plugins: It verifies if features like the Permissions API or the list of Plugins behave normally. Bots often fail these because they don't simulate the background data of a real installation. Why People Use It
Bot Developers: Developers use it to verify that their "stealth" plugins, such as puppeteer-extra-plugin-stealth, are working correctly to bypass bot detection on sites like Google or Amazon.
Anti-Detect Browsers: Companies like Kameleo use Sannysoft as a benchmark to prove their software can successfully "mask" a user's identity.
Security Testing: Researchers use it to understand the latest techniques websites use to block automated scrapers or suspicious traffic. How to Improve Results Case 1: E-commerce Price Monitoring A company scraping
If you are failing checks on Sannysoft, common solutions include:
Stealth Plugins: Using specialized libraries like puppeteer-extra-plugin-stealth to automatically patch known "bot" leaks.
Residential Proxies: Rotating through high-quality residential or mobile proxies to avoid being flagged by your IP address.
Anti-Detect Browsers: Using tools like AdsPower or GoLogin, which are designed specifically to pass fingerprinting tests by creating unique, isolated browser profiles. Red/failed items indicate high-confidence bot signals
Are you trying to fix a specific failing test on the site, or
A company scraping competitor prices kept getting blocked after 50 requests. Using Selenium with headless Chrome and testing against bot.sannysoft, they discovered their navigator.webdriver flag was exposed. After patching it and re-verifying with the tool, their scrape success rate jumped to 95%.
bot.sannysoft Diagnostics| Symptom | What bot.sannysoft Shows | Fix |
| :--- | :--- | :--- |
| ElementClickInterceptedException | Canvas coordinates are offset (red overlay) | Set correct viewport size using --window-size |
| Text appears as boxes | Missing Arial/Times New Roman in font test | Install base fonts in Docker: apt-get install -y fonts-liberation |
| Screenshot is blank white | Headless mode not using GPU or renderer | Add --use-gl=egl or --disable-gpu flag toggle |
| Console errors about WebGL | WebGL test shows Unsupported | Upgrade Chrome version or fallback to software rendering |
pip install webdriver-manager)When you run Selenium inside a Docker container (e.g., selenium/standalone-chrome-debug), there is no GUI. Running a simple driver.get("https://google.com") might pass, but that doesn't test rendering. bot.sannysoft explicitly tells you if the headless browser is rendering fonts and canvases correctly.