> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorbrowser.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Network and Stealth

> Get past IP blocks, bot detection, and CAPTCHAs on automated browser sessions.

Sites block automation in two places: the **network** (IP reputation, geography, rate limits) and the **browser** (fingerprinting, bot checks, CAPTCHAs). The options below address each layer. Set them in `session` and `browser` at create time, or once per task in `task_default_browser_configuration`.

### [Proxy](/advanced/proxy)

Most automation failures start at the IP. Datacenter addresses get flagged, the wrong country gets geo-blocked, and shared proxy pools burn out fast. A proxy puts your session on an IP and location the target site expects — US retail from a US address, EU compliance from an EU exit, or your own corporate proxy when policy requires it. Anchor provides built-in residential-style routing with country/region/city targeting.

### [Bring Your Own Proxy](/advanced/bring-your-own-proxy)

When policy or compliance requires your own egress, plug in an HTTP, HTTPS, or SOCKS5 server you already operate. You control the provider, credentials, and network path; Anchor routes the browser session through it.

### [Dedicated Sticky IP](/advanced/dedicated-sticky-ip)

Some sites don't just care *where* you are — they care that your IP *stays the same*. Banking, SaaS accounts, and fraud systems lock or challenge users whose IP jumps between sessions. A dedicated sticky IP reserves one egress address for a profile so every run looks like the same device coming from the same place.

### [Anchor VPN](/advanced/anchor-vpn)

Rotating proxies trade consistency for scale. When you need a **stable, private egress path** at enterprise volume — one IP that belongs only to you, on infrastructure Anchor operates end-to-end — VPN replaces the commodity proxy hop. Fewer reputation surprises, fewer mid-flow auth breaks.

### [Extra Stealth](/essentials/stealth)

A clean IP is not enough if the browser itself screams "bot." Sites inspect fingerprints: automation flags, headless signals, canvas/WebGL consistency, and dozens of other tells. Extra Stealth runs a hardened Chrome environment built to pass those checks — so your session is less likely to be identified as automated before it ever clicks a link. Requires proxy. Growth plan.

### [CAPTCHA solving](/advanced/captcha-solving)

CAPTCHAs exist to stop bots at the front door — image puzzles, Cloudflare turnstiles, "verify you're human" gates. When one appears mid-flow, automation stops unless something solves it. Anchor watches for CAPTCHA UI in the session and resolves it automatically using vision-based detection, so your workflow continues without a human in the loop. Requires proxy (or a profile with its own stable egress).

### [Web Bot Auth](/advanced/cloudflare-web-bot-auth)

Not every site wants to block all bots — some participate in Cloudflare's Web Bot Auth program and will **allow verified automated clients** that cryptographically identify themselves. If you are building an approved integration, signed requests prove you are Anchor Browser rather than a scraper spoofing a user agent. Different path than hiding; you are declaring yourself as a legitimate bot.

### [Web Unlocker](/advanced/web-unlocker)

Sometimes you do not need a full browser — you need the HTML. Web Unlocker is a single API call that fetches a rendered page from a URL. Anchor handles proxy rotation, CAPTCHA, and fingerprinting internally. Good for read-only extraction at scale; use a session when you need to log in, click, or maintain state across steps.

## Enterprise IP allowlisting

Some platforms require you to allowlist Anchor's outbound IP addresses before browser automation can reach protected endpoints. Static egress routing is enabled for your project upon request — [contact us](mailto:support@anchorbrowser.io?subject=Static%20egress%20IP%20allowlist) to turn it on.

Add these addresses to your firewall, WAF, or platform allowlist:

```
3.19.204.234
16.58.4.236
18.219.69.116
3.143.75.163
18.189.45.103
3.21.249.234
```

<Note>
  Allowlisting is a change on your side — Anchor does not block access from our end.
</Note>
