If you work with social networks, casinos, bookmakers and other companies that use a system that detects multi-accounting, then most likely you know the basic principles of anonymity (browser anti-detection, proxy, vpn and other bypass schemes). In addition to them, of course, the detection of non-standard situations can also occur by behavioral factors. But today we will look at a selection of online services that show how anonymous your antidetect browser + proxy bundle is.

 

Let’s start with services for checking the anonymity of the browser. 

We have almost no influence on this part of anonymity. Therefore, with this services you can analyze your antidetect browsers:

– whoer.net is the easiest anonymity checker. It shows the main anonymity problems and solutions to fix them;

– browserleaks.com – a set of separate tests for everything and everyone;

– deviceinfo.me – rather just a set of features of your browser than a test. Suitable for proxy test;

– f.vision – from the creators of Linken Sphere. It checks IP against 77 bases;

– iphey.com – in some cases even better than pixelscan;

– pixelscan.net – is considered the best checker in the community;

– 2ip.ru/privacy – a simple browser privacy test. There are also many useful functions related to checking for anonymity;

– coveryourtracks.eff.org – a browser check service that shows how well you are protected from being tracked and fingerprinted;

– amiunique.org – shows the level of relevance of your browser’s fingerprint;

–browser spy.dk – shows how much information can be obtained from your browser when visiting a page;

– aida64.com – a program that checks your hardware;

– fingerprint.com – a tool for identifying anonymous site visitors with accuracy based on a combination of several parameters;

– audiofingerprint.openwpm.com – AudioContext fingerprint check.

 

In fact, there are quite a few anonymity testing services, but when improving only anonymity, you should not forget about other factors. It is much more difficult to cover them.

 

Now let’s talk about the integrated approach when working in social networks, which we use in our work.

 

After a relatively successful analysis of your antidetect browser + proxy combination, you can set up scenarios with the required level of randomness. It can be set both inside the action (spintax action, pauses between actions, ranges of pauses and quantities in the actions themselves), or set by us at the system level. Each internal action is different, even within the same scenario. There are no equally pressed buttons. When typing symbols, randomization algorithms are also incorporated.

 

Having considered the main privacy issues, you can create an anonymity checklist:  

  • Setting up a bunch of antidetect browser + proxy (we check it with services)
  • Separation of accounts to different IP addresses
  • Using different content for accounts (at least using spintax)
  • Using Ranges of Pauses and Actions
  • Image randomization (at least removing image info)

 

Now let’s go through behavioral anonymity using the example of the social network Facebook. We think it is the same for all social networks approximately. 

So, the most important trigger we look at when boosting accounts is checks when farming. If in the process of farming more than 10-15% of accounts go out for checking, then this is a sure sign that you need to revise the farming system:

 

1) Accounts.

If you buy auto-registrations in stores like djekxa and similar, it’s immediately “no”. We recommend using your autoregs on iphone or an emulator like BlueStacks or Memu. There is also an option to register for the browser, but before this registration, you need to warm up the account well.

 

2) Proxy.

We tried to use a variety of proxies for farming: IPv4, IPv6, residential, mobile.

-IPv6 – immediately “no”. We have not been able to use them at all for a long time. Everything goes out for checking.

-IPv4 – about six months ago we used IP4 statics and everything seemed to be fine. But now we can’t find normal ones at all. Most likely, Facebook introduced an additional filter and sees that they are server-based.

– Residential – not bad at all, but on a scale it will not pay off.

-Mobile – today it is the best option. Usually we set proxies for 1-2 accounts

 

3) Antidetect browser.

The advantage of our tests is that we can check 500-1000 accounts, and in this case, you can immediately see which segment and percentage crashes. There are various types of antidetect browsers, but at the moment we use AdsPower for our projects. He solved most of the problems when working a lot and FB is loyal to him. It has a normal API, there are no constant lags. There is a loading of extensions in all profiles at once. For us, this is critical, because uploading 1000 profiles by hand is simply utopian. And its prices are slightly lower than all on the market.

 

4) Farm scheme.

A lot has been said on this topic and there are different approaches. Someone farms for 5 days, someone for a month. We are constantly testing different methods and at some points there were developments when it was not yet public.

 

Telling you collectively about our approach and the rules that we follow to:

  • if the account flew out to the check, then we throw it out;
  • we have a tested farming period, approximately 14 days, and we stretch all activities for this period;
  • before authorizing the account, we warm up the profile, directly with those interests for which the account will be farmed;
  • we do not focus on limits, but proceed from the logic of the average person. All our scripts are written in the likeness of the work of an active living character. We think the lively farming style is more to the taste of Facebook AI. It is believed that this type of user will bring it more money;
  • we separate the actions of accounts from under the same IP and different sessions. We try to launch accounts with proxy reboot before each account. But if we hang 2 accounts on one proxy, then we don’t do actions on accounts at one moment. This also applies to the separation of activities within the same account on different browsers;
  •  the service randomizes patterns of behavior. We only indicate the ranges of pauses and the number of actions;
  • during the entire farm and work with the account, we continue to warming cookies up on third-party sites;
  • we stick to a clear line of farming interests. Starting with warm cookies up, we have clear interests set up. For example, the account has sports theme. This means that the sites that the account goes to will be mainly of a sports theme. Search and entry into the Fan Page and sports groups, an autoresponder for sports topics, viewing sports videos, working with a sports external page, etc .;
  • account viability checklist. There are different accounts (and, most likely, these are system bugs): some may fly out for a checking during authorization; others do not show recommendations; for others, ads in the feed are not shown for a long time; some accounts cannot create a Fan Page or Business Manager. Therefore, we have compiled a list of points through which a standard account must pass. If one or two accounts don’t pass, then this is the okay; if the entire network starts to fall off so it is the indicator when the farming system needs to be adjusted. Now we have added metrics to the dashboard and will soon add filters. This allows for more automated tracking of key farming points.