THE COMPLETE ENCYCLOPEDIA OF ANTI-DETECT BROWSER TESTING: From Basic Checks to Professional Auditing

[Professor]

INTRODUCTION: Why Testing Your Anti-Detect Browser Is Not Optional​

An anti-detect browser is not just a tool — it's your digital skin. If there's a hole in it, you're not just "exposed" — you're leaving a trail that leads directly back to you. In 2026, anti-fraud systems have become smarter, faster, and more cunning. They don't just check individual parameters — they build relationship graphs, analyze behavior, and look for inconsistencies in your digital profile.

CreepJS, BrowserLeaks, Pixelscan, IPHey, Whoer — these are not just websites to "check a box." They are your diagnostic tools. Without them, you're working blind. With them, you can see your digital shadow and control it.

This article covers every tool for testing anti-detect browsers, provides step-by-step algorithms, teaches you how to read results, and shows you how to fix problems. This is not just an overview — this is a complete diagnostic and configuration system.

PART 1: WHY ANTI-DETECT BROWSERS NEED TO BE TESTED​

1.1 What Is a "Hole" in an Anti-Detect Browser?​

A "hole" is any parameter that:

1. Leaks — shows your real data instead of the spoofed data (e.g., real IP, real Canvas fingerprint)
2. Is inconsistent — one parameter is spoofed, but a related one remains original
3. Reveals emulation — the site can tell you're using a virtual environment, not a real device
4. Is unstable — the fingerprint changes with every page load

1.2 How Anti-Fraud Systems Find Holes​

Modern anti-fraud systems (FingerprintJS Pro, DataDome, Akamai, PerimeterX) don't analyze individual parameters — they analyze combinations and consistency.

Check Type	What Is Analyzed	Example of Inconsistency
Geo-Consistency	IP, timezone, language, system time	IP from US, timezone Moscow, language ru-RU
Hardware Consistency	Canvas, WebGL, AudioContext, GPU model	Canvas and AudioContext from Intel, WebGL from NVIDIA
Version Consistency	User-Agent, engine version, installed fonts	Chrome 124, fonts like macOS
Behavioral Consistency	Typing speed, mouse movements, scrolling	Form filled in 2 seconds
Network Consistency	IP, DNS, WebRTC, TTL	WebRTC shows real IP, not proxy

1.3 Why You Can't Trust a Single Checker​

Each checker tests its own set of parameters. None of them provides 100% certainty. Only a combination of tools gives a complete picture.

Checker	Strengths	Weaknesses
CreepJS	Deep fingerprint analysis, lie detection	Hard to interpret
BrowserLeaks	Many parameters, detailed	Doesn't show consistency
Pixelscan	Quick diagnosis, behavioral analysis	Can be wrong
Whoer.net	Anonymity, DNS leaks	Surface-level analysis
IPHey.com	IP and region consistency	Limited functionality
AmIUnique	Fingerprint uniqueness	Doesn't show leaks

PART 2: MAIN TESTING TOOLS — Complete Breakdown​

2.1 CreepJS — The Most Honest and Complex Checker​

What It Is: This is not just a "fingerprint check." It's a lie detector — a system that checks how "honest" your browser is with the website. CreepJS analyzes dozens of parameters and tries to find inconsistencies ("lies").

Official Source: GitHub repository gabrieldiviricean/creepjs. All sites with .org, .com, etc., claiming to be CreepJS are unauthorized mirrors (potential traps).

What It Checks:

• Canvas fingerprint (image rendering)
• WebGL fingerprint (3D graphics rendering)
• AudioContext fingerprint (audio subsystem)
• Installed fonts
• navigator properties (userAgent, platform, language, hardwareConcurrency)
• screen properties (resolution, color depth)
• Timezone and system time
• Signs of browser tampering (leftover properties, API modifications)

How to Interpret Results:

