Hey guys, Reading tons of articles and posts from this forum for months. Right now I'm coding up a Google Account (of course Gmail account actually) generator. I have resolved the problem of dynamic IPs, real SIM based SMS verification. I have finished the Alpha version last week and had a 2 days tests on 2 VPS servers. The first day came well, every server had registered around 200 accounts per day. However, after around 24 hours I found these numbers dropped into 33 and fewer and fewer. My program cleared all shits like cookies, cache and whatever else in browser, and it is using IE as the browser core. Right now I think Google is still able to track the program and that was why the registration amount dropped down. I did a lot of search on line and this only has happened in the last several months it seems, as another guy I knew was having basically the same mechanism I have and his program was working well, till like 1 month ago the registration amount started dropping. I think there may be some kinds of mechanism Google is using now, for identifying the user registration, without using cookie and cache. There are 2 kinds of such thing out there for browser fingerprints to do the trick but Google must have its own tech. Any body has any information about this? Google should have been using something similar to this fingerprinting function via JS and transfer back a significant identification of a machine/browser to know that all the account registration actually are from the same guy. If any one can provide useful information about the mechanism of this, I'm willing to share the program with him. Any method to bypass this in mind would be appreciated! Thanks guys! For any possible idea!