Anti-detect browser · Setup pages
Kameleo
Give a Kameleo mobile profile a real mobile line, so the emulated device exits where it claims to be.
Kameleo's mobile profiles emulate a phone browser; a real carrier line completes the picture. One line per profile group, HTTP where possible.
Proxy string
Separate fields
Host: HOST Port: PORT Username: USER Password: PASS
HTTP proxy URL
http://USER:PASS@HOST:PORT
Protocol. HTTP is the simplest match for Kameleo profiles; SOCKS5 works when you bought the SOCKS5 port and keep DNS on the proxy.
Setup steps
Kameleo, step by step
- 1Create a profile, choosing a mobile device type if the account lives on a phone.
- 2Open the profile's proxy settings and choose HTTP or SOCKS5 to match your port.
- 3Enter host, port, username and password exactly as issued.
- 4Set timezone and geolocation to follow the proxy, and disable WebRTC leaks.
- 5Launch the profile and run the verification checks below.
Rotation link
Changing the IP on purpose
Kameleo has no rotation-link field; call the link from your script when you need a new exit. Do not rotate too frequently; it does more harm than good. Keep calls at least 5 minutes apart and check the status link before the next launch.
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 profile group per line, sized with the calculator.
| Platform | growth | maintenance |
|---|---|---|
| Instagram / Threads | 3 per line | 8 per line |
| TikTok | 3 per line | 8 per line |
| 3 per line | 8 per line | |
| 5 per line | 10 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
Kameleo and mobile lines
Yes. A phone fingerprint leaving from a datacenter or home connection is the mismatch platforms look for first.