Indicator	What It Means	Action
Trust Score	Overall browser "honesty." > 85% is good	If < 85%, find inconsistencies
Lies detected	Inconsistencies found	Check specific parameters
Canvas / WebGL / Audio	Fingerprint stability	Should be identical on reload
Fonts	Font list	Should match region

Proper Testing Procedure:

1. Test #1: Initial Run. Open CreepJS in a clean profile. Wait for full load.
2. Test #2: Reload. Refresh the page 2–3 times. Ensure the fingerprint hash is identical.
3. Test #3: Stability. Close the browser, reopen, and check CreepJS. The fingerprint should be identical.

Common CreepJS Mistakes:

Mistake	Consequence	Fix
Using unofficial site	Your fingerprint is collected	Use only GitHub version
Testing only once	Can't see stability	Test 2–3 times with reloads
Ignoring "Lies"	You think everything is fine	Always check the Lies section

2.2 BrowserLeaks — Detailed Layer-by-Layer Analysis​

What It Is: A comprehensive tool that shows each parameter individually. Allows you to find the specific "hole."

BrowserLeaks Sections and What They Show:

Section	What It Shows	What to Watch For
IP	Your IP, geolocation, ISP	Must match proxy
WebRTC	Real IP through WebRTC	Must be blocked or show proxy IP
Canvas	Canvas rendering hash	Must be stable
WebGL	GPU model, renderer, hash	Must match legend
Fonts	Installed fonts list	Must not be empty
Audio	Audio fingerprint	Must be unique
DNS	DNS server	Must match region

How to Interpret BrowserLeaks Results:

Parameter	Normal	Problem	Fix
IP	Matches proxy	Shows real IP	Change proxy, check WebRTC
WebRTC	Shows proxy IP or blocked	Shows real IP	Enable WebRTC protection
Canvas	Stable hash	Changes on reload	Set "Noise" mode with fixed seed
WebGL	Matches legend GPU	Doesn't match	Configure WebGL in anti-detect
Fonts	10–20 fonts	Too few or wrong region	Install region-standard fonts

2.3 Pixelscan — Quick Multi-Checker​

What It Is: A public test that simulates anti-fraud system behavior. Quick diagnosis, but not always accurate.

What It Checks:

• Fingerprint (overall)
• IP reputation (proxy, VPN, datacenter)
• DNS leaks
• Behavioral signals (bot patterns)
• Signs of automation

How to Interpret:

Result	What It Means	Action
Green / Safe	Everything is fine	Can use
Yellow / Warning	Some suspicions	Check with CreepJS
Red / Risky	High risk	Don't use, fix first

Why Pixelscan Sometimes Lies: Pixelscan is not an anti-fraud system. It's a simulation. Its algorithms may differ from real systems, so it can give false positives or false negatives.

2.4 WebBrowserTools — Specialized Checker​

What It Is: A tool for checking specific parameters — Canvas Fingerprint and AudioContext Fingerprint.

When to Use: When CreepJS or BrowserLeaks show a problem but you don't understand exactly what it is. WebBrowserTools lets you check a specific parameter in isolation.

2.5 Whoer.net — Anonymity Check​

What It Is: A classic tool for checking anonymity level.

What It Shows:

• IP geolocation vs timezone and language
• Anonymity level (should be 100%)
• DNS leaks
• WebRTC leaks

Proper Testing Procedure:

1. Open whoer.net in a regular browser — record results
2. Open whoer.net in the anti-detect browser — compare
3. Anonymity level should be 100%

2.6 IPHey.com — Consistency Check​

What It Is: A quick check of what your browser "tells" sites about you.

What It Shows:

• IP address and geolocation
• Language and timezone
• User-Agent
• Screen resolution

Check: All parameters should match the proxy region.

2.7 AmIUnique — Fingerprint Uniqueness Check​

What It Is: A tool showing how unique your fingerprint is among other users.

Why It Matters: If your fingerprint is too unique, you're easily tracked. If it's too standard, you look like a bot.

