docs: simplify verification sites to CreepJS and BrowserLeaks

Author: MSTU0

docs/guides/README.md

@@ -16,7 +16,7 @@ These guides cover everything from initial setup to advanced deployment scenario
 | [Bot Script](getting-started/BOT_SCRIPT.md) | Automate BotBrowser without Playwright or Puppeteer using `--bot-script` and Chrome Debugger APIs. |
 | [CLI Recipes](getting-started/CLI_RECIPES.md) | Use copy-paste CLI recipes for proxy, fingerprint, identity, and deployment scenarios. |
 | [Profile Management](getting-started/PROFILE_MANAGEMENT.md) | Manage profile files, versions, and lifecycle for reproducible browser identity. |
-| [First Verification](getting-started/FIRST_VERIFICATION.md) | Validate fingerprint consistency with CreepJS, Iphey, BrowserScan, and Pixelscan. |
+| [First Verification](getting-started/FIRST_VERIFICATION.md) | Validate fingerprint consistency with CreepJS and BrowserLeaks. |
 | [Automation Consistency Practices](getting-started/AUTOMATION_CONSISTENCY.md) | Reduce framework-related inconsistency signals in Playwright/Puppeteer workflows. |
 | [CanvasLab](getting-started/CANVASLAB.md) | Record Canvas 2D, WebGL, and WebGL2 API calls to study tracking techniques and verify fingerprint protection. |
 | [AudioLab](getting-started/AUDIOLAB.md) | Record Web Audio API calls to study audio fingerprint collection and verify audio privacy protection. |

docs/guides/getting-started/FIRST_VERIFICATION.md

@@ -1,6 +1,6 @@
 # First Verification
 
-> Verify BotBrowser fingerprint protection with CreepJS, Iphey, BrowserScan, and Pixelscan after setup.
+> Verify BotBrowser fingerprint protection with CreepJS and BrowserLeaks after setup.
 
 ---
 
@@ -32,13 +32,11 @@ chromium-browser \
 Open one of the following URLs in the browser:
 
 - **CreepJS:** `https://abrahamjuliot.github.io/creepjs/`
-- **Iphey:** `https://iphey.com/`
-- **BrowserScan:** `https://www.browserscan.net/`
-- **Pixelscan:** `https://pixelscan.net/`
+- **BrowserLeaks:** `https://browserleaks.com/`
 
 ### 3. Check for a passing result
 
-Each tool reports a trust score or consistency status. A properly configured BotBrowser instance should show consistent fingerprint data across all reported properties.
+Each tool reports either a trust score or detailed signal output. A properly configured BotBrowser instance should show consistent fingerprint data across all reported properties.
 
 ---
 
@@ -59,14 +57,14 @@ BotBrowser profiles define all of these properties consistently at the browser e
 When you switch to a new profile version, run one fast pass first:
 
 1. Launch with only `--bot-profile` and `--proxy-server`.
-2. Open CreepJS and BrowserScan.
+2. Open CreepJS and BrowserLeaks.
 3. Confirm no obvious mismatch before adding advanced flags.
 
 ### Regression check before production rollout
 
 Use the same machine, profile, and proxy to compare before/after results:
 
-1. Capture screenshots from CreepJS, Iphey, and Pixelscan.
+1. Capture screenshots from CreepJS and BrowserLeaks.
 2. Save launch args used for each run.
 3. Diff results and investigate any new mismatch signals.
 
@@ -121,31 +119,14 @@ await browser.close();
 ```
 
 <a id="iphey"></a>
-### Iphey
+<a id="browserleaks"></a>
+### BrowserLeaks
 
-**URL:** `https://iphey.com/`
+**URL:** `https://browserleaks.com/`
 
-Iphey provides a straightforward pass/fail assessment with detailed breakdown by category.
+BrowserLeaks is useful for drilling into individual fingerprint surfaces such as Canvas, WebGL, fonts, WebRTC, timezone, and headers.
 
-Look for a green "Trusted" badge with all categories showing green checkmarks.
-
-<a id="pixelscan"></a>
-### Pixelscan
-
-**URL:** `https://pixelscan.net/`
-
-Pixelscan displays a consistency status for browser properties and network location.
-
-Look for "Consistent" status across all tested categories with no mismatches.
-
-<a id="browserscan"></a>
-### BrowserScan
-
-**URL:** `https://www.browserscan.net/`
-
-BrowserScan tests a broad range of fingerprint surfaces and displays results in a clear dashboard.
-
-Look for consistent values across all fingerprint sections with no warnings or mismatches.
+Look for values that match your loaded profile and proxy configuration with no obvious contradictions between sections.
 
 ---
 
@@ -189,9 +170,7 @@ const PROFILE = process.env.BOT_PROFILE_PATH;
 
 const sites = [
   { name: "CreepJS", url: "https://abrahamjuliot.github.io/creepjs/", wait: 15000 },
-  { name: "Iphey", url: "https://iphey.com/", wait: 10000 },
-  { name: "BrowserScan", url: "https://www.browserscan.net/", wait: 10000 },
-  { name: "Pixelscan", url: "https://pixelscan.net/", wait: 10000 },
+  { name: "BrowserLeaks", url: "https://browserleaks.com/", wait: 10000 },
 ];
 
 const browser = await chromium.launch({

docs/guides/getting-started/PROFILE_MANAGEMENT.md

@@ -31,7 +31,7 @@ chromium-browser \
 
 ### 3. Verify it works
 
-Visit [CreepJS](https://abrahamjuliot.github.io/creepjs/) or [Iphey](https://iphey.com/) to confirm the fingerprint is active. See [First Verification](FIRST_VERIFICATION.md) for a complete verification checklist.
+Visit [CreepJS](https://abrahamjuliot.github.io/creepjs/) or [BrowserLeaks](https://browserleaks.com/) to confirm the fingerprint is active. See [First Verification](FIRST_VERIFICATION.md) for a complete verification checklist.
 
 ---