What is the best Antidetect Browser?

Multilogin is best, but expensive
What? Man…. Seriously? Im expert in fingeprints and I saw multilogin is a joke.
You tell use why you think multilogin is ok and I tell you why is not. Want arguments!!!
 
You better use a natural browser.
Try ivanovation, work with all kind of browsers, firefox chrome edge, he also have firefox portable so you can test wich is better for your needs
Hello. I'm interested by Ivanovation. Do you offer a trial ? Thanks
 
Have you tried GenLogin? It provides free Automation tool to design, develop and serve your automation tasks
 
Hello. I'm interested by Ivanovation. Do you offer a trial ? Thanks
Im not a seller, sorry, Im only a fingerprint expert, who dont like to see how peoples are tricked by this low antidetect softwares. Is just marketing.
Learn, study about fingerprints before you buy. Everybody can write “wow I use that and that and is awesome and is working” without tehnical arguments dont trust nobody :)
 
Im not a seller, sorry, Im only a fingerprint expert, who dont like to see how peoples are tricked by this low antidetect softwares. Is just marketing.
Learn, study about fingerprints before you buy. Everybody can write “wow I use that and that and is awesome and is working” without tehnical arguments dont trust nobody :)

Or do the reverse method, say the market leader is trash but don't deliver arguments.
 
Or do the reverse method, say the market leader is trash but don't deliver arguments.
Well, I already let arguments on another forum, but if you insist then I will argue with you about any antidetect software from the market not just the leader :)
 
Well, I already let arguments on another forum, but if you insist then I will argue with you about any antidetect software from the market not just the leader :)

Why is MultiLogin "trash"?
 
Why is MultiLogin "trash"?
Is many ways that can be detected, trough resolution, fonts, canvas, webgl, almoust on all fingerprints, and also even if all fingeprints wold be ok, is still not enought to defeat tracking services.

1. resolution - they spoof resolution and the fake resolution can be detected instantly by any website with a simple javascript code who read “viewport” resolution especially if the real screen resolution is set with zoom DPI

2. Fonts - they only spoof the name of fonts, but if a website check for that font name who is not exist in the system, simply load that font and make the measures “GLYPHS” who read the hight and widh and weight if the font, and will not match on statistics. If a font dont exist by his name then the system will load the next default font available in the system wich mean also that all fonts used in spoof will generate same font parameters identical.

3. They dont change non uniq canvas, and canvas noise generate a uniq canvas who do not statisticslly exist in any real device . This will result 100% in a reject

3. webgl, same problem as canvas

4. timezone dont solve the timestamp fongeprints “ time discrepancy” wich is the diffrence time between your device and the website server time, you have to always sincronize time and date to be most accurate. Otherwise this coult be a uniq fingeprint who target your device.

5. webrtc udp IP, simple try to comunicate with fake ip spoofed in webrtc will result in no responde, wich mean is fake!

They dont change hardware. Websites can acces some devices, especially audio video and graphic, can see device graphic version, install date, device id, not just the vendor

+ many other secret tricks that tracking services could use to target you!
If you spoof, you die, this is a golden rule!!! Any antidetect who use spoof methods are not safe.
 
1. resolution - they spoof resolution and the fake resolution can be detected instantly by any website with a simple javascript code who read “viewport” resolution especially if the real screen resolution is set with zoom DPI

Is limited by browser window as well. Tor Browser is a good example of that, it changes the browser size. Display resolution is very standard, 100% of all displays have 1 out of like 3 or 4 display resolutions

2. Fonts - they only spoof the name of fonts, but if a website check for that font name who is not exist in the system, simply load that font and make the measures “GLYPHS” who read the hight and widh and weight if the font, and will not match on statistics. If a font dont exist by his name then the system will load the next default font available in the system wich mean also that all fonts used in spoof will generate same font parameters identical.

Again, same as the resolution fonts are pretty standard, if you use default fonts of your OS there isn't much fingerprinting.


