Proxies

A website sees two things about every visitor: the browser fingerprint and the IP address the request comes from. Kameleo builds the fingerprint, and a proxy supplies the IP. Together with stored data such as cookies, they make up the identity of a profile. If two profiles share an IP, or a profile claims to be in Berlin while its IP sits in Texas, detection systems can link or flag them no matter how good the fingerprint is.

How a proxy works

A proxy is a server that forwards your traffic. Your browser connects to the proxy, the proxy connects to the website, and the website only sees the proxy's IP address. DNS lookups also happen on the proxy, so your local resolver never learns which sites the profile visits.

Kameleo supports three proxy protocols:

Protocol How it works Credentials Encrypted link to the proxy Carries UDP traffic
HTTP Tunnels each connection through the proxy. Kameleo automatically detects whether the proxy speaks HTTPS. Optional Only with HTTPS No
SOCKS5 Forwards raw network connections, not just web requests. Optional No On Chroma, if the provider supports UDP
SSH Kameleo logs in to an SSH server and uses it as a SOCKS5 tunnel. Handy if you run your own server. Username and password required Yes No

Credentials are optional for HTTP and SOCKS5 because many providers can allowlist your own IP address instead. The encrypted link matters on networks you don't trust: without it, anyone on the path to the proxy can read your proxy credentials and the hostnames you visit. Pages loaded over HTTPS stay encrypted end to end with every protocol.

Proxy types

Proxy providers sell IPs from different sources, and detection systems trust them differently:

Type Where the IP comes from Trust from detection systems Trade-off
Datacenter Hosting and cloud companies Low Fast and cheap, easy to recognize
ISP Consumer ISPs, but hosted in data centers Medium to high Stable and fast, costs more
Residential Real home connections High Slower, usually billed per GB
Mobile Mobile carriers, shared by many users at once Highest Most expensive

Providers also decide how often the IP changes. A rotating proxy hands out a new IP per request or per time interval, while a sticky proxy keeps one IP for a session, usually set by a session ID in the proxy username.

Many anti-bot systems bind their cookies to the IP that received them, so an IP change mid-session can trigger a new challenge. For scraping, rotate between profile runs and stay sticky within a run. For long-lived accounts, keep the same IP as long as you can.

How Kameleo applies a proxy

Each profile has its own proxy. Kameleo applies it at start, and it stays fixed until the profile stops.

Before the browser opens, the Kameleo Engine checks the proxy and sends a request through it to learn the public IP and its location. The browser then sends all page traffic through the same proxy. To attach, test, or remove a proxy, follow Using proxy servers.

flowchart LR
    Engine[Kameleo Engine] -. IP and location lookup at start .-> Proxy[Proxy server]
    Browser[Browser profile] -- Page traffic and DNS --> Proxy
    Proxy -.-> Lookup[Kameleo location service]
    Proxy --> Website[Website]

Settings derived from the IP

Three profile settings follow the proxy IP when you set them to automatic:

Setting With automatic
Timezone Matches the time zone of the proxy's location.
Geolocation Reports coordinates near the proxy's location.
WebRTC Shows the proxy's public IP instead of your real one.

You can set each value manually instead, or block geolocation and WebRTC entirely, although a browser that refuses these APIs looks unusual. In automatic mode, Kameleo reads the IP and location when the profile starts and refreshes them every few minutes. If a rotating proxy switches IP mid-session, the automatic settings can lag behind until the next successful refresh.

Network protection

A proxy hides your IP only for the traffic that goes through it. Kameleo adds the following protections against leaks that skip the proxy or reveal your machine:

Protection Chroma Junglefox
HTTP/3 (QUIC) over SOCKS5 Yes Not yet supported
WebRTC UDP over SOCKS5 Yes Not yet supported
Local port scan protection Yes Not yet supported

The first two work only with a SOCKS5 proxy whose provider supports UDP, sometimes listed as UDP ASSOCIATE. HTTP and SSH proxies cannot carry UDP.

HTTP/3 (QUIC) over SOCKS5

Many sites serve pages over HTTP/3, which runs on QUIC over UDP. On Chroma, Kameleo sends QUIC traffic through a SOCKS5 proxy by default whenever the provider supports UDP. When UDP cannot go through the proxy, the browser falls back to TCP, which does go through the proxy, so QUIC never leaks. You don't need to configure anything.

WebRTC UDP over SOCKS5

WebRTC powers video calls and peer-to-peer connections, and it prefers UDP. On Chroma, Kameleo sends WebRTC UDP traffic through a SOCKS5 proxy by default whenever the provider supports UDP.

When UDP cannot go through the proxy, WebRTC sends it directly. Kameleo already replaces the IP that WebRTC reports to JavaScript, but the direct connection can still reveal your real address. This applies on Junglefox, and on Chroma with HTTP or SSH proxies or SOCKS5 proxies without UDP support. To close that gap, limit WebRTC to proxied TCP as shown in Using proxy servers.

Local port scan protection

A website can use WebRTC to probe addresses on your own machine from inside the page, for example by trying to connect to localhost. Open ports reveal local services such as remote desktop tools or automation servers, and that gives detection systems another signal to link or flag a profile. Chroma blocks these probes to loopback addresses by default. If a legitimate app needs that access, you can turn the protection off.

Best practices

  • Give every profile its own proxy. A shared IP links the profiles that use it.
  • Keep the same proxy, or at least the same region, for a profile across sessions.
  • Leave timezone, geolocation, and WebRTC on automatic.
  • Set the profile language to match the proxy country.
  • Use residential or mobile proxies for accounts, and save datacenter proxies for targets with little protection.
  • If your provider does not support UDP, or you use Junglefox, limit WebRTC to proxied TCP.