Good Cloaking Tools with PHP and Javascripts

analytic

Junior Member
Joined
May 1, 2023
Messages
110
Reaction score
39
Good Cloaking Tools with PHP and Javascripts


Hi guys. Do you use PHP and Javascript for cloaking?

For example, there are bases (ip2location and maxmind) - for working with IP information. That allows us to do what.




There is a landing site (many sites), there is a code (PHP + Javascript) that collects data about the user and passes it to the base site. Here you need to understand the code at an elementary level (this will be discussed in the instructions)




Further on the received parameters - we can do a lot of things .. In particular, create a condition (based on the received parameters) on the basis of which
1) Display the desired text block/banner
2) Redirect

Further, snippets are included in the system codes
1) Accounting for clicks on redirects
2) Accounting for block/banner impressions

Those. based on (the parameters below) - we can build our own landing pages with dynamic content and redirects. Yes, at least you need to understand the layout. :)

But it's worth it - given the flexibility of embedding these conditions into any site (both in php and html)

It makes sense to compare this system with Keitaro or other tds|analytical systems only in those functions = for which the code system was developed, namely:
1. Traffic accounting for a large number of parameters (which most do not have). Analysis of campaigns with the highest bot traffic.
2. Flexible traffic distribution system. Implementation at the code level.

Now about the parameters

1. IP parameter (PHP) - IP via PHP code
2. IP parameter (JS) - IP via JS code

3. IPW1 parameter - local IP leak via WebRTC
No local IP or local IP is different for the same IP users = BOT TRAFFIC

4. IPW2 parameters - IPv6 leak via WebRTC - there is IPv6 BOT TRAFFIC

5. IPW3 settings - IPv4 leak via WebRTC. IPv4 is not equal to IP BOT TRAFFIC

6. Parameter Country (IP) - User country
7. Parameter Country code (IP) - Code table will be. Sometimes it's easier.
8. Parameter City (IP) - City
9. Parameter Region (IP) - Region
10. Parameter ISP (IP) - Internet provider. Often used in bot distribution. snippet example
PHP:
PHP:
<?php

if ($check["isp"]=="Yandex LLC")

{

echo "output the page to be indexed by Yandex";

}

elseif ($check["isp"]=="Google LLC")

{





echo "output the page to be indexed by Google";

}





elseif ($check["isp"]=="Yahoo! Inc.")

{





echo "displaying the page to be indexed by Yahoo";

}

else





{

echo "display page for normal user";

}





?>





11. Parameter latitude and longitude (IP). If you want to distribute traffic by ranges.

12. Connection type parameter (IP). If the user's connection type does not match -BOT TRAFFIC


13. Parameter time zone (IP).

14. IP DNS parameter. To obtain this parameter, configuration at the BIND level is required. This will be in the output.

15. Parameter Country (IP DNS)
16. Parameter Country Code (IP DNS)
17. Parameter City (IP DNS)
18. Parameter Region (IP DNS)
19. ISP setting (IP DNS)
20. Connection type parameter (IP DNS)
21. Time zone setting (IP DNS)

22. Parameter USERAGENT (PHP) - here it is clear the user agent received by PHP code

23. User agent type parameter (PHP)

Defined user agent types
1. Browser
2. Bot
3. Feed reader
4. Libraries
5. Mobile application
6. Personal information manager - PIM
7. Media players

24. Parameter user agent name (PHP) - there will be a table with the names of common bots and browsers

25. User agent version parameter (PHP)

26. Parameter user agent engine (PHP)

27. Parameter operating system name (PHP) - there will be a table with OS

28. Operating system version parameter (PHP)

29. Operating system bit depth parameter (PHP)

30. Device Parameter (PHP)
List of defined devices
1 Computer
2 Smartphone
3 tablet
4 Mobile phone
5 Console
6 TV
7 Car Browser
8 Smart display
9 Camera
10 Portable media player
11 Phablet
 
