Anti-detect browser · Setup pages
Multilogin
Route a Multilogin profile through a mobile line and keep the masking tied to the exit.
Multilogin is used by larger teams with shared workspaces. Assign lines per workspace group so an operator never launches two groups on the same exit.
Proxy string
Separate fields
Host: HOST Port: PORT Username: USER Password: PASS
HTTP proxy URL
http://USER:PASS@HOST:PORT
SOCKS5 proxy URL
socks5://USER:PASS@HOST:PORT
Protocol. HTTP(S) or SOCKS5, matching the port you bought. With SOCKS5 keep the proxy's DNS option on so lookups happen on the line.
Setup steps
Multilogin, step by step
- 1Create or edit a browser profile and open its proxy section.
- 2Choose HTTP(S) or SOCKS5, matching the credential set on the line's page in the portal.
- 3Enter host, port, username and password exactly as issued.
- 4Run the built-in check; it should resolve the exit country before you save.
- 5Keep timezone, geolocation and WebRTC masking set to follow the proxy IP.
- 6Launch the profile and run the verification checks below.
Rotation link
Changing the IP on purpose
Multilogin has no per-profile field for a rotation link in every version. Call the link from your workflow when you need a new exit, keep calls at least 5 minutes apart and confirm the change on the status link before launching the next profile. Do not rotate too frequently; it does more harm than good.
curl -s ROTATION_LINK # then poll until the exit IP has settled curl -s STATUS_LINK
The rotation and status links are on the line's page in the portal and in the API documentation. The daily allowance of customer-driven changes is in the fair-use policy.
DNS, timezone and leaks
Keep the fingerprint on the line
- Timezone: match the line's country. Austria and Germany run on Central European Time; for a US line, use the timezone an IP checker reports for the exit.
- Language and locale: match the account, not your desk. A German line running an Austrian account still wants de-AT.
- WebRTC: disable it or let the tool replace the WebRTC address with the proxy address. A leak here shows your real network to the site.
- DNS: with HTTP the site's hostname is resolved on the line. With SOCKS5 switch the tool to resolve DNS through the proxy (often called remote DNS or proxy DNS), or your resolver reveals your location.
- Geolocation: let the profile derive it from the IP, or set it to a city in the line's country. Never mix a US timezone with a European line.
Accounts per line
How many accounts on one line
One workspace group per line. Operators sharing a workspace share the exit when they launch on it.
| Platform | growth | maintenance |
|---|---|---|
| Instagram / Threads | 3 per line | 8 per line |
| 3 per line | 8 per line | |
| X / Twitter | 5 per line | 10 per line |
| 4 per line | 8 per line |
Verification checklist
Before the first account
- The tool's own proxy check passes and shows the line's country.
- Inside the launched profile, an IP checker shows a different public IP than your desk and a mobile-carrier network name.
- The timezone the site sees matches the country of the line.
- A WebRTC test inside the profile shows no address from your own network.
- A DNS-leak page inside the profile shows resolvers in the line's country, not your ISP's.
What each check proves is on the verification page.
Pitfalls
What goes wrong
- The rotation link is not a proxy address. It never goes into the host field.
- Pasting HTTP credentials into a SOCKS5 field, or the other way round, is the most common failed check.
- Do not rotate the IP too frequently; it does more harm than good. Change the exit when a group needs a fresh IP, not on a timer.
- Two profiles on one line share the same exit IP at the same time. Keep one account group per line.
Questions
Multilogin and mobile lines
Technically yes, since the line accepts any number of connections. They share the exit IP while both are launched, so treat the line as one account group, not one seat.