Antidetect browser proxy settings and exit IP

Supported proxy protocols

Select the protocol supplied by your proxy provider: HTTP, HTTPS or SOCKS5. Enter Host and Port, plus User and Password when authentication is required. A website using HTTPS does not tell you which protocol to select for the proxy connection; use the provider's connection details.

In the profile editor's Proxy section, choose Library to use a saved entry or Custom to enter a connection for that profile. A static proxy stores a specific connection address. An extraction proxy obtains an address from the provider before using it to open the profile.

• Import common connection strings in bulk, including the format host:port:user:pass.
• Include the required credentials before checking a proxy that uses username and password authentication.
• Click Check and inspect the result. Saving the connection details alone does not confirm that the proxy is reachable.

Proxy library and profile assignments

Open Proxies → Proxy library to keep connections in one place. You can check proxies in bulk and inspect the detected exit IP, country, city, time zone and coordinates. Assign an entry to the appropriate store or account profile after confirming the result.

The library is shared within the team, with operations controlled by member permissions. Use proxy names to describe their intended purpose, but rely on the detected exit information when checking the actual location. After changing a profile's proxy, run the check again before continuing account work. See team management for organizing profiles and access.

Time zone, language and location

When a profile opens, the client resolves its proxy and checks the exit before applying the profile's network-related fingerprint settings. Select Follow IP for Time zone, Language or Location to use the detected exit location. Review each setting separately if the profile previously used custom values.

Recheck the exit after changing the proxy, selecting another extraction region or moving the profile to another computer. If the reported region differs from what you requested, inspect the node supplied by the provider first. Editing the browser's time zone will not move the network connection to another region.

Device templates, graphics information and stable noise remain part of the profile's fingerprint settings. Review those settings alongside the network configuration. For multiple accounts, keep a clear record of which profile uses which connection so that a proxy change can be checked against the intended account.

WebRTC policy

The profile's WebRTC setting offers Proxy only and Disabled. This controls a separate browser network capability, so include it in your review after assigning a proxy. Checking the exit used by an ordinary web page is only one part of checking the profile's network behavior.

Choose the policy according to the web features you use, then verify the relevant pages still work. A public checker can show the IP information visible through the browser. Record the proxy protocol, authentication and WebRTC setting with the profile's other configuration details so a teammate can repeat the check during a handoff.

Proxy extraction sources

Open Proxies → Sources to connect a provider's extraction API. Choose URL template for an extraction address with response parsing rules. Use Integration script when the provider requires request signing, token exchange or special response handling. The editor's Test panel shows extracted connections, exit information and failure details.

An extraction proxy in a profile or the library can select a source, a supported region and when to extract. Every time it opens requests another address. Only when the last IP stops working reuses the address cached during the current client run and extracts again after a failed check.

Opening a profile does not automatically switch to another region when the requested region has no available IP. It reports a failure. Automation plugins can define their own explicit regional fallback, so review that workflow separately. See proxy API extraction for source configuration and response handling.

Creating, editing and deleting sources requires proxy management permission. An integration script written or changed by another member needs approval before its first run on your computer. Existing workflows can also use sources through the automation tools.

Connection and location checks

Extraction requests leave from the computer running the client. If the provider uses an IP allowlist, confirm that your current computer's exit is authorized after changing computers or networks. Use the Test panel's response information to identify a configuration problem before repeatedly requesting another connection.

1. Check the static proxy or test the extraction source. Determine whether the failure occurs while obtaining an address or while connecting through it.
2. Verify protocol, host, port and authentication. If extraction succeeds but the connection check fails, inspect the returned connection details.
3. Resolve provider errors about an allowlist, API key, balance or permissions, then test again with the corrected settings.
4. Compare the detected country and city with the intended exit. Check both the provider's returned node and the region selected for the profile.
5. Review Time zone, Language, Location and WebRTC in the profile before signing in or starting a batch task.

FAQ