@ozsuakin Sorry, but I don't have experience with either of these tools. You can try Mobilehop proxies. They have TCP fingerprint spoofing (so TCP, not TLS, but it might work in your use case).
Update Fingerprint Browser Version
Moved
Feature request
-
A feature to update an already obtained fingerprint to the latest bas browser version would be an amazing feature! It would allow profile fingerprints to stay the same over a long period of time, while updating the browser version to make it look like a regular user, instead of having to keep the same profile and fingerprint on a version that gradually gets older, or keep the profile and change the fingerprint, which in the case of many sites, makes it so a new warmup period of time needs to happen. I would help pay money for this feature to be added as it would make many things 1 million times easier!
-
M Moderator moved this topic from Запросы функционала
-
This has come up in the older forum discussions. Users mostly discuss the logic, approach and design without sharing their actual scripts. Have you checked what they’ve tried and what problems they’ve run into?
I get what you’re asking for: keep the same profile and device identity while moving to the latest BAS browser version. That would be useful. But changing the version in the User-Agent and related fields may only cover part of it.
A newer browser can introduce new features or change how existing ones behave. The fingerprint/emulation layer may need changes too, otherwise you could end up with a fingerprint that claims one version but behaves differently.
Keeping all of that consistent across updates could be quite a headache. Maybe that’s one reason there’s no built-in feature for this, though that’s just my guess.
Personally, I don’t expect the BAS developers to implement this feature themselves. I think users who need it have little choice but to build and maintain their own solutions and scripts, adapting them as browser versions change.