@hungdaingoc what exactly wrong? check results show that canvas is working, if you talking about that canvas hash haven't changed its because your perfect canvas request referring to your target site,not browserleaks
if you collect perfect canvas for browserleaks you'll see that it will be different
I have a problem
Moved
Support
-
Hello, I want to get into the topic immediately without further ado. I'm making an automation and using BAS's fingerprint. It gives very bad results on sites such as Browserscan and Pixelscan. He gets caught every time. Is there something I don't know or am doing wrong?
Do I need to make a special setting? I think BAS is a little inadequate when it comes to fingerprinting. Or I couldn't do it
-
M Moderator moved this topic from Support on
-
-
@m4zuper I read and applied what you wrote, but nothing changed. When I logged in with the Canvas inspector, browserscan detected that WebRTC was leaking the IP address. But other results were positive. When I use it with BAS, it is captured directly in many elements.
