Anti‑Detect Browsers Overview of Features and testing experience

MikeJames225 said:

what you mean when yo usay that the scrolling part does not work on Dolphin if you are using it from a laptop? you saying that you can't literally scroll down or up in teh advance settings section?

Click to expand...

Lol, yeah, preciselly that.

I can do using the tab button, but yeah, would you buy a used car from someone who releases an app like that?

MikeJames225 said:

i mean is literally a minor thing when you put it in perspective don't you think?

i use dolphin mostly on pc with a mouse so i don't really have this issue when i work with it, and dolphin also offers some other cool features like the smart paste, that emulates the writing pattern of person when you copy and paste login credentials. I don't know if any of the other option for the anti detect browser offfers something similiar but overall i would say that i'm pretty comfortable by working with dolphin anty

Click to expand...

Yes it's minor, but there's of course more major issues, like testing what kind of values are generated overall and especially the canvas noising, which is the litmus test, if you check, you'll find that canvas drift and noising is the most challenging task for an anti detect provider , this one part is perhaps just as important as proxies, if not more.

MikeJames225 said:

oh well, i didn't know about that. Personally i'm not so technically savy since i don't have too much experience in developing and those types of areas, but i really appreciate the knowledge that you are droppig here for all of us the regular users. I use dolphin mainly to work with profiles on adult sites ( PH XV, XH, etc ) and until know i haven't had any issue with the accounts as long as i keep my security measures on check of course. I think that i never tried to touch the canvas noise part, i mostly tend to only work with the firgerprint, the MAC address and device name in combination with the proxy.

Click to expand...

Thanks for the compliments, don't worry about mac address, nobody can ever see that, least not a website.

It's always a back and forth, the websites find new ways, then the anti detects try to catch up etc.

It's best to never expect some sort of setup to work forever, but to understand how things work and be ready to adapt on short notice.

People always say this and that don't work anymore, but if you think about it, it's like saying anti detect measures from 15 years ago do not work anymore.

The gmail auto creators have suffered that, they are directly responsible for Google clamp down, they didn't send their gmails with the languages set internal to the account, some ip info and the used "username123x" naming convention, something that I'd fire them on the spot for. And their backup emails were usually one time throwaway emails, and they tried that on Google, of all opponents. Initially this was small but then an ecosystem of clueless resellers grew and Google had enough of it.

This is why I try to bring some lights into this Sphere, nothings worse to me when random people say use this and that anti detect or proxy(this field is even worse, anti detects do a good job compared to proxies, there was a time when residential proxies were real good, but thenproviders have degraded the products now badly).

And actually, it's interesting to take some couple hours and test the various anti detect providers, proxies are harder to check properly.

Scaling phones and suddenly hitting captchas is almost always signal correlation, not a per-device thing. If the phones share anything — same subnet/gateway, similar device fingerprints, synchronized behavior, sequential account ages — the anti-bot clusters them and challenges the whole group. Each phone needs to look independent: separate egress IP (mobile/residential, not one shared NAT), varied fingerprints, desynchronized timing. The captcha is the symptom; the farm looking like a farm is the cause.