Month: September 2017

How to Block and Stop Bad Bots and spiders from stealing you?  You can manage the blacklist.

An Internet Bot, also known as web robot, WWW robot or simply bot, spider is a software application that runs automated tasks (scripts) over the Internet.  Bad bots consume bandwidth, slow down your server, steal your content and look for vulnerability to compromise your server. Be proactive and Block Bad Bots right away from accessing your server.

• The Stop Bad Bots Free WordPress Plugin is the easiest way to stop Bad Bots and Spiders.
• More than 2500 Bad Bots Included!
• Your Bad Bots Table is always updated with free online automatic updates
• No robots.txt neither .htaccess file requiered
• You Can Add more Bad Bots…
• No DNS Traffic Redirection. No Downtime!
• Easy to manage the list of bad bots
• Easy to set up
• Lightweight
• Save bandwidth.
• Optionally receive an email alert
• Updated On Line Guide
• Start Up Guide
• FAQ Page
• Demo Video
• Free Support Ticket System
• Rated 5 Stars at WordPress
• The Plugin doesn’t block main Google, Yahoo and Bing (Microsoft).

Very light, easy and quick to install (just 2 minutes) and manage.

Visit the official website here

DNS PORT (53) Flood Detected! Anyone else?>

Here is a list of CIDR,,… to block! 😉

62.210.0.0/16
195.154.0.0/16
212.129.0.0/18
62.4.0.0/19
212.83.128.0/19
212.83.160.0/19
212.47.224.0/19
163.172.0.0/16
51.15.0.0/16
151.115.0.0/16
# 2001:bc8::/32 * Experimental on CSF *

Cheers!

NOTE:

An internet server company Poney Telecom run from France has been at the centre of multiple allegations of organised international criminal activity for over 12 months with all warnings, court summons and legal demands to be closed ignored.

The French service provider facilitates large quantities of spam to a variety of European companies from computers which can be traced back to Russia. These malicious emails should not be opened or responded to as it is common practice to embed viruses within such emails.

Contacting Poney Telecom is far from easy, however when The International‘s legal team finally did make contact they were informed by a member of staff from Poney Telecom that any criminal activity that occurs by using it’s services are “not my problem“. The staff member claiming to be able to speak on behalf of the company went on to state that they had a policy of non-compliance with authorities in or outside of the EU.

As such we advice anyone who receives emails or contact from anybody using a Poney Telecom server IPA to keep a detailed record of all contact that is made via the company. Should sufficient suspicious activity arise contact your local non-emergency police.

Note:

AS4134 – ChinaNet
AS9808 – Guangdong Mobile Com
AS16276 – OVH SAS
AS15003 – Nobis Tech Group
AS36352 – ColoCrossing
AS29761 – QuadraNet
AS15895 – Kyivstar PJSC
AS50915 – S.C. Everhost S.R.L.
AS53889 – Micfo
AS57858 – Fiber Grid OU

http://www.ip2location.com/blockvisitorsbycountry.aspx

If someone is having the same problem,
I solved it by enabling LF_IPSET in csf.conf

😉

# systemctl restart csf

If you want to redirect HTTP to HTTPS and want to add www with each URL, use the htaccess below:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R,L]
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L] 

It will first redirect HTTP to HTTPS and then it will redirect to https://www

😉

My friend ran into a problem with my CENTOS Server. The problem was related to a error in Opencart.

“Error 413 Request Entity is Too Large…”

You need to edit mod_security.conf to fix this issue

/etc/httpd/conf.d/mod_security.conf

Locate this part near the top of the configuration

# Default recommended configuration
SecRuleEngine On “You may turn this Off, until you fix thing, but put it back On“
SecRequestBodyAccess On
SecRule REQUEST_HEADERS:Content-Type “text/xml” \
“id:’200000′,phase:1,t:none,t:lowercase,pass,nolog,ctl:requestBodyProcessor=XML”
SecRequestBodyLimit 531072
SecRequestBodyNoFilesLimit 531072
SecRequestBodyInMemoryLimit 531072
SecRequestBodyLimitAction Reject

Now change the value of those two configuration

SecRequestBodyLimit 2147483647   (2GB unlimited value)
SecRequestBodyNoFilesLimit 5242880  (This will fix the 413 error)
SecRequestBodyInMemoryLimit 531072
SecRequestBodyLimitAction Reject

Restart Apache

systemctl restart httpd

ENJOY!

Cheers Dejan from SERBIA! TEAMWORK!!!