ADVO
Registered Member
- Oct 8, 2020
- 85
- 63
Hi everyone, in this thread https://www.blackhatworld.com/seo/a...dead-in-the-water-as-of-4-5-days-ago.1748680/ people have asked if we can have an up to date Proxy topic and I think just like anti detect browsers, proxy handling deserves its own discussion, it is a very important part of the tech stack when multi accounting.
As for credentials, I have an IT background and I am currently developing a Proxy IP pool cleaner application for a proxy provider.
This topic is important because if we as a community do not set up our proxies properly, we are all poisoning the well so to say, IPs get blacklisted very quickly and remain in circulation, they often get blacklisted because the anti detect was set up poorly which then leads to bad IPs in circulation, having profiles banned etc.
First, I want to state, just in case anyone is curious, a VPN is of no use for multi accounting, second I want to state this is not an instruction on how to do multi accounting web abuse, this is purely educational of course.
Step one, assuming the anti detect browser is set up properly, here is what we need to pay attention to.
People always ask who knows a good proxy provider, and then they get answers by some people who really know and by other people who have no expertise on the matter. It is much more important that you know how to check the quality yourself.
I will assume the hardest use case, aka a requirement where you need multiple sessions on a profile where the goal is that your emails stay alive when you log back into the profiles.
Note about proxy checkers:
Free "proxy score" lookup sites are often affiliated with proxy sellers and anti‑detect browsers and should be treated as promotional or beta ware at best, they are basically a landing page where they will lead you to buy something, which is okay, but it cannot be treated as a reliable source.
Many of the reliable checks are hidden behind paid APIs. Independent client‑side tools like BrowserLeaks are still useful for quick manual inspections because they surface IP hops, WebRTC/STUN leaks and other client‑side signals. You can use BrowserLeaks while switching between a sticky session and a rotating session to observe where the rotation actually lands. If your orginal IP was in London and then after the session ends you get assigned an IP in Belfast one minute later, you know this proxy is useless. If it hops more than 17 times, its useless.
Also be aware of IPv6 leaks: if your OS or browser prefers IPv6, DNS resolution, WebRTC, or dual‑stack TCP connections can expose a different IP family unless your proxy/anti‑detect stack handles IPv6 consistently (or you explicitly disable IPv6).
1 Datacenter vs Residential vs Mobile
Datacenter proxies
Run from servers in cloud/data centers.
Pros: cheap, fast, low-latency, lots of IPs and high throughput for scraping and automated tasks.
Cons: ALWAYS easier for services to detect and block because the IP ranges/ASN patterns look like cloud providers. Higher risk of being blacklisted quickly.
Residential proxies
IPs assigned by ISPs to residential customers.
Pros: look like regular home users, harder to block at scale, if an account is detected to be suspicious, your whole profile network is not compromised, very important!
Cons: more expensive, can have variable performance and availability, and provider quality varies a lot.
Mobile proxies
IPs from mobile carriers (3G/4G/5G). Often NATed and change frequently.
Pros: appear as real mobile connections; very trusted by many services.
Cons: high cost, high churn (IPs change often), sometimes limited concurrent connections, and unpredictable latency. And especiallynot useful in combination with Anti detect browsers where you emulate Laptops and PCs.
Pick carefully.
2 Sticky vs Rotating sessions
Sticky sessions
A session binds a client to the same IP for a configurable duration (seconds, minutes, hours).
Absolute must have where continuity is required, things like logging into an account, performing actions, and returning later without triggering re-authentication or risk from IP changes. If your session is unstable or disrupted during any of these actions, you can consider your profile compromised. Further, the new session must guarantee the same IP or something very close, as in same city close, else the service is useless.
Rotating sessions
The proxy hands you a different IP on each request or after short intervals.
Great for high-volume crawling, scraping, or when you must distribute requests across a large pool to avoid rate-limits. This is the ONLY use for rotating proxies, keep this in mind.
3 Why guaranteed sticky sessions matter
A provider that guarantees sticky sessions (and gives you control over session lifetime and the ability to end sessions on demand) provides operational control:
You can complete multi-step login flows without surprise IP swaps and many other reasons which are not listed here for brevity sake.
If a provider calls something "sticky" but doesn't let you control or reliably reproduce the session, it's functionally worthless for stateful uses.
5 After rotating, why you want the new IP to be "close" to the previous one
"Close" here means similar network characteristics (same city/region, same ISP or ASN and similar reverse DNS patterns).
The reasons:
Fingerprints stay consistent: Services look at geolocation, ASN, and latency as signals. A jump from, say, an ISP in Madrid to an IP from a cloud ASN in Singapore looks suspicious. Extreme example but THIS IS HAPPENING WITH SOME PROVIDERS.
Cookies and sessions tying: Some heuristics correlate IP geo/ASN with browser timezone and language, keeping those signals aligned avoids conflicting signals.
Thus, when rotating, prefer a rotation strategy that keeps you within the same region and ASN scope if the goal is to maintain apparent continuity.
6 Quick testing checklist
When evaluating an IP or pool, test these signals conceptually:
IP geolocation vs expected city/region.
ASN and reverse DNS patterns (do they look like home ISPs or clouds?)
TLS/HTTPS handshake behavior and certificates.
Latency and failure modes under load.
Whether the IP is on common blacklists or has previous abuse history.
Don't rely on any single test combine multiple checks to judge quality.
Practical hygiene suggestions
Keep session lifetimes reasonable and aligned with the type of activity.
Avoid reusing IPs across unrelated profiles, IP isolation reduces cross contamination.
Monitor IP reputation and retire IPs that show repeated failures.
Log session metadata (time, IP, user-agent, geolocation) for postmortem analysis.
As for credentials, I have an IT background and I am currently developing a Proxy IP pool cleaner application for a proxy provider.
This topic is important because if we as a community do not set up our proxies properly, we are all poisoning the well so to say, IPs get blacklisted very quickly and remain in circulation, they often get blacklisted because the anti detect was set up poorly which then leads to bad IPs in circulation, having profiles banned etc.
First, I want to state, just in case anyone is curious, a VPN is of no use for multi accounting, second I want to state this is not an instruction on how to do multi accounting web abuse, this is purely educational of course.
Step one, assuming the anti detect browser is set up properly, here is what we need to pay attention to.
People always ask who knows a good proxy provider, and then they get answers by some people who really know and by other people who have no expertise on the matter. It is much more important that you know how to check the quality yourself.
I will assume the hardest use case, aka a requirement where you need multiple sessions on a profile where the goal is that your emails stay alive when you log back into the profiles.
Note about proxy checkers:
Free "proxy score" lookup sites are often affiliated with proxy sellers and anti‑detect browsers and should be treated as promotional or beta ware at best, they are basically a landing page where they will lead you to buy something, which is okay, but it cannot be treated as a reliable source.
Many of the reliable checks are hidden behind paid APIs. Independent client‑side tools like BrowserLeaks are still useful for quick manual inspections because they surface IP hops, WebRTC/STUN leaks and other client‑side signals. You can use BrowserLeaks while switching between a sticky session and a rotating session to observe where the rotation actually lands. If your orginal IP was in London and then after the session ends you get assigned an IP in Belfast one minute later, you know this proxy is useless. If it hops more than 17 times, its useless.
Also be aware of IPv6 leaks: if your OS or browser prefers IPv6, DNS resolution, WebRTC, or dual‑stack TCP connections can expose a different IP family unless your proxy/anti‑detect stack handles IPv6 consistently (or you explicitly disable IPv6).
1 Datacenter vs Residential vs Mobile
Datacenter proxies
Run from servers in cloud/data centers.
Pros: cheap, fast, low-latency, lots of IPs and high throughput for scraping and automated tasks.
Cons: ALWAYS easier for services to detect and block because the IP ranges/ASN patterns look like cloud providers. Higher risk of being blacklisted quickly.
Residential proxies
IPs assigned by ISPs to residential customers.
Pros: look like regular home users, harder to block at scale, if an account is detected to be suspicious, your whole profile network is not compromised, very important!
Cons: more expensive, can have variable performance and availability, and provider quality varies a lot.
Mobile proxies
IPs from mobile carriers (3G/4G/5G). Often NATed and change frequently.
Pros: appear as real mobile connections; very trusted by many services.
Cons: high cost, high churn (IPs change often), sometimes limited concurrent connections, and unpredictable latency. And especiallynot useful in combination with Anti detect browsers where you emulate Laptops and PCs.
Pick carefully.
2 Sticky vs Rotating sessions
Sticky sessions
A session binds a client to the same IP for a configurable duration (seconds, minutes, hours).
Absolute must have where continuity is required, things like logging into an account, performing actions, and returning later without triggering re-authentication or risk from IP changes. If your session is unstable or disrupted during any of these actions, you can consider your profile compromised. Further, the new session must guarantee the same IP or something very close, as in same city close, else the service is useless.
Rotating sessions
The proxy hands you a different IP on each request or after short intervals.
Great for high-volume crawling, scraping, or when you must distribute requests across a large pool to avoid rate-limits. This is the ONLY use for rotating proxies, keep this in mind.
3 Why guaranteed sticky sessions matter
A provider that guarantees sticky sessions (and gives you control over session lifetime and the ability to end sessions on demand) provides operational control:
You can complete multi-step login flows without surprise IP swaps and many other reasons which are not listed here for brevity sake.
If a provider calls something "sticky" but doesn't let you control or reliably reproduce the session, it's functionally worthless for stateful uses.
5 After rotating, why you want the new IP to be "close" to the previous one
"Close" here means similar network characteristics (same city/region, same ISP or ASN and similar reverse DNS patterns).
The reasons:
Fingerprints stay consistent: Services look at geolocation, ASN, and latency as signals. A jump from, say, an ISP in Madrid to an IP from a cloud ASN in Singapore looks suspicious. Extreme example but THIS IS HAPPENING WITH SOME PROVIDERS.
Cookies and sessions tying: Some heuristics correlate IP geo/ASN with browser timezone and language, keeping those signals aligned avoids conflicting signals.
Thus, when rotating, prefer a rotation strategy that keeps you within the same region and ASN scope if the goal is to maintain apparent continuity.
6 Quick testing checklist
When evaluating an IP or pool, test these signals conceptually:
IP geolocation vs expected city/region.
ASN and reverse DNS patterns (do they look like home ISPs or clouds?)
TLS/HTTPS handshake behavior and certificates.
Latency and failure modes under load.
Whether the IP is on common blacklists or has previous abuse history.
Don't rely on any single test combine multiple checks to judge quality.
Practical hygiene suggestions
Keep session lifetimes reasonable and aligned with the type of activity.
Avoid reusing IPs across unrelated profiles, IP isolation reduces cross contamination.
Monitor IP reputation and retire IPs that show repeated failures.
Log session metadata (time, IP, user-agent, geolocation) for postmortem analysis.
