Skip to main content

Anti-Detection Best Practices

Meshbrow handles most anti-detection automatically, but your agent’s browsing behavior still matters. This guide covers what Meshbrow does for you and what you need to handle in your automation code.

What Meshbrow Handles Automatically

Browser Fingerprint

Canvas noise, WebGL spoofing, font enumeration, plugin list, screen resolution — all generated consistently per session.

Navigator Properties

platform, hardwareConcurrency, deviceMemory, languages, webdriver flag — all patched to match the fingerprint.

WebRTC Leak Prevention

Local IP addresses are masked. WebRTC candidates reflect the proxy IP only.

TLS Fingerprint

JA3/JA4 fingerprints match real Chrome browsers. No detectable automation signatures.

Timezone & Locale

Automatically matched to proxy geo-location. Intl.DateTimeFormat and Date are consistent.

Chrome Flags

No --enable-automation, no cdc_ driver properties, no leaked DevTools protocol indicators.

What You Need to Do

1. Behave Like a Human

Anti-detect isn’t just about fingerprints — it’s about behavior.

2. Simulate Mouse Movement

3. Scroll Naturally

4. Use Realistic Session Durations

5. Match Proxy Geo with Content

Common Detection Vectors

Testing Your Anti-Detection

Use these sites to verify your setup:

Stealth Levels Explained

Always start with stealth: "max". Only reduce if you need faster session launch times for known low-security targets.