internetsway
Newbie
- Sep 6, 2015
- 17
- 7
Well hello BHW, just noticed I had this account from 2015, which I haven't used since then.
A lot of things have changed and I am now a software developer, specialized in Cyber Security.
Currently, I am working on a Cloaker, which I might sell on here. Of course it should be an outstanding and great product.
That is why I wanted to ask you guys: Are there any 'special features' you always wanted to see in a Cloaker? Any must haves?
I am not new to cloaking, but so far I only used my private cloakers for my private projects.
Big databases with IPs of datacenter, VPNs, public proxies, blacklisted IPs, IPs owned by companies, User-Agents of bots and much more are 'in my posession'.
So far my idea would be to provide a cloaking API that will receive all of the required information about the client trying to access the cloaked page (screen resolution, IP, User-Agent, JavaScript check) and then decide, based on the data I have saved, whether it should be redirected to a 'safe page' (i.e. google.com) or to the cloaked page. Would provide my clients with PHP, JavaScript, Python and so on that they could integrate into their webapp in order to make use of my cloaker.
Any Input would be much appreciated and I hope that I will be able to release, sell and satisfy people on here with my cloaker!
A lot of things have changed and I am now a software developer, specialized in Cyber Security.
Currently, I am working on a Cloaker, which I might sell on here. Of course it should be an outstanding and great product.
That is why I wanted to ask you guys: Are there any 'special features' you always wanted to see in a Cloaker? Any must haves?
I am not new to cloaking, but so far I only used my private cloakers for my private projects.
Big databases with IPs of datacenter, VPNs, public proxies, blacklisted IPs, IPs owned by companies, User-Agents of bots and much more are 'in my posession'.
So far my idea would be to provide a cloaking API that will receive all of the required information about the client trying to access the cloaked page (screen resolution, IP, User-Agent, JavaScript check) and then decide, based on the data I have saved, whether it should be redirected to a 'safe page' (i.e. google.com) or to the cloaked page. Would provide my clients with PHP, JavaScript, Python and so on that they could integrate into their webapp in order to make use of my cloaker.
Any Input would be much appreciated and I hope that I will be able to release, sell and satisfy people on here with my cloaker!