Proxy Configuration and Geographic Distribution for Cloud Browsers

Introduction

A browser fingerprint alone is not enough for a consistent identity. Your IP address, DNS behavior, and geographic metadata must all align with the identity your browser profile presents. If your profile says "Windows user in Berlin" but your IP resolves to a data center in Virginia, the inconsistency is obvious to any detection system.

BotCloud handles geographic consistency automatically, but understanding how it works helps you configure proxies effectively for your specific needs.

Why Geographic Consistency Matters

Modern detection systems cross-reference multiple geographic signals:

• IP geolocation - Where your IP address is physically located
• Timezone - The Intl.DateTimeFormat resolved timezone
• Language - The navigator.language and Accept-Language header
• Locale - Number formatting, date formatting, currency preferences

When these signals disagree, it raises flags. A browser claiming America/New_York timezone but connecting from a German IP is suspicious. A user with Accept-Language: ja-JP connecting from Brazil is unusual.

Proxy Types

BotCloud supports all major proxy protocols:

Protocol	Format	DNS Resolution	Best For
SOCKS5	socks5://user:pass@host:port	Client-side	General purpose
SOCKS5H	socks5h://user:pass@host:port	Proxy-side	Privacy (no DNS leak)
HTTP	http://user:pass@host:port	Proxy-side	Wide availability
HTTPS	https://user:pass@host:port	Proxy-side	Encrypted proxy connection

SOCKS5 vs SOCKS5H

The critical difference is DNS resolution. With SOCKS5, your machine resolves domain names locally, then sends the IP to the proxy. This can leak your DNS server's location. With SOCKS5H, domain names are sent to the proxy for resolution, keeping DNS within the proxy tunnel.

For privacy-sensitive automation, always prefer SOCKS5H.

Automatic Geographic Alignment

When you specify a proxy with BotCloud, the session automatically aligns geographic signals to match the proxy's location:

• Timezone is set based on the proxy IP's geolocation
• Language and locale preferences match the region
• WebRTC is configured to prevent IP leaks outside the proxy tunnel
• DNS queries route through the proxy (SOCKS5H)

This means you do not need to manually configure timezone, language, or locale for each session. Specify the proxy, and everything else follows.

Configuration Examples

Basic proxy setup

const browser = await puppeteer.connect({
  browserWSEndpoint: 'wss://bots.win/ws?apiKey=YOUR_API_KEY&proxy=socks5h://user:pass@proxy.example.com:1080',
});

Per-session proxy rotation

const proxies = [
  'socks5h://user:pass@us-east.proxy.com:1080',
  'socks5h://user:pass@eu-west.proxy.com:1080',
  'socks5h://user:pass@ap-south.proxy.com:1080',
];

for (const proxy of proxies) {
  const browser = await puppeteer.connect({
    browserWSEndpoint: `wss://bots.win/ws?apiKey=YOUR_API_KEY&proxy=${encodeURIComponent(proxy)}`,
  });

  const page = await browser.newPage();
  // Each session has a different geographic identity
  await page.goto('https://example.com');
  await browser.close();
}

Common Pitfalls

DNS Leaks

Using SOCKS5 instead of SOCKS5H sends DNS queries through your own resolver, not the proxy. Detection systems can compare your DNS server's location with your proxy IP's location. Always use SOCKS5H for automation.

WebRTC Leaks

WebRTC can expose your real IP through STUN/TURN requests that travel outside the proxy tunnel. BotCloud configures WebRTC to prevent these leaks by default.

Free Proxy Risks

Free proxies often inject content, log traffic, or share IP addresses among many users. For production automation, use reputable proxy providers with dedicated or semi-dedicated IPs.

Best Practices

1. Use SOCKS5H for all automation to prevent DNS leaks
2. Match proxy location to target audience - Use US proxies for US-targeted sites
3. Rotate proxies across sessions to avoid IP-based rate limiting
4. Monitor proxy health - Dead proxies cause timeouts that waste compute time
5. Use residential proxies for sites with strict datacenter IP blocking