For the complete documentation index, see llms.txt. This page is also available as Markdown.

Multilogin

Multilogin is the most fingerprint-fidelity-focused option among antidetect browsers. Its proxy support covers all helodata products.

Per-profile setup

  1. New profileProxy section.

  2. Connection type: HTTP or SOCKS5.

  3. Fill in:

Residential / Mobile (gateway)

Field
Value

Host

gate.helodata.io

Port

7777

Login

helo_s1a2b3c4d5e-type-res-region-us-session-prof01-sesstime-30

Password

sub-user password

ISP

Field
Value

Host

198.51.100.42

Port

8000

Login

helo_s1a2b3c4d5e

Password

sub-user password

  1. Click Check proxy — Multilogin probes and shows the exit IP, country, and timezone.

  2. Multilogin will offer to auto-match fingerprint to the proxy's country. Accept it.

[screenshot: Multilogin profile creation with helodata proxy]

Bulk via API

Multilogin's Local API can create profiles programmatically — useful for spinning up N profiles, each bound to one ISP IP:

Loop over your ISP list to provision profiles in seconds.

Fingerprint match

Multilogin's strength is matching the browser fingerprint to the proxy's locale. Enable Match fingerprint to proxy country:

  • Language headers align with the country

  • Timezone derives from the proxy IP

  • WebGL / Canvas fingerprints are randomized within country norms

Verify

Hit https://browserleaks.com/ip + https://browserleaks.com/javascript and check IP, timezone, navigator.language all align.

Common pitfalls

  • MultiloginProxyError: AUTHENTICATION_FAILED — gateway products require the full username (helo_...-type-res-region-us), not just helo_s1a2b3c4d5e.

  • Profile launched before proxy check — Multilogin will sometimes hold a stale proxy in memory; restart the profile after editing.

Last updated

Was this helpful?