31. Device model parameter (PHP) - the ability to distribute traffic by device model (phone or tablet)


32. Device brand parameter (PHP) - the ability to distribute traffic by device brand.

33. Parameters for USERAGENT (JS) - User agent received by javascript code. If
USERAGENT (JS) is not equal to USERAGENT (PHP) BOT TRAFFIC
34. User agent type parameter (JS)
35. User agent name parameter (JS)
36. User agent version parameter (JS)
37. User agent engine parameter (JS)
38. Operating system name parameter (JS)
39. Operating system version (JS) parameter
40. Operating system bit depth parameter (JS)
41. Device Parameter (JS)
42. Device model parameter (JS)
43. Device brand parameter (JS)

44. Parameter REFERRAL Accounting for the address of the site (full) from which the traffic came. Accounting for direct visits and through sites
45. GET parameter (Track campaigns and other parameters)
Tracking standard campaign tags and any GET passed parameters

46. Screen extension options - Screen extension generated and does not match the device - BOT TRAFFIC

47. System time settings

48. Parameter number of plugins - No plugins. BOT TRAFFIC

49. Parameter list of plugins - Plugins are generated for one IP - BOT TRAFFIC
50. FLASH version parameter - Flash is missing - most likely BOT TRAFFIC


50. FLASH version parameter - Flash is missing - most likely BOT TRAFFIC
51. Parameter number of visits - many visits from one IP and from different devices in a certain period of time - BOT TRAFFIC
52. Browser language parameter - used in add. checks
53. Parameter Cookies - Cookies are disabled - BOT TRAFFIC
54. Parameter Fingerprint2 - Generated Fingerprint2 - BOT TRAFFIC

55. Parameter time zone (JS) Time zone does not match - locally and systemically BOT TRAFFIC

56. Check parameter CHECK1 = 0 . if the IP country and DNS IP country (elite proxy or VPN) do not match. BOT TRAFFIC
57. Check parameter CHECK2 = 0. if IP city and DNS IP city (elite proxy or VPN) do not match. BOT TRAFFIC
58. Check parameter CHECK3= 0. if ISP IP and ISP IP DNS (elite proxy or VPN) do not match. BOT TRAFFIC
59. Check parameter CHECK4= 0. if the local and system time zones do not match. BOT TRAFFIC
60. Check parameter CHECK5 = 0, PHP and JS user agents are not equal - BOT TRAFFIC
61. Check parameter CHECK6 = 0 if the language in the browser does not match the country of the user BOT TRAFFIC
62. Check parameter CHECK7=0 . Public proxy detected. BOT TRAFFIC
 
Bot traffic is not determined by a metric - as Google Analytics and other analytical systems - use javascript. Bot traffic - in 80% does not work with javascript - therefore, its systems on PHP and javascript - it is more competent to organize cloaking.
 
Last edited:
Device Parameter (PHP)
List of defined devices
1 Computer
2 Smartphone
3 tablet
4 Mobile phone
5 Console
6 TV
7 Car Browser
8 Smart display
9 Camera
10 Portable media player
11 Phablet
https://github.com/matomo-org/device-detector
PHP:
$dd->isSmartphone();
$dd->isFeaturePhone();
$dd->isTablet();
$dd->isPhablet();
$dd->isConsole();
$dd->isPortableMediaPlayer();
$dd->isCarBrowser();
$dd->isTV();
$dd->isSmartDisplay();
$dd->isSmartSpeaker();
$dd->isCamera();
$dd->isWearable();
$dd->isPeripheral();


Methods check client type:

PHP:
$dd->isBrowser();
$dd->isFeedReader();
$dd->isMobileApp();
$dd->isPIM();
$dd->isLibrary();
$dd->isMediaPlayer();
 
Last edited:
Working with the API is one of the most difficult tasks, but at the same time, it allows you to receive
diverse and combined data, depending on the analytical tasks.


More examples
 

Attachments

Last edited:
Back
Top