Man
Professional
- Messages
- 3,046
- Reaction score
- 571
- Points
- 113
Hey guys. So today I want to share with you what I believe is a really nice set up. I will be focusing on fv.pro but non only. Beating the checker is not a goal by itself, but when you do, it gives you credit to work with success. As I see it, if everything is clear on the set up itself, then if failure there is, they are not to blame on it. It is easier to spot what went wrong (behavior, cookies, BIN), and work on fixing those aspects only.
My experience is on working on laptop/desktop computer only. I will not go into cellphone settings.
INTRODUCTION:
Fv.pro, as others checker, is focusing on two main parts of the set-up. The first part being the browser. For that it will look if the browser, if google chrome for example is up to date. It will also check if the fingerprints are genuine. It will look for the webGL, the Canvas, the Audio, the Fonts, the client Rects, etc. if any of those are seen as fake, it will add some fraud score to our set up. And we don’t want that.
Our goal is to change the maximum settings that we can, to cover our identity, but without adding % to our fraud score. Antifraud system also has access to tools similar to fv.pro when not more sophisticated.
The second aspect of the checker is the connection itself. Fv.pro isn’t really accurate for the connection part. It can show 0% when the IP is actually in a blacklist, registered as a proxy or VPN. Defeating this part of the fv.pro is not difficult. However, if fv.pro show a fraud score to the connection part of the set up, then it is not good for us. Again, depending on the merch and on the antifraud that we want to beat. For some shops and merch, it will not really matter.
To cover our fingerprint, to me, two main solutions are available to us. The first being the Virtual Machine, and the second being the anti-detect browser. The two can also be combined sometimes (anti detect browser used inside a VM).
Today I want to focus on the antidetect, with whom I am more familiar with. Because I do not find VM convenient for work (this is my personal opinion only). On basic VM like virtual box, for me it always showed on fv.pro, that I was using an antidetect browser, and automatically gave me 50% fraud score on the browser part, so 25% on the total fraud score. But I could pass the connection part using socks 5 in direct. By using profixier and ******** as socks 5 provider. Also keep in mind that using a cellular sock will automatically be detected as a proxy since we are here using a laptop/desktop computer.
The following picture is using a VM: We can see that it is detected as an antidetect. However, the proxy is not seen (the IP being in a blacklist doesn’t really matter it is just a matter of changing it, the important part is not being spotted as using a proxy). Sometimes the Blacklist can result of a wrong DNS setting, in this specific case the IP is simply dirty and there is nothing to do apart changing it. On the VM using proxifier, it is required to change in the windows setting itself the DNS for the IPv4 to get the proxy not detected. If using straight proxifier then the fv.pro will see that we are using a proxy. I will not go into how setting up the DNS in the windows configuration itself, it can be looked up on google.
Part 2: Anti-Detect:
In a second time I will talk about the AntiDetect. In this field many options are offered to us, and depending on the needs or ease to use, one will prefer one or another. I am using currently two anti-detect, Linken Sphere, and Octo Browser.
On Linken Sphere, it is today, no matter what setting we use, impossible to not be seen as using an antidetect. Again, it is not necessarily a problem, but can be. If using socks 5 directly into the socks 5 input it will also be impossible to not be detected as using a proxy. We can then try to add the DNS we want in the Linken Sphere set up, but it will lead to additional problem, in additional checkers. And for this reason, to me the solution is not viable. We can also try to use a UDP from Wireguard config, that I will describe soon in the Thread. Then we will be able to beat the connection part of the fv.pro, but we will keep the detection of the browser. And then the 50% browser fraud score > 25% global fraud score.
On the following picture, we can see our score fv.pro, using Linken Sphere and socks 5. We get 30% fraud score in total. We could reduce that score to 25% using the UDP method, but the problem would be that it would need to change for each session, and it isn’t convenient to do, especially if we keep a 25% fraud score. The positive aspect of this set up is that we can input a lot of socks 5 at the same time into the Linken account, and work simultaneously on each of them without having to do any change, apart of replacing the logs of the socks every day. This method also comes with a cost. In the case of let’s say 15 profiles, it will cost around 1$ x 15 each day at minimum, so 15$, and more when one the socks is dying or blacklisted and need to be changed. The cost can quickly add up, for a result on fv.pro that isn’t really satisfying. Nevertheless, it isn’t a bad set up and can be worked on (I personally had success on Amazon, and different others merch using this exact set up and having this exact 30% fraud score).
But to my opinion, the ultimate goal is to have a perfect setting that is bullet proof, and not a “Good enough” set up.
Part 3: Perfect Set up
So now that we explored the benefits or not of the VM, and of Anti detect, lets get on the interesting part, the perfect set up (again in my opinion).
There are many ways fv.pro uses to detect proxy like > UDP support > TCP/IP Fingerprint > Latency > DNS Signature etc. If you want to bypass both fake browser + proxy detection, use Octo Browser + StarVPN https://www.starvpn.com
Octo browser have the same functionality than Linken Sphere, except that it does pass the fv.pro and is today (to my knowledge) the only anti detect that is not being directly detected when checked. The fingerprints that it offers are mostly the same than on Linken.
This is what it looks like on fv.pro using socks 5 with Octo Browser.
As we can see here, using OctoBrowser, we already reduced our score from 30% compared to LinkenSphere to 7%, using the exact same things which are socks5 from proxy LTE. We could have even go as low as 5% if we our IP wouldn’t be on a blacklist, using a clean IP.
For fingerpring, we are using a usual screen resolution (1920x1080). If our computer runs on windows 10, then we need to use our profile on windows 10. If our OS is windows 11, then run the profile on windows 11. This is because if we don’t, fv.pro will notice that OS don’t match and will give a fraud score on browser.
So just matching the windows session fingerprint with our actual OS we eliminate the 15% fraud score in the browser section.
We are using:
Now that we eliminated the browser aspect of the fraud and reached 0% browser fraud score, we want to get a 0% fraud score on the connection part. For that we will use the following tools
The DNS part is actually essential as without it the IP can be shown as Blacklisted and we don’t want that. And if we want to skip the cost of detect.expert (0.15$ per check), then we will face a problem if located in Russia: The DNS will always show you being in Germany, which is not good.
The Picture is here using the Wireguard UDP connection threw the Wireguard app, with a basic google DNS. In this specific case being 8.8.8.8, 8.8.8.8 . In my case I also had a problem with the google DNS 8.8.8.8, 8.8.4.4 because it systematically showed my IP as blacklisted.
One of the main things when doing the set up with StarVPN, is that it is divided in two parts, that are both needed, but not necessarily convenient. The web panel, from which can be extracted the “.conf”. And the App itself. The web panel let us access the “.conf”, but do not display the IP that we have, and the app does display the IP, but we can’t get the configuration from it. This appeared to be really confusing to me at first and definitively not convenient at the beginning.
The solution being for me that I update the IP only using the web panel. Never from the app itself. Because it will not necessarily update my Wireguard config, and then I just have an IP update credit lost.
What I do step by step is:
1: Select an IP from the state that I need, I use for ISP Sticky only (random). There is possibility to go for targeting ISP - Comcast, AT&T, and Spectrum.
2: I export the wireguard config into my wireguard app, and put my test session in Direct
3: On my Octo Browser test session, I stay connected on fv.pro, and refresh the page to get my IP and see if it dirty from fv.pro directly. I also look what is the ISP for my future DNS search.
4: My IP is clean, and doesn’t show proxy, then I check the IP on IPqualityscore and see if it actually clean (as I mentioned at the beginning of the thread, fv.pro can show clean when it isn’t in fact). If the IP is showed as blacklisted on fv.pro, it can be due to the DNS config itself, and so I keep on looking up on IPqualityscore, and do not automatically look for a new IP using an IP credit. (you have 1000 credit/M)
5: - A) My IP is dirty from qualityscore, it shows as Proxy or VPN status. All I need to do then is update IP on the StarVPN web panel, I do not need to change the “.conf” file in the Wireguard app, this is done automatically. Then I simply refresh the fv.pro and repeat step “2” and step “3”.
B) - If my IP is cleaned then I start to look for a matching ISP DNS on expert.detect. One trick that I have to see if the DNS is good is the following: If on the bottom on my computer screen connection icon, I see that I have no internet. The DNS is not working, I need to change it. If I see that the icon is showing normal Wi-Fi network, then the DNS is working but it will show my IP as blacklisted. If the Icon show secured connection, then the DNS is covering both proxy detection and Blacklist. However, it can be slow and then not suitable for work
6: I check the speed of my connection. For example, if I get 0.66mbps then the DNS is poor and even if everything is green, it won’t be suitable for work and will be detected as a proxy by other checkers due to the latency. That’s why I try to keep a DNS that give me at list 1.60mbps, ideally 2mbps+.
7: I search on detect.expert a correct ISP DNS that will match my IP and give me fast secured connection, and add it to my wireguard config, twice the same DNS.
In the case my connection is good secure but slow (less than 1mbps) I simply change the DNS always using the same ISP than the IP, until I find a DNS that give me fast connection. This step can be long at the beginning but after finding the DNS that suit my needs, I save it in my DNS/State file, for a later use.
8: After checking for connection speed + webRTC leaks + DNS leaks + any other additional check on browserleaks.com, I am ready to go.
As I mentioned with this set up in UDP the webRTC need to be in real. It will not leak Russia, but still need to be checked time to time, and will help beat the AF and fv.pro.
I then check that my DNS is correct on https://browserleaks.com/dns, and same with the webRTC on https://browserleaks.com/webrtc. If I want to check also if the DNS I use is really suitable, I can then go check the all set up on https://proxy.incolumitas.com/proxy_detect.html , with this specific set up you can beat this checker. But you will need your DNS to allow you to get 2.2mbps at list.
If you check the set up on https://botchecker.net/ you will have the proxy spotted. The only way to solve this is to then add your DNS directly into the OctoBrowser fingerprints config. Which is a bad idea because it will clear the botchecker, but show your proxy on any others checker. I keep the botchecker just to see if my fingerprints are good to go, and don’t care about the proxy result.
Here are all the links of the services/softwares/checkers that I have been mentioning:
Conclusion:
I tried to be as complete and extensive as possible in my explanations, for that anyone that start into setting up can understand and follow step by step the set up. This specific set up is to me perfect because it passes most of the checker, if not all when properly done. The cons of it would be that for each session it need to be redone. That’s why I use it now for working perfectly one session (for a valuable order for example), and when I finish, I switch to another session and redo the set up.
What I also do is as I mentioned is to keep track of the DNS that are good, after I tried them, the one that are fast. So, I can use the DNS on the specific location or city that I want to work on. It is pretty accurate doing, almost like would be a socks 5 selecting the ZIP code.
I also like the rotating IP aspect of it. It come with benefit such as being like any American citizen using a laptop, but also have cons such as sometime the rotating IP can be bad, and so the global setup requires a regular checking to make sure that everything still in the clear.
The big cons are that it can only be applied to one session at the time. If you look for a set up to run 30 amazon account at the same time, then it is not the best set up. It can still be updated by buying 3 slots on StarVPN at the cost of 70$.
The cost may also seem important but, if you look at it you get unlimited clean UDP tunnel, and at the end of the month when compared to the prices of socks5 you would have spent, it is quick to become cheaper to work with, with the benefit of being clean.
When starting with this set up it can be challenging, and long, but when using it for a time, you will have all your ISP DNS ready for the state you want, will be used to change the DNS in the Wireguard config quickly, and the all process will take you 5 minutes at most in between sessions switching. You can also say goodbye to most of captcha and questions about you being a robot using this set up.
I hope that this “guide” is clear and will help you success in the work. I wish you all good luck.
For any questions or help to set this up don’t hesitate PM and I will answer or help you whenever I have free time.
My experience is on working on laptop/desktop computer only. I will not go into cellphone settings.
INTRODUCTION:
Fv.pro, as others checker, is focusing on two main parts of the set-up. The first part being the browser. For that it will look if the browser, if google chrome for example is up to date. It will also check if the fingerprints are genuine. It will look for the webGL, the Canvas, the Audio, the Fonts, the client Rects, etc. if any of those are seen as fake, it will add some fraud score to our set up. And we don’t want that.
Our goal is to change the maximum settings that we can, to cover our identity, but without adding % to our fraud score. Antifraud system also has access to tools similar to fv.pro when not more sophisticated.
The second aspect of the checker is the connection itself. Fv.pro isn’t really accurate for the connection part. It can show 0% when the IP is actually in a blacklist, registered as a proxy or VPN. Defeating this part of the fv.pro is not difficult. However, if fv.pro show a fraud score to the connection part of the set up, then it is not good for us. Again, depending on the merch and on the antifraud that we want to beat. For some shops and merch, it will not really matter.
To cover our fingerprint, to me, two main solutions are available to us. The first being the Virtual Machine, and the second being the anti-detect browser. The two can also be combined sometimes (anti detect browser used inside a VM).
Today I want to focus on the antidetect, with whom I am more familiar with. Because I do not find VM convenient for work (this is my personal opinion only). On basic VM like virtual box, for me it always showed on fv.pro, that I was using an antidetect browser, and automatically gave me 50% fraud score on the browser part, so 25% on the total fraud score. But I could pass the connection part using socks 5 in direct. By using profixier and ******** as socks 5 provider. Also keep in mind that using a cellular sock will automatically be detected as a proxy since we are here using a laptop/desktop computer.
The following picture is using a VM: We can see that it is detected as an antidetect. However, the proxy is not seen (the IP being in a blacklist doesn’t really matter it is just a matter of changing it, the important part is not being spotted as using a proxy). Sometimes the Blacklist can result of a wrong DNS setting, in this specific case the IP is simply dirty and there is nothing to do apart changing it. On the VM using proxifier, it is required to change in the windows setting itself the DNS for the IPv4 to get the proxy not detected. If using straight proxifier then the fv.pro will see that we are using a proxy. I will not go into how setting up the DNS in the windows configuration itself, it can be looked up on google.
Part 2: Anti-Detect:
In a second time I will talk about the AntiDetect. In this field many options are offered to us, and depending on the needs or ease to use, one will prefer one or another. I am using currently two anti-detect, Linken Sphere, and Octo Browser.
On Linken Sphere, it is today, no matter what setting we use, impossible to not be seen as using an antidetect. Again, it is not necessarily a problem, but can be. If using socks 5 directly into the socks 5 input it will also be impossible to not be detected as using a proxy. We can then try to add the DNS we want in the Linken Sphere set up, but it will lead to additional problem, in additional checkers. And for this reason, to me the solution is not viable. We can also try to use a UDP from Wireguard config, that I will describe soon in the Thread. Then we will be able to beat the connection part of the fv.pro, but we will keep the detection of the browser. And then the 50% browser fraud score > 25% global fraud score.
On the following picture, we can see our score fv.pro, using Linken Sphere and socks 5. We get 30% fraud score in total. We could reduce that score to 25% using the UDP method, but the problem would be that it would need to change for each session, and it isn’t convenient to do, especially if we keep a 25% fraud score. The positive aspect of this set up is that we can input a lot of socks 5 at the same time into the Linken account, and work simultaneously on each of them without having to do any change, apart of replacing the logs of the socks every day. This method also comes with a cost. In the case of let’s say 15 profiles, it will cost around 1$ x 15 each day at minimum, so 15$, and more when one the socks is dying or blacklisted and need to be changed. The cost can quickly add up, for a result on fv.pro that isn’t really satisfying. Nevertheless, it isn’t a bad set up and can be worked on (I personally had success on Amazon, and different others merch using this exact set up and having this exact 30% fraud score).
But to my opinion, the ultimate goal is to have a perfect setting that is bullet proof, and not a “Good enough” set up.
Part 3: Perfect Set up
So now that we explored the benefits or not of the VM, and of Anti detect, lets get on the interesting part, the perfect set up (again in my opinion).
There are many ways fv.pro uses to detect proxy like > UDP support > TCP/IP Fingerprint > Latency > DNS Signature etc. If you want to bypass both fake browser + proxy detection, use Octo Browser + StarVPN https://www.starvpn.com
Octo browser have the same functionality than Linken Sphere, except that it does pass the fv.pro and is today (to my knowledge) the only anti detect that is not being directly detected when checked. The fingerprints that it offers are mostly the same than on Linken.
This is what it looks like on fv.pro using socks 5 with Octo Browser.
As we can see here, using OctoBrowser, we already reduced our score from 30% compared to LinkenSphere to 7%, using the exact same things which are socks5 from proxy LTE. We could have even go as low as 5% if we our IP wouldn’t be on a blacklist, using a clean IP.
For fingerpring, we are using a usual screen resolution (1920x1080). If our computer runs on windows 10, then we need to use our profile on windows 10. If our OS is windows 11, then run the profile on windows 11. This is because if we don’t, fv.pro will notice that OS don’t match and will give a fraud score on browser.
So just matching the windows session fingerprint with our actual OS we eliminate the 15% fraud score in the browser section.
We are using:
- WebGL > Fake
- Canvas > Fake
- WebRTC > Real (never fake, can be according to the IP but I don’t recommend)
Now that we eliminated the browser aspect of the fraud and reached 0% browser fraud score, we want to get a 0% fraud score on the connection part. For that we will use the following tools
- StarVPN Rotating Residential
- Wireguard Config
- Wireguard APP
- Detect.expert
- Ipqualityscore
The DNS part is actually essential as without it the IP can be shown as Blacklisted and we don’t want that. And if we want to skip the cost of detect.expert (0.15$ per check), then we will face a problem if located in Russia: The DNS will always show you being in Germany, which is not good.
The Picture is here using the Wireguard UDP connection threw the Wireguard app, with a basic google DNS. In this specific case being 8.8.8.8, 8.8.8.8 . In my case I also had a problem with the google DNS 8.8.8.8, 8.8.4.4 because it systematically showed my IP as blacklisted.
One of the main things when doing the set up with StarVPN, is that it is divided in two parts, that are both needed, but not necessarily convenient. The web panel, from which can be extracted the “.conf”. And the App itself. The web panel let us access the “.conf”, but do not display the IP that we have, and the app does display the IP, but we can’t get the configuration from it. This appeared to be really confusing to me at first and definitively not convenient at the beginning.
The solution being for me that I update the IP only using the web panel. Never from the app itself. Because it will not necessarily update my Wireguard config, and then I just have an IP update credit lost.
What I do step by step is:
1: Select an IP from the state that I need, I use for ISP Sticky only (random). There is possibility to go for targeting ISP - Comcast, AT&T, and Spectrum.
2: I export the wireguard config into my wireguard app, and put my test session in Direct
3: On my Octo Browser test session, I stay connected on fv.pro, and refresh the page to get my IP and see if it dirty from fv.pro directly. I also look what is the ISP for my future DNS search.
4: My IP is clean, and doesn’t show proxy, then I check the IP on IPqualityscore and see if it actually clean (as I mentioned at the beginning of the thread, fv.pro can show clean when it isn’t in fact). If the IP is showed as blacklisted on fv.pro, it can be due to the DNS config itself, and so I keep on looking up on IPqualityscore, and do not automatically look for a new IP using an IP credit. (you have 1000 credit/M)
5: - A) My IP is dirty from qualityscore, it shows as Proxy or VPN status. All I need to do then is update IP on the StarVPN web panel, I do not need to change the “.conf” file in the Wireguard app, this is done automatically. Then I simply refresh the fv.pro and repeat step “2” and step “3”.
B) - If my IP is cleaned then I start to look for a matching ISP DNS on expert.detect. One trick that I have to see if the DNS is good is the following: If on the bottom on my computer screen connection icon, I see that I have no internet. The DNS is not working, I need to change it. If I see that the icon is showing normal Wi-Fi network, then the DNS is working but it will show my IP as blacklisted. If the Icon show secured connection, then the DNS is covering both proxy detection and Blacklist. However, it can be slow and then not suitable for work
6: I check the speed of my connection. For example, if I get 0.66mbps then the DNS is poor and even if everything is green, it won’t be suitable for work and will be detected as a proxy by other checkers due to the latency. That’s why I try to keep a DNS that give me at list 1.60mbps, ideally 2mbps+.
7: I search on detect.expert a correct ISP DNS that will match my IP and give me fast secured connection, and add it to my wireguard config, twice the same DNS.
In the case my connection is good secure but slow (less than 1mbps) I simply change the DNS always using the same ISP than the IP, until I find a DNS that give me fast connection. This step can be long at the beginning but after finding the DNS that suit my needs, I save it in my DNS/State file, for a later use.
8: After checking for connection speed + webRTC leaks + DNS leaks + any other additional check on browserleaks.com, I am ready to go.
As I mentioned with this set up in UDP the webRTC need to be in real. It will not leak Russia, but still need to be checked time to time, and will help beat the AF and fv.pro.
I then check that my DNS is correct on https://browserleaks.com/dns, and same with the webRTC on https://browserleaks.com/webrtc. If I want to check also if the DNS I use is really suitable, I can then go check the all set up on https://proxy.incolumitas.com/proxy_detect.html , with this specific set up you can beat this checker. But you will need your DNS to allow you to get 2.2mbps at list.
If you check the set up on https://botchecker.net/ you will have the proxy spotted. The only way to solve this is to then add your DNS directly into the OctoBrowser fingerprints config. Which is a bad idea because it will clear the botchecker, but show your proxy on any others checker. I keep the botchecker just to see if my fingerprints are good to go, and don’t care about the proxy result.
Here are all the links of the services/softwares/checkers that I have been mentioning:
- https://fv.pro/check-privacy/general
- https://octobrowser.net
- https://www.starvpn.com
- https://www.wireguard.com/
- https://browserleaks.com
- https://www.ipqualityscore.com
- https://proxy.incolumitas.com/proxy_detect.html
- https://botchecker.net
- https://detect.expert/dnscheck
Conclusion:
I tried to be as complete and extensive as possible in my explanations, for that anyone that start into setting up can understand and follow step by step the set up. This specific set up is to me perfect because it passes most of the checker, if not all when properly done. The cons of it would be that for each session it need to be redone. That’s why I use it now for working perfectly one session (for a valuable order for example), and when I finish, I switch to another session and redo the set up.
What I also do is as I mentioned is to keep track of the DNS that are good, after I tried them, the one that are fast. So, I can use the DNS on the specific location or city that I want to work on. It is pretty accurate doing, almost like would be a socks 5 selecting the ZIP code.
I also like the rotating IP aspect of it. It come with benefit such as being like any American citizen using a laptop, but also have cons such as sometime the rotating IP can be bad, and so the global setup requires a regular checking to make sure that everything still in the clear.
The big cons are that it can only be applied to one session at the time. If you look for a set up to run 30 amazon account at the same time, then it is not the best set up. It can still be updated by buying 3 slots on StarVPN at the cost of 70$.
The cost may also seem important but, if you look at it you get unlimited clean UDP tunnel, and at the end of the month when compared to the prices of socks5 you would have spent, it is quick to become cheaper to work with, with the benefit of being clean.
When starting with this set up it can be challenging, and long, but when using it for a time, you will have all your ISP DNS ready for the state you want, will be used to change the DNS in the Wireguard config quickly, and the all process will take you 5 minutes at most in between sessions switching. You can also say goodbye to most of captcha and questions about you being a robot using this set up.
I hope that this “guide” is clear and will help you success in the work. I wish you all good luck.
For any questions or help to set this up don’t hesitate PM and I will answer or help you whenever I have free time.
Last edited:
