A BlackHatWorld thread title sums up the problem: "IG asks for phone number right after signup (fresh ISP proxy, AdsPower, new Proton email)". The visible part of the opening post lists the setup: "1 static US ISP proxy, one IP for one profile", and "AdsPower, Windows fingerprint, passed the BrowserLeaks tests". On paper, everything checked out. Instagram still wanted a phone number.
A browser profile controls what the browser reports. Some signals sit below the browser, and some have nothing to do with it. The basic proxy setup is on our AdsPower proxies page; this post covers what that page does not.
Why does a profile that passes BrowserLeaks still get flagged?
BrowserLeaks shows what your setup reports without grading it, and a clean IP, WebRTC and DNS result says nothing about your account, your behaviour, or the network layer under the browser.
People see the proxy address and no WebRTC leak, and call it a pass. Fair enough. But nobody outside Meta knows how Facebook or Instagram weighs its signals, and anyone quoting an exact formula is guessing. What we can do is separate three layers:
- What the browser profile declares: user agent, operating system, timezone, language, canvas and WebGL noise, WebRTC behaviour.
- What the network shows: the exit IP, its history, and the way the exit machine's operating system builds TCP packets.
- What the account is: its age, how it was created, how it behaves, and whether it was verified with a real phone.
AdsPower controls layer one. The proxy decides most of layer two. Layer three is yours alone.
What AdsPower's fingerprint settings actually control
AdsPower's settings change what the browser reports to JavaScript and in its headers, and its own help center lists them by name.
Two BlackHatWorld posters asked this. One wrote: "I want to use ads power to create, warm up and eventually use facebook accounts for advertising. What settings should I use?" Another: "Im having a hard time trying to figure what settings do I toggle on and off." A reply that shows up in the search preview of that second thread says: "Whether it's Adspower or Linken Sphere, I use the automatic digital fingerprint settings. The main thing is to import cookies and use good proxies."
The defaults are a reasonable starting point. Here is what they do, per AdsPower's fingerprint documentation:
- Timezone, Language and Location each default to "Based on IP". Timezone uses "timezone based on Ip location", Language uses "language based on IP location", and Location (geolocation) in that mode either asks each time or always allows. Custom and Block are the alternatives.
- WebRTC offers Forward, Replace, Real, Disabled and Disabled UDP. Replace uses "the WebRTC IP that matches your proxy". Real exposes your own address, so it has no place in a proxied profile. AdsPower's WebRTC article notes that with WebRTC closed, a website "will detect that you close the WebRTC".
- Canvas, WebGL, AudioContext, Media Device, Client Rects and SpeechVoices get "a random but consistent noise".
One setting matters most for a long-lived account. AdsPower's profile creation guide describes a random fingerprint mode in which "UA, WebGL metadata, CPU, RAM, and other data will be randomly generated upon browser startup." An ad account you run for months should look like the same computer every time. Generate one fingerprint and keep it.
"Based on IP" also assumes the IP's location is right. When a geolocation database misplaces an address, the profile copies the mistake. We covered that failure in My GoLogin profile looks right, so why doesn't the site trust it?, and it applies to AdsPower the same way.
The layer under the profile: the proxy exit's TCP/IP stack
With an HTTP or SOCKS5 proxy, the TCP connection the website receives is opened by the proxy exit, so the site sees the exit machine's network stack, not yours, and no browser setting changes that.
With HTTP CONNECT, the proxy opens a connection to the site and then, in the words of RFC 9110, restricts itself to "blind forwarding of data, in both directions". SOCKS5 works the same way: RFC 1928 describes the port "the server assigned to connect to the target host". The first packet the website receives (the TCP SYN) was built by the exit's operating system.
That packet carries an OS signature. The passive fingerprinting tool p0f reads it from the initial TTL, the window size, the MSS, the order of the TCP options and a few header quirks. Initial TTL alone splits the field: Windows commonly starts at 128, while Linux, macOS, iOS and Android commonly start at 64, as this write-up on TCP stack fingerprinting lays out.
Not everything comes from the exit. The CONNECT tunnel is what RFC 9110 calls "an end-to-end virtual connection" that can be "secured using TLS". So the TLS handshake and HTTP headers still come from your browser, and AdsPower shapes those. It never sends the TCP packets, and none of its documented fingerprint settings touch them.
You can see it yourself. BrowserLeaks' IP page has a "TCP/IP Fingerprint" block with an OS guess, MTU, hop distance and a JA4T string, and the TCP/IP Fingerprinting page breaks the packet down field by field. A JA4T value such as 64240_2-4-8-1-3_1460_7 reads as window size 64240, options MSS, SACK, timestamp, NOP and window scale, MSS 1460, scale factor 7.
Treat the OS guess as rough. Loaded from one of our own Linux servers, the IP page said Android. The researcher behind this TCP/IP fingerprinting tool also writes that from the SYN alone "it's not possible to discern whether it's an macOS device or an iOS device."
When the profile says iOS and the network says Linux
A mismatch between the operating system your profile declares and the one the exit's packets suggest is one more inconsistency a site can notice, not a known ban trigger.
On BlackHatWorld, under a thread about Reddit accounts in AdsPower, the preview of one post reads: "Adspower simulate iOS only from device side but not from IP side, most proxies emit Linux fingerprint for example." In another thread, a preview line reads: "you use cheap resitential proxies that scream linux and most likely are burned."
The idea is sound, with limits. p0f's own documentation has a flag for exactly this case, where the OS fingerprint does not match the user agent, and the incolumitas author built a classifier on the rule that "If the TCP/IP fingerprint operating system is different than the claimed User-Agent operating system, there must be something wrong with that client."
What nobody outside Meta can tell you is whether Facebook or Instagram uses it, or how much weight it gets. A mismatch is also common in honest traffic: any employee behind an office proxy shows the proxy's stack, not their laptop's. Treat it as noise you can remove, not as the reason your account died.
The cheap fix is consistency you control. A Windows profile over an exit whose TTL starts at 128 tells one story. An iPhone profile over a Linux-looking stack tells two.
Check your own exit before you tie an account to it
Open the profile in AdsPower, load browserleaks.com/ip through it, and compare the TCP/IP Fingerprint OS row with the operating system you picked for the profile.
Do it before the first login:
- If the OS row and the profile disagree badly (iOS profile, Linux-looking exit), change the profile's operating system before the account ever logs in. Changing it later is a device change.
- Run the same check on /tcp and note the initial TTL. 128 versus 64 is the clearest split.
On our side, plainly: we have not measured what OS each of our exits reports on this test. So test yours. Our static ISP proxies are server-hosted, and servers generally run server operating systems, so expect a non-Windows, non-iOS stack there. That is an expectation, not a measurement. ISP addresses are billed monthly per IP in Germany, the UK, the US, Hong Kong, France and Japan. Replacing one needs a paid IP Refresh Pass, so test before you build an account on it.
Our residential proxies are billed per GB, through gate.birdproxies.com on port 7777, with the country in the username (for example USER-country-us-session-ads1). Sessions rotate or stick for up to 60 minutes, so a residential test result belongs to that one session. That fits the r/VPN poster who wanted "a pay-as-you-go model, where the cost is calculated based on GB usage" for testing ad campaigns. Mobile 4G/5G runs in Germany, the UK, the US and Japan.
What neither a proxy nor a profile fixes
Account age, behaviour, phone verification and where the account came from are decided by you, and no proxy or fingerprint setting changes them.
The poster in the thread "Meta keeps banning my new accounts on proxies + antidetect browser" wrote: "I have static residential proxies with adspower to hide fingerprint and every time i create a new meta account i get banned." New accounts get the hardest scrutiny. Our post on Facebook's video selfie for new accounts goes through what the IP decided there and what it did not.
Phone checks are the same. When Instagram asks for a number right after signup, use a real number you own. We do not help anyone get around phone verification, create accounts in bulk, or evade a ban.
Bought accounts carry their history with them. Facebook's terms say to "Create only one account (your own)" and not to "transfer your account to anyone else" without permission. A clean profile and a fresh IP do not undo where the account came from.
When a site misbehaves, change one variable at a time. A reply in the preview of a BlackHatWorld thread about AI sites failing in AdsPower puts it well: "Try a fresh profile, clear cookies, and test a different proxy provider to narrow it down."
The setup that holds up is the boring one: your own ad accounts, one AdsPower profile per account, one fixed exit per profile, and a profile OS that fits the exit. If you run ads across a border, what the login IP decides covers the rest.
FAQ
Why does my AdsPower profile pass BrowserLeaks but still get banned?
BrowserLeaks shows what the browser and IP report. It does not score the account's age, behaviour or verification. A clean profile can still sit on a brand-new or bought account.
What AdsPower settings should I use for Facebook?
The defaults are a sound start: Timezone, Language and Location on "Based on IP", WebRTC on Replace, noise on canvas and WebGL. Avoid WebRTC Real, which exposes your own IP. For an account you keep, generate one fingerprint and leave it, instead of random generation at every startup.
Does a proxy show a Linux fingerprint?
It shows whatever the exit runs. With an HTTP or SOCKS5 proxy the site sees the exit's TCP stack, so a Linux exit reads as Linux. Test it rather than assume: load browserleaks.com/ip through the profile and read the TCP/IP Fingerprint OS row.
Should my AdsPower profile be iOS, Mac or Windows?
Pick the one that fits your exit. If the exit's initial TTL is 128, Windows fits. If it reads as Linux or Android, an iOS profile adds a second, contradicting story. Choose before the first login, because changing it later looks like a device switch.
Can AdsPower change my TCP/IP fingerprint?
No. With an HTTP or SOCKS5 proxy, the exit opens the TCP connection to the site, so its operating system builds the packets. AdsPower controls the browser, its headers and the TLS handshake, which still travel end to end through the tunnel.
Why does Instagram ask for a phone number right after I sign up?
New accounts get the strictest checks. No proxy or profile change removes the prompt. Use a real number you own.
