rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 04:03:37 AM |
|
I just tested this service and I didn't like it. This is listing my IP as a bot ip. ¬¬ You are on the black list I suppose, my website working for you? Yes. It is working. But my IP shouldn't be blacklisted. This is a home use IP that changes dinamically. It hasn't any port open and I haven't any service hosted here... Is this service working well for you?
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 04:14:04 AM |
|
I just tested this service and I didn't like it. This is listing my IP as a bot ip. ¬¬ You are on the black list I suppose, my website working for you? Yes. It is working. But my IP shouldn't be blacklisted. This is a home use IP that changes dinamically. It hasn't any port open and I haven't any service hosted here... Is this service working well for you? I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
Now the script that includes block Tor
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 12:00:45 PM |
|
I just tested this service and I didn't like it. This is listing my IP as a bot ip. ¬¬ You are on the black list I suppose, my website working for you? Yes. It is working. But my IP shouldn't be blacklisted. This is a home use IP that changes dinamically. It hasn't any port open and I haven't any service hosted here... Is this service working well for you? I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
Now the script that includes block Tor Just notice that the following code will generates some false positives: @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )) This code is verifying if the ports 80 and 8080 are open. A lot of legit users have their ports 80 and 8080 open for any motive. But if you don't worry about this, just forget this issue... Search on Google for the most used ports for proxy servers and reply this code for them. This way you will block more proxies.
|
|
|
|
minifrij
Legendary
Offline
Activity: 2352
Merit: 1267
In Memory of Zepher
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 12:59:37 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies.
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 06:21:01 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward?
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 07:29:10 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward? This code will validate the visit every page load. If you put this in your index.php, the visitor will be checked twice. One time when entering your page. One second time when the claim confirmation page is loaded.
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 07:39:20 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward? This code will validate the visit every page load. If you put this in your index.php, the visitor will be checked twice. One time when entering your page. One second time when the claim confirmation page is loaded. And so I avoid?
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 07:49:19 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward? This code will validate the visit every page load. If you put this in your index.php, the visitor will be checked twice. One time when entering your page. One second time when the claim confirmation page is loaded. And so I avoid? Well... You have two option: 1st. check just at the claim action: The visitor will be checked once and just if he claims in the faucet. This the best option from the performance point of view and good for your earnings because even proxy user can click or see your CPM ads. But only those whice try to get a reward will be checked and blocked. Otherwise, If you permit a bot to access your site this bot can click your ads crazily causing your ads account banning by abuse. 2nd. Check all incoming visitors. You will have more false positives in this implementation. And you will check every claimer twice. But you will be more protected agains auto-click bots also.
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 07:53:06 PM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward? This code will validate the visit every page load. If you put this in your index.php, the visitor will be checked twice. One time when entering your page. One second time when the claim confirmation page is loaded. And so I avoid? Well... You have two option: 1st. check just at the claim action: The visitor will be checked once and just if he claims in the faucet. This the best option from the performance point of view and good for your earnings because even proxy user can click or see your CPM ads. But only those whice try to get a reward will be checked and blocked. Otherwise, If you permit a bot to access your site this bot can click your ads crazily causing your ads account banning by abuse. 2nd. Check all incoming visitors. You will have more false positives in this implementation. And you will check every claimer twice. But you will be more protected agains auto-click bots also. And in php as I do, I have no idea.
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 07:53:56 PM |
|
A new probabily scam address added to the topic: 14dSb5iAsKdeeY24cSS3MbGWVVHSVsZTC8 New malicious IP address added also: 66.249.91.16 66.249.69.11 103.10.197.212 188.163.87.0 109.110.66.224 5.14.211.20 46.72.4.248 194.213.120.1 5.248.19.93 95.30.48.201 193.107.85.47 76.164.227.240 78.107.221.158 2.95.124.182 176.193.102.5 95.215.62.89 162.245.145.120 195.110.32.55 84.19.165.213 46.118.23.135 46.167.114.51 158.255.215.59 52.26.170.43 176.222.147.152 88.200.136.116 151.236.21.174 114.79.28.82 178.137.124.236 223.255.230.57 95.25.182.122 52.32.249.184 37.27.16.188 5.45.255.86 95.85.56.226 217.118.81.22 91.121.153.214 141.0.12.137 46.32.85.140 202.44.228.168
|
|
|
|
pickupcoin
Legendary
Offline
Activity: 1203
Merit: 1000
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 09:06:56 PM |
|
Does anyone have properly setup cloudflare on faucet site? thanks
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 09:45:49 PM |
|
A new probabily scam address added to the topic: 14dSb5iAsKdeeY24cSS3MbGWVVHSVsZTC8 New malicious IP address added also: 66.249.91.16 66.249.69.11 103.10.197.212 188.163.87.0 109.110.66.224 5.14.211.20 46.72.4.248 194.213.120.1 5.248.19.93 95.30.48.201 193.107.85.47 76.164.227.240 78.107.221.158 2.95.124.182 176.193.102.5 95.215.62.89 162.245.145.120 195.110.32.55 84.19.165.213 46.118.23.135 46.167.114.51 158.255.215.59 52.26.170.43 176.222.147.152 88.200.136.116 151.236.21.174 114.79.28.82 178.137.124.236 223.255.230.57 95.25.182.122 52.32.249.184 37.27.16.188 5.45.255.86 95.85.56.226 217.118.81.22 91.121.153.214 141.0.12.137 46.32.85.140 202.44.228.168 Google bot 66.249.
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 03, 2015, 11:21:26 PM |
|
A new probabily scam address added to the topic: 14dSb5iAsKdeeY24cSS3MbGWVVHSVsZTC8 New malicious IP address added also: 66.249.91.16 66.249.69.11 103.10.197.212 188.163.87.0 109.110.66.224 5.14.211.20 46.72.4.248 194.213.120.1 5.248.19.93 95.30.48.201 193.107.85.47 76.164.227.240 78.107.221.158 2.95.124.182 176.193.102.5 95.215.62.89 162.245.145.120 195.110.32.55 84.19.165.213 46.118.23.135 46.167.114.51 158.255.215.59 52.26.170.43 176.222.147.152 88.200.136.116 151.236.21.174 114.79.28.82 178.137.124.236 223.255.230.57 95.25.182.122 52.32.249.184 37.27.16.188 5.45.255.86 95.85.56.226 217.118.81.22 91.121.153.214 141.0.12.137 46.32.85.140 202.44.228.168 Google bot 66.249. Thank you. I will check this!
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 04, 2015, 12:31:50 AM |
|
I'm just using it, for now it goes well block some proxies but not all. I'm doing tests now and I see that the following code blocks more proxies <?php if ($_SERVER['HTTP_X_FORWARDED_FOR'] || $_SERVER['HTTP_X_FORWARDED'] || $_SERVER['HTTP_FORWARDED_FOR'] || $_SERVER['HTTP_CLIENT_IP'] || $_SERVER['HTTP_VIA'] || @fsockopen( $_SERVER['REMOTE_ADDR'], 80, $errstr, $errno, 1 ) || @fsockopen( $_SERVER['REMOTE_ADDR'], 8080, $errstr, $errno, 1 )){ echo 'Blocked Proxy'; exit; } ?>
The problem with these checks is that almost all off them are HTTP headers and can be modified using certain functions of a browser/PHP. You should keep these checks in your code, but you shouldn't rely on them to block all proxies. They have reason, how can I prevent the use of this code after the first visit? Or is that only read the ip when you enter, but not when you receive the reward? This code will validate the visit every page load. If you put this in your index.php, the visitor will be checked twice. One time when entering your page. One second time when the claim confirmation page is loaded. And so I avoid? Well... You have two option: 1st. check just at the claim action: The visitor will be checked once and just if he claims in the faucet. This the best option from the performance point of view and good for your earnings because even proxy user can click or see your CPM ads. But only those whice try to get a reward will be checked and blocked. Otherwise, If you permit a bot to access your site this bot can click your ads crazily causing your ads account banning by abuse. 2nd. Check all incoming visitors. You will have more false positives in this implementation. And you will check every claimer twice. But you will be more protected agains auto-click bots also. How do you do it?
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 04, 2015, 02:29:37 AM |
|
It depends on that option you want to implement.
I would advice you to implement the 2nd.
This isn't the best performance choice but is the most secure.
I use my security this way in my site.
Choose of them and I will help you.
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 04, 2015, 03:01:13 AM Last edit: November 04, 2015, 04:45:22 AM by misterbit |
|
It depends on that option you want to implement.
I would advice you to implement the 2nd.
This isn't the best performance choice but is the most secure.
I use my security this way in my site.
Choose of them and I will help you.
The first ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) He would serve with an include? I already got it! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 04, 2015, 03:24:11 PM |
|
It depends on that option you want to implement.
I would advice you to implement the 2nd.
This isn't the best performance choice but is the most secure.
I use my security this way in my site.
Choose of them and I will help you.
The first ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) He would serve with an include? I already got it! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Nice! Let me know if you need some help!
|
|
|
|
misterbit
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 04, 2015, 04:55:23 PM |
|
It depends on that option you want to implement.
I would advice you to implement the 2nd.
This isn't the best performance choice but is the most secure.
I use my security this way in my site.
Choose of them and I will help you.
The first ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) He would serve with an include? I already got it! ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Nice! Let me know if you need some help! What method would you use for the first option?
|
|
|
|
grosminer
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 05, 2015, 02:04:56 AM |
|
A new suspicious ip appeared in my logs since november:
77.222.106.36 9000 hits in 4 days only..
And the faucet got milked.. i'm not sure yet but this ip looks really suspicious
|
|
|
|
rkandrades (OP)
Sr. Member
![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif) ![*](https://bitcointalk.org/Themes/custom1/images/star.gif)
Offline
Activity: 392
Merit: 251
Bitcoin Faucet & Blog
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
November 05, 2015, 05:27:18 PM |
|
A new suspicious ip appeared in my logs since november:
77.222.106.36 9000 hits in 4 days only..
And the faucet got milked.. i'm not sure yet but this ip looks really suspicious
~ Hi, friend. I checked this IP for suspicious activities in the internet (SPAM, BOTs and Malicious attacks) and then I did some tests to check if it is a proxy IP. I didn't found anything about this IP. It seems to be a normal IP. However, it is a Russian IP. If I was you I would keep on open eye on my logs to monitor this IP actions...
|
|
|
|
|