First Verification

Verify BotBrowser fingerprint protection with CreepJS and BrowserLeaks after setup.

Prerequisites

• BotBrowser binary installed and working. See INSTALLATION.md.
• A profile file loaded via --bot-profile. See Profile Management.
• A proxy (optional but recommended for testing geo-detection).

Quick Start

1. Launch BotBrowser

chromium-browser \
  --bot-profile="/path/to/profile.enc" \
  --proxy-server=socks5://user:pass@proxy.example.com:1080 \
  --user-data-dir="$(mktemp -d)"

2. Visit a verification site

Open one of the following URLs in the browser:

• CreepJS: https://abrahamjuliot.github.io/creepjs/
• BrowserLeaks: https://browserleaks.com/

3. Check for a passing result

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.

How It Works

Fingerprint verification tools check browser properties for internal consistency.

BotBrowser profiles define all of these properties consistently at the browser engine level, so verification tools should see a unified, authentic browser environment.

Common Scenarios

Quick smoke test after profile updates

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 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 and BrowserLeaks.
2. Save launch args used for each run.
3. Diff results and investigate any new mismatch signals.

Framework vs. framework-less verification

If a framework-based run fails consistency checks:

1. Re-run with --bot-script using the same profile/proxy.
2. Compare outcomes to isolate whether the issue is framework artifacts.
3. Re-introduce framework options incrementally.

Verification Sites

CreepJS

URL: https://abrahamjuliot.github.io/creepjs/

CreepJS is one of the most comprehensive fingerprint analysis tools. It displays a trust score and consistency status across many browser properties.

Look for a high trust score and zero inconsistencies. All sections should show consistent data without “undefined” or error values.

Automation verification:

import { chromium } from "playwright-core";
 
const browser = await chromium.launch({
  executablePath: process.env.BOTBROWSER_EXEC_PATH,
  headless: true,
  args: [
    `--bot-profile=${process.env.BOT_PROFILE_PATH}`,
    "--proxy-server=socks5://user:pass@proxy.example.com:1080",
  ],
});
 
const page = await browser.newPage();
await page.addInitScript(() => {
  delete window.__playwright__binding__;
  delete window.__pwInitScripts;
});
 
await page.goto("https://abrahamjuliot.github.io/creepjs/");
// Wait for CreepJS to finish analysis
await page.waitForTimeout(15000);
await page.screenshot({ path: "creepjs-result.png", fullPage: true });
await browser.close();

BrowserLeaks

URL: https://browserleaks.com/

BrowserLeaks is useful for drilling into individual fingerprint surfaces such as Canvas, WebGL, fonts, WebRTC, timezone, and headers.

Look for values that match your loaded profile and proxy configuration with no obvious contradictions between sections.

What to Check

When reviewing verification tool results, confirm that all reported properties are internally consistent and match the loaded profile. BotBrowser handles this alignment automatically when a profile is loaded correctly. If you see any mismatch, check the troubleshooting table below.

Common Verification Failures and Fixes

Automated Verification Script

Run a complete verification check from the command line:

import { chromium } from "playwright-core";
 
const EXEC = process.env.BOTBROWSER_EXEC_PATH;
const PROFILE = process.env.BOT_PROFILE_PATH;
 
const sites = [
  { name: "CreepJS", url: "https://abrahamjuliot.github.io/creepjs/", wait: 15000 },
  { name: "BrowserLeaks", url: "https://browserleaks.com/", wait: 10000 },
];
 
const browser = await chromium.launch({
  executablePath: EXEC,
  headless: true,
  args: [
    "--disable-audio-output",
    `--bot-profile=${PROFILE}`,
  ],
});
 
for (const site of sites) {
  const page = await browser.newPage();
  await page.addInitScript(() => {
    delete window.__playwright__binding__;
    delete window.__pwInitScripts;
  });
 
  console.log(`Testing ${site.name}...`);
  await page.goto(site.url);
  await page.waitForTimeout(site.wait);
  await page.screenshot({
    path: `verification-${site.name.toLowerCase()}.png`,
    fullPage: true,
  });
  await page.close();
  console.log(`  Screenshot saved: verification-${site.name.toLowerCase()}.png`);
}
 
await browser.close();
console.log("Verification complete. Review the screenshots.");

Troubleshooting / FAQ

Next Steps

• Validation Results. Full test matrix across platforms and fingerprinting checks.
• CLI Recipes. Common flag combinations for different scenarios.
• Profile Management. Understand profile types, versions, and configuration.
• Proxy & Geolocation. How auto-detection works and how to override it.
• CLI Flags Reference. Complete list of all available flags.

Related documentation: Installation | Validation | Profile Configuration

Legal Disclaimer & Terms of Use  • Responsible Use Guidelines . BotBrowser is for authorized fingerprint protection and privacy research only.