Dolphin Anty and Proxies: Setup Guide
Configuring a proxy per Dolphin Anty profile: choosing address types per platform, binding with sticky sessions, and the mistakes that link accounts.
- antidetect-browsers
- multi-accounting
Dolphin Anty assigns a proxy at the profile level, which is the right model. The work is in choosing the right address for each profile and binding it so it stays put.
This is a setup guide for the proxy side. The general principles are in Why Antidetect Browsers Need Proxies, and the step-by-step walkthrough with screenshots is in our Dolphin Anty integration guide.
Choose the address type per platform
The address has to be plausible for the platform the profile signs into.
| Platform | Address type | Notes |
|---|---|---|
| Business and ad dashboards | Static ISP | Stable, fast, business-plausible |
| Social accounts | Mobile or residential | Consumer range matches real usage |
| Marketplaces | Sticky residential or ISP | Consistency across long sessions |
| Read-only research | Rotating residential | No login, rotation is fine |
A profile on a datacenter range will work until the platform decides it should not, and then the account is flagged rather than the proxy. The reasoning is in ISP Proxies vs Residential.
Bind one address per profile
Dolphin Anty accepts a proxy string per profile. Two shapes:
http://user:pass@host:port
socks5://user:pass@host:port
For account profiles, include a session parameter so the exit address holds:
http://user-session-acct014:pass@host:port
Without the session parameter, some providers rotate the address on every request even though you thought you had a sticky endpoint. The mechanics are in Understanding Proxy Session IDs.
Match the profile to the address
Four fields need to agree with the address, and all four are in the profile settings:
- Timezone. Should match the address country, and ideally the region.
- Language and locale. A Polish profile from a German address is a mismatch on the first request.
- User agent. Should be plausible for the device the profile claims to be.
- Geolocation override. Keep it aligned with the timezone rather than setting a third, unrelated location.
Coherence across those fields matters more than any single value. A plainly configured profile in the right place beats a heavily randomised one that contradicts itself.
Team workflow
When more than one person runs profiles, two things prevent accidents:
Ownership. Assign each profile to one operator. Shared profiles mean shared browsing habits, which is its own signal and a coordination problem.
No ad hoc rebinding. Changing a profile's address should be a logged event, not something anyone does to fix a slow session. A changed address mid-life is one of the most visible signals there is.
Keep the binding record outside the app, with profile id, endpoint, country and assignment date. If an account is challenged later, that record tells you whether the address moved.
Verify before you work
Two minutes of checks per profile at setup.
- Open the profile and load the Proxy Checker. Confirm the exit address is the one you assigned.
- Confirm the country via the IP Lookup and compare it to the profile timezone.
- Run the WebRTC Leak Test. A leak exposes the host address and undoes the profile.
- Load a public fingerprinting page and check for contradictions rather than trusting a "passed" label.
Common mistakes
Sharing one endpoint across profiles. The clearest linkage signal, and it survives every other isolation measure. See Avoiding Residential IP Reuse.
Rotating a logged-in profile. Sessions get invalidated and re-verified. Covered in Rotating IPs for Browser Profiles.
Ignoring the leak. A WebRTC leak means every profile on the machine shows the same real address regardless of assignment.
Skipping the language field. A profile that says en-US from a Warsaw address is not fatal for a traveller, but it is a contradiction that adds up with others.
Reusing an address from a burned account. Reputation travels with the address. Retire it rather than reassigning it.
Where proxies fit in the stack
The profile manager handles isolation, and the address layer handles credibility. Neither substitutes for the other, and accounts get flagged when one of the two is neglected.
For the address layer, see IP Quality and Reputation, and for the products, Residential and Mobile.