3. They dont change non uniq canvas, and canvas noise generate a uniq canvas who do not statisticslly exist in any real device . This will result 100% in a reject

I don't know how canvas actually is creating, but blocking is an option and prevents specific fingerprinting -> instead of exact it is blocked.


4. timezone dont solve the timestamp fongeprints “ time discrepancy” wich is the diffrence time between your device and the website server time, you have to always sincronize time and date to be most accurate. Otherwise this coult be a uniq fingeprint who target your device.

It is fakeable without notice as it is OS dependent (ie. you can choose it in the OS which timezone it is) and MultLogin is probably able to hook in between and fakes the OS notification to the browser.

5. webrtc udp IP, simple try to comunicate with fake ip spoofed in webrtc will result in no responde, wich mean is fake!

It is actually possible as the "faked IP" answers on WebRTC. Other way would be to block so it does not matter.
 
Is limited by browser window as well. Tor Browser is a good example of that, it changes the browser size. Display resolution is very standard, 100% of all displays have 1 out of like 3 or 4 display resolutions



Again, same as the resolution fonts are pretty standard, if you use default fonts of your OS there isn't much fingerprinting.




I don't know how canvas actually is creating, but blocking is an option and prevents specific fingerprinting -> instead of exact it is blocked.




It is fakeable without notice as it is OS dependent (ie. you can choose it in the OS which timezone it is) and MultLogin is probably able to hook in between and fakes the OS notification to the browser.



It is actually possible as the "faked IP" answers on WebRTC. Other way would be to block so it does not matter.
All your ways will result in a rejection. You cant simple block fingerprints. They expect to see all this fingeprints as in any normal environment. You cant just block webrtc or webgl or canvas or whatever, all modern browsers have this features enabled by default.
I dont try to convince you nothing, but if you dont accept logic argument, then I think you dont care about the true.
If you dont know what is viewport on resolution then check browserleaks to better understand the parameters and why they are unusual.

I just made a short description of what multilogin do wrong.
Also about fonts, use default fonts? Then why spoof anymore? If the safe method is to ise default fonts, and no, default fonts is not good for statistics in fingeprints, because they will expect some other fonts, or they may not take the risk to accept your device.
By fonts they can deduct your windows version (home pro,etc) even the subversion due to well know fonts that come with this windows versions.
Each diffrent sub version of windows will have a diffrent set of fonts wich is well lnow by statistics, and also they expect some new other fonts as a pruve that the windows is not fresh installed.

each time you as a user, if you install a software then that software may install you a uniq font as part of his product. For example NOKIA font wich not exist by default in windows. They want this custom fonts to target you better and if they dont find any custom font then…. Could reject you :)

some website do this, others dont.
Is not recomandated to have only the default fonts, and not to spoof them, best way is to manage delete and install real set of diffrent fonts, wich is a hard and complicate way to do it. Most of antidetect choose the spoof because is verry simple and fast!!! Against quality
 
What kind of rejection? I have never received any rejection with blocked WebRTC/Canvas and default system fonts with 4g or datacenter proxies.
 
What kind of rejection? I have never received any rejection with blocked WebRTC/Canvas and default system fonts with 4g or datacenter proxies.
This is viewport
 

Attachments

  • 4F96CA2A-9779-47A2-9537-2AF471255DCC.jpeg
    4F96CA2A-9779-47A2-9537-2AF471255DCC.jpeg
    633.3 KB · Views: 77
This is viewport

What does it have to do with rejection on a site?

Also, viewport = browser window size, I have explained it already. No way to fingerprint it correctly, it's a changing value. Check Tor browser, they create the browser window inside their browser.
 
What kind of rejection? I have never received any rejection with blocked WebRTC/Canvas and default system fonts with 4g or datacenter proxies.
It really depends on what you do. For highly sensitive stuff any bit of detail can make a difference.

About the implied "rejection" I guess it meant the website will take an internal decision about your session, and you might not even know what that is and how they will going to act on it. It can also be in an instant, or with a high delay of hours or days.
 
Back
Top