I'm getting caught by Gmail verification despite proxies and special software?

[JamesBerullo]

So essentially, I'm trying to make a lot of differentiated online personas that are supposed to appear like real people. I want each persona to have its own social media accounts (gmail, Facebook, Twitter, Reddit, etc.) that clearly belong to the same "person" but I'm using proxies so that there is no way to connect each "person" to one another. I've got a bunch of dedicated proxies through Blazing Proxies that seem totally clean to me. I'm using Ghost Browser to manage the personas. Ghost Browser works by tracking cookies only for specific sessions and making each section completely separate from each other. They also let you give each session a specific proxy to use.

So in theory, it's supposed to be untraceable because Persona A is being run through a proxy in Miami and the cookies are all isolated from Persona B who is being run through a proxy in Chicago, and so on and so on for each Persona. But something is wrong, because after I created accounts for my first two personas without a problem, Gmail started asking me for verification for all my next ones. I'm not dumb, each persona is completely separate from each other and from my browsing history, so I don't understand how Google is picking it up.

There's two explanations that make sense to me but I don't know how I'd check which one is correct.

A: Ghost Browser might be the problem. It might not actually be keeping the cookies separate.
B: The proxies I'm using are HTTP proxies, not SOCKS proxies, so Google might be tracking me through that. I could switch my proxies to SOCKS proxies but I'm trying to use them for social media and I read that sites like Twitter don't work with SOCKS proxies.


Anyone have any advice or thoughts?

 

[Aaric]

They profile system!

 

[JamesBerullo]

Do you mean through UserAgent? Is that enough to recognize that it's me specifically?

 

[au2mopi]

He mean by UserAgent, Operating system, Screen resolution ... etc

 

[JamesBerullo]

Is there a way to vary all that? Ghost Browser is developing the ability to alter your User Agent but that functionality doesn't exist yet

 

[SMG]

Take a look at Windscribe (VPN)'s Split Personality:

• Split Personality - Rotates your browser's user agent every time you start your browser, which helps fight browser fingerprinting.

Don't know if it will help against Google but you could try testing it using Panopticlick.

 

[Redaline]

A: Ghost Browser might be the problem. It might not actually be keeping the cookies separate.
B: The proxies I'm using are HTTP proxies, not SOCKS proxies, so Google might be tracking me through that. I could switch my proxies to SOCKS proxies but I'm trying to use them for social media and I read that sites like Twitter don't work with SOCKS proxies.

There, there is your problem. Gentle introduction first...you must internalize that Google is a multi-billion dollar company that lives of their search & ads business. What that means is that they have all the necessary resources to get maximum out of existing technologies in order to track you.

I never had problem with them, simply because I don't "fight" them by trying to be smarter than 100k PhDs, but rather I make it impossible for them to track me on a technological level.

HTTP proxies fail for two possible reasons: actually one, but that one is replicated in two technological stacks:

1) Flash media connections - enables flash plugins to connect directly to media servers, bypassing your proxy settings and revealing your real IP. Remember that Flash is implemented as standalone DLL, which is basically a self-sustaining executable code running in the browser context. That is also the reason why so many exploits are done over it.

2) WebRTC & WebSockets - same thing, but in HTML5.

So, how do you get stealthy:

1) Use virtual machine
2) Use portable versions of the apps
3) Use Chromium instead of Chrome
4) Use VPN or mobile Internet connection from that virtual machine - There is one problem with VPN and that lies in a fact that Google mapped 90% of their exit connections. That in it self won't reveal you, but will seriously impede your work and for that reason I prefer mobile Internet.
5) Do not install any Google products in your virtual machine if you can avoid it
6) Change virtual machine settings, resolution, hardware (add more cpu's, add less memory), installed software...I personally don't dwell on this one, since I found no evidence that it plays any role if you do previous steps