Optimal Range: 10–30% uniqueness. This means your fingerprint appears in 10–30% of other users.

2.8 chrome://gpu/ — Browser-Level Check​

What It Is: Built-in Chrome/Chromium tool showing graphics processor information.

When to Use: When other checkers show signs of emulation.

What to Watch For:

• "Software only" — sign of emulation
• Unusual drivers (VMware, VirtualBox)
• Lack of hardware acceleration

PART 3: STEP-BY-STEP TESTING ALGORITHM​

Step 1: Basic Test (Whoer.net + BrowserLeaks)​

Goal: Ensure basic spoofing works and there are no obvious leaks.

Procedure:

1. Launch a clean anti-detect browser profile
2. Open whoer.net — check anonymity (should be 100%)
3. Open browserleaks.com — check:
   • IP and geolocation (match proxy)
   • WebRTC (no leaks)
   • Canvas (stable hash)
   • WebGL (matches legend)
   • Fonts (not empty)
   • Timezone (matches region)

Signs of Success:

• Anonymity 100%
• All parameters match legend

Step 2: Deep Test (CreepJS)​

Goal: Check spoofing consistency and absence of "lies."

Procedure:

1. Open official CreepJS
2. Wait for full load
3. Check:
   • Trust Score (> 85%)
   • Number of "Lies" (fewer is better)
   • Specific problematic parameters
4. Reload page and verify fingerprint hash doesn't change
5. Close browser, reopen, and check stability

Signs of Success:

• Trust Score > 85%
• No or minimal "Lies"
• Stable fingerprint on reload

Step 3: Comparative Test (Baseline vs Anti-Detect)​

Goal: Ensure the anti-detect browser spoofs parameters to different values, not just "hides" them.

Procedure:

1. Launch regular Chrome (without anti-detect) and open CreepJS + BrowserLeaks
2. Record parameters (Canvas, WebGL, Audio, fonts, resolution, User-Agent)
3. Launch anti-detect profile and compare parameters
4. Ensure parameters are different, but consistent within themselves

Signs of Success:

• Parameters differ from regular browser
• Within anti-detect, parameters are consistent

Step 4: Uniqueness Test (AmIUnique)​

Goal: Check how unique your fingerprint is.

Procedure:

1. Open amiunique.org
2. Wait for test completion
3. Check uniqueness percentage

Signs of Success:

• Uniqueness 10–30%

Step 5: Stability Test (Long-Term)​

Goal: Ensure the profile remains stable over time.

Procedure:

1. Run tests (Steps 1–4)
2. Close the profile
3. Reopen the profile after 1–2 hours
4. Repeat tests

Signs of Success:

• All parameters remain unchanged

PART 4: COMMON PROBLEMS AND HOW TO FIX THEM​

4.1 Problem: Timezone and IP Mismatch​

How It Shows: Whoer.net shows anonymity < 90%. IP from US, timezone Moscow.

Cause: Timezone not configured in anti-detect.

Fix:

1. In profile settings, select timezone matching proxy region
2. Check system time (should match timezone)

4.2 Problem: WebRTC Leak​

How It Shows: BrowserLeaks shows real IP in WebRTC section.

Cause: WebRTC not blocked or spoofed.

Fix:

1. In anti-detect settings, enable "WebRTC Protection"
2. Select mode: "Block" or "Use proxy IP"
3. Check on browserleaks.com/webrtc

4.3 Problem: Unstable Canvas​

How It Shows: Canvas hash changes on each page reload.

Cause: "Noise" mode too strong or not fixed.

Fix:

1. In Canvas settings, select "Noise" or "Randomization" mode
2. Set fixed seed for noise generation
3. Check stability on BrowserLeaks

4.4 Problem: Language and Region Mismatch​

How It Shows: IP from US, browser language ru-RU.

Cause: Language not configured in anti-detect.

Fix:

