Multi-Accounting Without Bans: Pairing Profiles With Proxies

Most multi-accounting bans are not caused by the browser. They are caused by two profiles sharing something they should not have shared — usually an IP address, occasionally a timezone, sometimes both at once.

An anti-detect browser fixes the fingerprint. It cannot fix the network. If you have already chosen a browser — and if not, the comparison is here — this is the other half of the setup.

What actually links two accounts

Platforms correlate accounts on signals that are expensive for you to vary and cheap for them to store. In rough order of how often they are the cause:

• Shared exit IP. Two profiles logging in from one address, minutes apart, is the strongest link there is. It needs no fingerprinting at all.
• Timezone and locale disagreeing with the IP. A profile on a Frankfurt address reporting America/New_York is a contradiction a real user cannot produce.
• Canvas, WebGL and font entropy. What the anti-detect browser exists to randomise.
• Behavioural timing. Six accounts that all post within the same nine-minute window every day.
• Recovery data. The same phone number or recovery email across profiles, which defeats every other precaution at once.

The first two are network problems. Get them right and the browser is doing the job it is good at instead of compensating for the job it cannot do.

One profile, one IP, for the life of the profile

The rule that matters: a profile's exit address should change as rarely as a real person's does. Real users do not appear in Frankfurt on Monday and São Paulo on Tuesday.

This makes rotating pools the wrong tool. Rotation is built for anonymity across many stateless requests; account management needs the opposite, which is continuity. Two products fit.

Static residential is the default. Each address is ISP-registered, leased to one customer, and unmetered — $3.50 per IP per week, falling to $2.28 at 250 IPs. Because bandwidth is not metered, a profile that idles all week costs the same as one that runs constantly, which is the right shape for account work. Two free replacements per IP per week cover an address that gets flagged.

Mobile LTE is the escalation, at $1.60 per IP per day. Carrier-grade NAT puts the profile behind an address shared with thousands of real subscribers, which is why platforms that have hardened against residential ranges still accept mobile. It costs roughly triple static residential per week, so reserve it for the platforms that need it rather than applying it to every profile.

Pinning an address to a profile in code

Whatever orchestrates your profiles, the proxy credential should be derived from the profile ID rather than assigned by hand. Hand-assignment is how two profiles end up on one address six months later.

import hashlib

def proxy_for(profile_id: str, country: str) -> str:
    """Same profile, same exit address, forever."""
    token = hashlib.sha256(profile_id.encode()).hexdigest()[:12]
    return (
        f"http://user-country-{country}-session-{token}"
        f":[email protected]:8080"
    )

On a static residential lease the address is fixed already and the session segment is redundant. On a rotating product the session token is what makes an exit sticky, and deriving it from the profile ID means the mapping survives a restart, a redeploy and a new machine.

Make the profile agree with the address

An address in Milan and a browser reporting Europe/London is a contradiction no genuine user produces. Every anti-detect browser lets you set these per profile; the discipline is deriving them from the proxy rather than filling them in from memory.

PROFILE_GEO = {
    "de": {"timezone": "Europe/Berlin",  "locale": "de-DE", "lang": "de-DE,de;q=0.9"},
    "us": {"timezone": "America/Chicago", "locale": "en-US", "lang": "en-US,en;q=0.9"},
    "gb": {"timezone": "Europe/London",  "locale": "en-GB", "lang": "en-GB,en;q=0.9"},
}

Four things must agree: the exit country, the reported timezone, the Accept-Language header, and the browser locale. WebRTC is the fifth — leave the browser's WebRTC leak protection on, because a WebRTC candidate carrying your real address defeats every other control in one request.

Selenium and Playwright against a profile

Driving profiles programmatically is where the network config is most often skipped. Both drivers take the proxy at launch:

from selenium import webdriver

opts = webdriver.ChromeOptions()
opts.add_argument(f"--proxy-server=http://gate.fleetproxy.com:8080")
driver = webdriver.Chrome(options=opts)

Chrome's --proxy-server flag cannot carry credentials, which is why so many Selenium setups end up on the machine's own IP after the auth prompt is dismissed. Use IP whitelisting on the FleetProxy credential so no prompt appears, or drive an anti-detect browser's local API, which passes user:pass through for you.

Playwright handles credentials directly and is the less error-prone option:

browser = playwright.chromium.launch(proxy={
    "server": "http://gate.fleetproxy.com:8080",
    "username": "user-country-de-session-prof07a2",
    "password": "pass",
})

Verify before you log in, every time

The cheapest habit in this entire workflow: on profile start, fetch your own IP through the profile and refuse to continue if it is not the expected one.

async def assert_exit(page, expected_country: str) -> None:
    await page.goto("https://api.fleetproxy.com/v1/ip")
    data = await page.evaluate("() => JSON.parse(document.body.innerText)")
    if data["country"].lower() != expected_country:
        raise RuntimeError(f"profile on {data['country']}, expected {expected_country}")

A proxy that silently stopped applying is not detectable from inside the session. It is trivially detectable from outside it, and one request is cheaper than one banned account.

Stagger the humans

Profiles that act in lockstep look like what they are. If six accounts post within the same nine minutes daily, timing alone correlates them regardless of IP separation. Randomise the window per profile — a fixed offset derived from the profile ID gives each one a stable routine, which is more human than fresh randomness every day.

A setup checklist

1. One profile, one address, for the profile's whole life.
2. Static residential by default; mobile only for platforms that reject residential ranges.
3. Derive the proxy credential from the profile ID, never by hand.
4. Match timezone, locale and Accept-Language to the exit country.
5. Leave WebRTC protection enabled.
6. Assert the exit IP on every profile start, before any login.
7. Give each profile its own activity window and its own recovery details.