Which proxy type per workload
This single decision matters more than any setting inside the browser. Pick by what the profile does, not by price:
| What the profile does | Proxy type | Why |
|---|---|---|
| Long-lived accounts, one identity each | Static residential / ISP, dedicated | The platform expects to see the same address tomorrow; a changing IP on a logged-in account is the loudest signal there is |
| Social platforms with strict checks | Mobile, one port per identity | Carrier NAT means thousands of real subscribers share it — the hardest type to act against |
| Registration waves, farming new accounts | Rotating residential, sticky session | A fresh IP per profile at signup, held for the whole session |
| Scraping through a profile | Rotating residential per GB | Volume work; identity is irrelevant |
| Anything with a login | Never datacenter | Hosting ranges carry the abuse history of every previous tenant |
The setup, field by field
Dolphin Anty keeps proxies per profile, and you can save them in the proxy manager to reuse across profiles. What you paste is the same four things every provider issues:
- Type — SOCKS5 if your provider offers it, HTTP otherwise. SOCKS5 carries more protocols and does not rewrite headers.
- Host and port — straight from the provider dashboard.
- Login and password — authenticated proxies only. If a proxy needs no credentials, everyone who found that list is on it with you.
- One proxy per profile. Reusing an IP across profiles links those accounts together permanently, and that is the mistake that takes out whole batches at once.
Then the part most people skip: set the profile timezone and language to match the IP country. A German IP with an Asia/Dhaka clock is a contradiction any risk system checks for free, and it undoes everything the fingerprint spoofing bought you.
Why the built-in checker is not enough
Dolphin's proxy check confirms the proxy responds and reports its exit IP. Useful, and also the easy half. It does not tell you whether the IP sits in a hosting range, whether your requests arrive carrying X-Forwarded-For, or whether WebRTC is handing out a second address behind the browser's back.
Run the profile against our IP check and leak test before you touch a target site. It prints the autonomous system and its owner — so a hosting range sold to you as “residential” is obvious in seconds — plus the header, timezone and WebRTC checks that decide whether the profile survives.
What a profile actually costs to run
The honest arithmetic, because “how many profiles can I afford” is the real question:
- Farming and short-lived profiles: rotating residential per GB. A profile doing light browsing burns well under a gigabyte, so cost per profile lands in cents, not dollars — and with non-expiring traffic you buy once and draw down as you go.
- Long-lived account profiles: a dedicated static IP per profile, a few dollars a month each. This is where people try to economise by sharing one IP across five accounts, and it is exactly the shortcut that loses all five.
- High-risk platforms: a mobile port, the most expensive per identity and the only thing that holds on the strictest targets.
Practical rule: the IP should cost a fraction of what the account is worth. If an account matters enough to build a fingerprint profile for, it matters enough not to share its address.
Five mistakes that kill Dolphin profiles
- Sharing one IP across profiles. Links the accounts. Irreversible once noticed.
- Free or public proxies. Shared with hundreds of strangers and frequently already banned on your target.
- Timezone not matching the IP. Free, instant contradiction.
- Rotating IPs on a logged-in account. Use sticky sessions or a static IP; a mid-session country change is a hard flag.
- Trusting the seller's label. “Residential” is a word, not a guarantee. Check the ASN yourself.
More on the browser-agnostic side of this in our antidetect browser proxy guide, and the type breakdown in the residential proxy guide.