1. In profile settings, select language matching proxy region
2. Check Accept-Language in HTTP headers

4.5 Problem: Too Clean Fingerprint​

How It Shows: CreepJS shows anomalies due to "perfect" spoofing.

Cause: Spoofing too "sterile," without natural variations.

Fix:

1. Add some "realistic noise" to Canvas/WebGL
2. Use "Randomization" instead of "Fixed" mode
3. Install standard region fonts

4.6 Problem: Too Few Fonts​

How It Shows: BrowserLeaks shows fewer than 10 fonts.

Cause: Fonts not installed in profile.

Fix:

1. Install standard font set for the region
2. For Windows: Arial, Times New Roman, Verdana, Georgia, Courier New, Calibri, Cambria, Tahoma, Consolas
3. For macOS: add Helvetica Neue, Lucida Grande, San Francisco

4.7 Problem: Identical Fingerprint Across All Profiles​

How It Shows: All profiles have identical hashes on CreepJS.

Cause: Anti-detect not configured with unique parameters for each profile.

Fix:

1. For each profile, configure unique parameters:
   • Screen resolution
   • Font list
   • Canvas noise
   • WebGL renderer
2. Use different browser versions for different profiles

4.8 Problem: DNS Leak​

How It Shows: Pixelscan shows DNS leak.

Cause: DNS queries go through real ISP, not proxy.

Fix:

1. Enable DNS-over-HTTPS in anti-detect
2. Configure DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8)
3. Check on browserleaks.com/dns

4.9 Problem: Emulator Detection​

How It Shows: chrome://gpu/ shows virtualization signs (Software only, VMware).

Cause: Browser running in virtual environment and it's visible.

Fix:

1. Use anti-detect with deep hardware spoofing
2. Configure GPU to a real model
3. For critical operations, use real hardware

PART 5: ADVANCED AUDITING — When Standard Checks Are Not Enough​

5.1 Testing Through Real Anti-Fraud Systems​

The most reliable way is to test the profile on a site using a real anti-fraud system (FingerprintJS Pro, DataDome, Akamai).

Examples:

1. FingerprintJS Pro: Many sites use this library. Find a site with the FingerprintJS Pro demo.
2. DataDome: Used on large e-commerce platforms.
3. Akamai Bot Manager: Used on many large sites.

How to Test:

1. Find a site with a known anti-fraud system (e.g., a major retailer)
2. Navigate the site, perform several actions (view products, add to cart)
3. Check if CAPTCHAs appear, if access is blocked

5.2 TLS Fingerprint Consistency Check​

TLS fingerprint is one of the hardest parameters to spoof. It shows encryption version and TLS settings.

Tools for Checking:

1. JA3 / JA4 Fingerprint: Analyzes TLS handshake.
2. What's My TLS Fingerprint: Shows TLS fingerprint.

How to Fix Issues:

1. Use anti-detects with TLS fingerprint spoofing support
2. Select preset fingerprint sets for popular browsers

5.3 HTTP Header Leak Check​

HTTP headers can reveal your real browser or OS.

Tools for Checking:

1. HTTP Header Live: Browser extension
2. curl -v: Command line

What to Check:

• Accept-Language (should match region)
• Accept-Encoding (standard set)
• User-Agent (should match OS and browser)

PART 6: ANTI-DETECT BROWSER TESTING CHECKLIST​

6.1 Basic Checklist (Before Every Operation)​

• IP address matches proxy region
• IP geolocation matches timezone and language
• WebRTC blocked or shows proxy IP
• Canvas fingerprint stable (doesn't change on reload)
• WebGL matches GPU model from legend
• AudioContext spoofed
• Font list contains 10–20 fonts matching region
• Timezone matches proxy region
• Browser language matches proxy region
• User-Agent matches OS and browser

6.2 Advanced Checklist (Weekly)​

• Trust Score in CreepJS > 85%
• No or minimal "Lies" in CreepJS
• Fingerprint uniqueness on AmIUnique 10–30%
• Anonymity level on Whoer.net 100%
• No DNS leaks
• chrome://gpu/ shows no emulation signs
• TLS fingerprint matches browser
• HTTP headers are consistent

PART 7: TOOL COMPARISON TABLE​

Tool	Best For	Strengths	Weaknesses	Use Frequency
CreepJS	Deep consistency check	Lie detection, deep analysis	Complex to interpret	Every session
BrowserLeaks	Parameter-by-parameter check	Detailed, many parameters	No overall score	Every session
Pixelscan	Quick diagnosis	Fast, behavioral analysis	Can be inaccurate	Weekly
Whoer.net	Anonymity check	Simple, clear	Surface-level	Every session
IPHey.com	IP consistency check	Fast, focused	Limited scope	Every session
AmIUnique	Uniqueness check	Unique perspective	Doesn't show leaks	Weekly
chrome://gpu	Emulation detection	System-level	Technical	Monthly
TLS Checkers	TLS fingerprint	Deep security	Requires expertise	Monthly

PART 8: ANTI-DETECT CONFIGURATION TEMPLATE​

8.1 Optimized Settings for Anti-Detect Browsers​

Parameter	Recommended Setting	Notes
Canvas	Noise mode with fixed seed	Stable fingerprint
WebGL	Realistic GPU model	Match legend
AudioContext	Spoofed	Must not match real hardware
WebRTC	Blocked or proxy IP	No leaks
Fonts	15–20 region-standard fonts	Not too few, not too many
Timezone	Match proxy region	Must match IP
Language	Match proxy region	Must match IP
Screen Resolution	Standard (1920x1080, 1366x768)	No exotic resolutions
User-Agent	Current, common version	Match OS
TLS Fingerprint	Preset from popular browser	Match User-Agent

8.2 Daily Profile Rotation​

Day	Profile Use	Action
Day 1	Check IP and geolocation	Verify consistency
Day 2	Run BrowserLeaks	Check for leaks
Day 3	Run CreepJS	Verify consistency
Day 4	Run Pixelscan	Quick health check
Day 5	Full audit	Run all tools
Day 6	Simulate browsing	Test on real sites
Day 7	Rest	Let profile "cool down"

PART 9: EXPERT TIPS FOR SUCCESSFUL TESTING​

1. Test every profile before use. A single unchecked profile can burn everything.
2. Always test under real conditions. Use the same proxy and setup as your actual operation.
3. Document your results. Keep a log of what works and what doesn't.
4. Update your tools. Fingerprint technology evolves rapidly.
5. Test for consistency, not just uniqueness. A unique fingerprint isn't enough — it must be consistent.
6. Check for all leak types. IP leaks, WebRTC leaks, DNS leaks, Header leaks — all of them matter.
7. Use multiple tools. No single tool catches everything.
8. Test across different sessions. Ensure your fingerprint remains stable over time.
9. Monitor for pattern detection. If the same sites keep blocking you, something is wrong.
10. Keep learning. The security landscape changes constantly.

CONCLUSION: 10 GOLDEN RULES OF ANTI-DETECT TESTING​

1. Don't trust a single checker. CreepJS + BrowserLeaks + Pixelscan is the optimal minimum.
2. Check stability. The fingerprint should be identical on reload and across sessions.
3. Compare with a baseline. Run a regular browser and compare parameters.
4. Spoofing must be consistent. If Canvas is spoofed, WebGL must also be spoofed. If IP is US, timezone and language must be US.
5. Test the profile before every major operation. Even if it worked yesterday, something may have changed today.
6. Fix holes immediately. Don't postpone.
7. Update tools regularly. Fingerprint technology evolves rapidly.
8. Test on real anti-fraud systems. Public checkers are good, but real systems are better.
9. Document everything. What works today may not work tomorrow.
10. Never stop learning. Security systems evolve, and so must you.