mirror of
https://github.com/mitchellkrogza/nginx-ultimate-bad-bot-blocker.git
synced 2025-09-15 01:29:49 +00:00
Introduce New Tests to Test New / Potentially Breaking Changes to the Blocker
This commit is contained in:
Mitchell Krog
parent
f22ce483bc
commit
7a1011aea5
30 changed files with 22845 additions and 0 deletions
1
.dev-tools/_conf_files_testing_changes/bots.d/.keep
Normal file
1
.dev-tools/_conf_files_testing_changes/bots.d/.keep
Normal file
|
|
@ -0,0 +1 @@
|
|||
null
|
||||
|
|
@ -0,0 +1,73 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD WORDS YOU WANT TO SCAN FOR ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.06
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# This is merely an example and gets auto included as since Version 2.2017.07 introduced on 2017-04-20
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# For all intensive purpose you can delete everything inside this file and leave it
|
||||
# completely blank if you do not want your Nginx Blocker to include scanning for bad words within urls or referrer string
|
||||
# Only add one entry per line
|
||||
|
||||
# *******************************
|
||||
# !!! WARNING WARNING WARNING !!!
|
||||
# *******************************
|
||||
|
||||
# ***************************************
|
||||
# PLEASE BE VERY CAREFUL HOW YOU USE THIS
|
||||
# ***************************************
|
||||
# Here is an example of how one supposed bad word can cause your whole site to go down.
|
||||
# An issue was logged where the users own domain name was specialisteparquet.com
|
||||
# Because this list contained the word "cialis" it was detected within his domain name causing
|
||||
# his entire site to go down and not server any assets.
|
||||
# That one entry would even cause any site containing a word like "specialist" anywhere in any
|
||||
# of their sites pages to cause them to be blocked and whitelisting your own domain name in the
|
||||
# whitelist-domains.conf file will not even bypass this, SO BE CAREFUL PLEASE
|
||||
|
||||
# Think very carefully before you add any word here
|
||||
|
||||
# *****************************************************************************************
|
||||
# PLEASE MAKE SURE that you use word regex boundaries to avoid false positive detection !!!
|
||||
# *****************************************************************************************
|
||||
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
|
||||
# As you can see in the examples below the word "adultgalls" is entered with a preceding \b and an ending \b
|
||||
# this makes it now "\badultgalls\b". It is crucial to use the word boundaries regex formatting.
|
||||
|
||||
# ---------
|
||||
# EXAMPLES:
|
||||
# ---------
|
||||
# "~*\badultgalls\b" 1;
|
||||
# "~*\bamateurxpass\b" 1;
|
||||
# "~*\bbigblackbooty\b" 1;
|
||||
# "~*\bblacktits\b" 1;
|
||||
# "~*\bcookie\-law\-enforcement\b" 1;
|
||||
# "~*\bfree\-share\-buttons\b" 1;
|
||||
# "~*\bfree\-social\-buttons\b" 1;
|
||||
# "~*\bfuck\-paid\-share\-buttons\b" 1;
|
||||
# "~*\bilovevitaly\b" 1;
|
||||
# "~*\blaw\-enforcement\-bot\b" 1;
|
||||
# "~*\blaw\-enforcement\-check\b" 1;
|
||||
# "~*\bshare\-buttons\-for\-free\b" 1;
|
||||
# "~*\bwebfuck\b" 1;
|
||||
# "~*\bxxxrus\b" 1;
|
||||
# "~*\bzeroredirect\b" 1;
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,45 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO BLACKLIST YOUR OWN CUSTOM DOMAIN NAMES ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.04
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Add One Entry Per Line - List all your own extra domains you want to blacklist.
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# Automatic updates will never be able to remove this custom list of yours
|
||||
# Add One Entry Per Line
|
||||
|
||||
# Make sure any domains have dots and special characters escaped as per the Regex examples below.
|
||||
# For example myblacklisteddomainname.com should be entered as myfirstowndomainname\.com
|
||||
# and my-second-blacklisted.com should be entered as my\-second\-owndomainname\.com
|
||||
|
||||
# *****************************************************************************************
|
||||
# PLEASE MAKE SURE that you use word regex boundaries to avoid false positive detection !!!
|
||||
# *****************************************************************************************
|
||||
|
||||
# As you can see in the examples below the domain "myblacklisteddomainname\.com" is entered with a preceding \b and an ending \b
|
||||
# this makes it now "\bmyblacklisteddomainname\.com\b". It is crucial to use the word boundaries regex formatting.
|
||||
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
# ---------
|
||||
# EXAMPLES:
|
||||
# ---------
|
||||
# "~*\bmyblacklisteddomainname\.com\b" 1;
|
||||
# "~*\bmy\-second\-blacklisted\.com\b" 1;
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,91 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD IP ADDRESSES OR IP RANGES YOU WANT TO BLOCK ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.07
|
||||
### Updated: 2018-08-06
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# This is merely an example and gets auto included as since Version 2.2017.07 introduced on 2017-04-20
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# For all intensive purpose you can delete everything inside this file and leave it
|
||||
# completely blank if you do not want your Nginx Blocker to do any blocking of bad IP's
|
||||
|
||||
# Add IP's you want to blacklist below this line, one per line as per example
|
||||
# Nginx [warn] notices may be reported when you try reload Nginx if you happen to include an
|
||||
# IP here that may already be included by the blocker with it's daily updates
|
||||
# NOTE: It is only an Nginx Warning message and will not cause Nginx to fail a reload.
|
||||
|
||||
# 111.111.111.111 1;
|
||||
|
||||
# Cyveillance / Qwest Communications / PSINET
|
||||
# *******************************************
|
||||
# I am extensively researching this subject - appears to be US government involved
|
||||
# and also appears to be used by all sorts of law enforcement agencies. For one they
|
||||
# do not obey robots.txt and continually disguise their User-Agent strings. Time will
|
||||
# tell if this is all correct or not.
|
||||
# For now see - https://en.wikipedia.org/wiki/Cyveillance
|
||||
|
||||
# IMPORTANT UPDATE ON Cyveillance / Qwest Communications !!!
|
||||
# **********************************************************
|
||||
# I have done a lot of research on Cyveillance now and through monitoring my logs I know
|
||||
# for sure what companies are using them and what they are actually looking for.
|
||||
# My research has led me to understand that Cyveillance services are used by hundreds
|
||||
# of companies to help them dicsover theft of copyrighted materials like images, movies
|
||||
# music and other materials. I personally believe a lot of block lists who originally recommended
|
||||
# blocking Cyveillance have done so to protect their torrent or p2p sites from being scanned.
|
||||
# I personally have now unblocked them as image theft is a big problem of mine but if you
|
||||
# do want to block Cyveillance you can simply modify the entries in the block below from "0" to "1"
|
||||
# Getty Images is one such company who appears to use Cyveillance to help monitor for copyright theft.
|
||||
|
||||
# If you really do want to block them change all the 0's below to 1.
|
||||
# Use this section at YOUR OWN RISK, you may block some legitimate networks but after many hours of
|
||||
# Research this is now the completely updated list of all IP ranges IPV4 and IPV6 owned Qwest Communications
|
||||
# PSINET and Cyveillance
|
||||
|
||||
# IMPORTANT NOTE: If you really want to keeps bot and things out of certain parts of your web site
|
||||
# Rather implement a comlex Google Re-Captcha to reach sections of your sites and for people to be able
|
||||
# to access download links. Google Re-Captcha with images is too complex for any bot.
|
||||
|
||||
38.0.0.0/8 0;
|
||||
206.2.138.0/23 0;
|
||||
208.71.164.0/22 0;
|
||||
4.17.135.32/27 0;
|
||||
63.144.0.0/13 0;
|
||||
65.112.0.0/12 0;
|
||||
65.192.0.0/11 0;
|
||||
65.213.208.128/27 0;
|
||||
65.222.176.96/27 0;
|
||||
65.222.185.72/29 0;
|
||||
|
||||
# ****************
|
||||
# Berkely Scanner
|
||||
# ****************
|
||||
|
||||
# The Berkeley University has a scanner testing all over the web sending a complex
|
||||
# payload an expecting a reply from servers who are infected or who just respond to such
|
||||
# a payload. The payload looks similar to this
|
||||
# "$\xC9\xE1\xDC\x9B+\x8F\x1C\xE71\x99\xA8\xDB6\x1E#\xBB\x19#Hx\xA7\xFD\x0F9-"
|
||||
# and is sometime VERY long. You may have noticed this in your logs.
|
||||
# I support research projects and all my servers respond with an error to this type of
|
||||
# string so I do not block them but if you want to block just uncomment the following line
|
||||
# or email them asking them not to scan your server. They do respond.
|
||||
# Visit http://169.229.3.91/ for more info
|
||||
|
||||
# If you really do want to block them change all the 0 below to 1.
|
||||
|
||||
169.229.3.91 0;
|
||||
|
|
@ -0,0 +1,62 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO BLACKLIST OR WHITELIST ANY BAD USER-AGENT STRINGS YOU WANT TO SCAN FOR
|
||||
# ****************************************************************************************************
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.05
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Add One Entry Per Line - List all the extra bad User-Agents you want to permanently block or whitelist.
|
||||
|
||||
# This is for User-Agents that are not included in the main list of the bot blocker
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# This allows you finer control of keeping certain bots blocked and automatic updates will
|
||||
# Never be able to remove this custom list of yours
|
||||
|
||||
# Please note this include file loads first before any of the already whitelisted User-Agents
|
||||
# in the bad bot blocker. By loading first in line it over-rides anything below it so for instance
|
||||
# if you want to block Baidu, Google or Bing for any reason you add them to this file which loads
|
||||
# first and takes precedence over anything below it. This now allows even finer control over the
|
||||
# bad bot blocker. Enjoy !!!
|
||||
|
||||
# Even though this file is called blacklist-user-agents, as mentioned it can also be used to whitelist user agents
|
||||
# By adding them below and setting the 3; to 0; this will permanently whitelist the User-Agent.
|
||||
|
||||
# Make sure any words that contain special characters are escaped and include word boundaries as per the Regex examples below.
|
||||
|
||||
# Example the User-Agent name "someverybaduseragentname1" is entered as "\bsomeverybaduseragentname1\b"
|
||||
# Example the User-Agent name "some-very-bad-useragentname2" is entered as "\bsome\-very\-bad\-useragentname1\b"
|
||||
# the "\b" are word boundaries which prevents partial matching and false positives.
|
||||
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
|
||||
# ---------------------
|
||||
# WHITELISTING EXAMPLES
|
||||
# ---------------------
|
||||
# "~*\bsomeverygooduseragentname1\b" 0;
|
||||
# "~*\bsomeverygooduseragentname2\b" 0;
|
||||
# "~*\bsome\-very\-good\-useragentname2\b" 0;
|
||||
|
||||
# ---------------------
|
||||
# BLACKLISTING EXAMPLES
|
||||
# ---------------------
|
||||
# "~*\bsomeverybaduseragentname1\b" 3;
|
||||
# "~*\bsomeverybaduseragentname2\b" 3;
|
||||
# "~*\bsome\-very\-bad\-useragentname2\b" 3;
|
||||
|
||||
|
||||
|
||||
63
.dev-tools/_conf_files_testing_changes/bots.d/blockbots.conf
Normal file
63
.dev-tools/_conf_files_testing_changes/bots.d/blockbots.conf
Normal file
|
|
@ -0,0 +1,63 @@
|
|||
# Author: Mitchell Krog <mitchellkrog@gmail.com> - https://github.com/mitchellkrogza/
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2017.02
|
||||
### Updated: Mon Aug 21 11:29:32 SAST 2017
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Include this in a vhost file within a server {} block using and include statement like below
|
||||
|
||||
# server {
|
||||
# #Config stuff here
|
||||
# include /etc/nginx/bots.d/blockbots.conf
|
||||
# include /etc/nginx/bots.d/ddos.conf
|
||||
# #Other config stuff here
|
||||
# }
|
||||
|
||||
#######################################################################
|
||||
|
||||
# BOTS
|
||||
# ****
|
||||
#limit_conn bot1_connlimit 100;
|
||||
limit_conn bot2_connlimit 10;
|
||||
#limit_req zone=bot1_reqlimitip burst=50;
|
||||
limit_req zone=bot2_reqlimitip burst=10;
|
||||
if ($bad_bot = '3') {
|
||||
return 444;
|
||||
}
|
||||
|
||||
# BAD REFER WORDS
|
||||
# ***************
|
||||
if ($bad_words) {
|
||||
return 444;
|
||||
}
|
||||
|
||||
|
||||
# REFERERS
|
||||
# ********
|
||||
if ($bad_referer) {
|
||||
return 444;
|
||||
}
|
||||
|
||||
# IP BLOCKS
|
||||
# *********
|
||||
if ($validate_client) {
|
||||
return 444;
|
||||
}
|
||||
|
||||
#######################################################################
|
||||
|
|
@ -0,0 +1,48 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO ADD ANY ADDITIONAL BAD REFERRER DOMAINS YOU WANT TO SCAN FOR ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.05
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# This is merely an example and gets auto included as since Version 2.2017.07 introduced on 2017-04-20
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# Only add one entry per line
|
||||
|
||||
# Make sure any domains have dots and special characters escaped as per the Regex examples below.
|
||||
# For example some-veryvery-randomwebsitename-thatdoesnotexist4.com should be entered as
|
||||
# some\-veryvery\-randomwebsitename\-thatdoesnotexist4\.com
|
||||
|
||||
# *****************************************************************************************
|
||||
# PLEASE MAKE SURE that you use word regex boundaries to avoid false positive detection !!!
|
||||
# *****************************************************************************************
|
||||
|
||||
# As you can see in the examples below the domain "someveryveryrandomwebsitenamethatdoesnotexist1\.com"
|
||||
# is entered with a preceding \b and an ending \b
|
||||
# this makes it now "\bsomeveryveryrandomwebsitenamethatdoesnotexist1\.com\b".
|
||||
# It is crucial to use the word boundaries regex formatting.
|
||||
# ---------
|
||||
# EXAMPLES:
|
||||
# ---------
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
# "~*\bsomeveryveryrandomwebsitenamethatdoesnotexist1\.com\b" 1;
|
||||
# "~*\bsomeveryveryrandomwebsitenamethatdoesnotexist2\.com\b" 1;
|
||||
# "~*\bsomeveryveryrandomwebsitenamethatdoesnotexist3\.com\b" 1;
|
||||
# "~*\bsome\-veryvery\-randomweb\-sitenamethatdoesnotexist4\.com\b" 1;
|
||||
|
||||
|
||||
|
||||
36
.dev-tools/_conf_files_testing_changes/bots.d/ddos.conf
Normal file
36
.dev-tools/_conf_files_testing_changes/bots.d/ddos.conf
Normal file
|
|
@ -0,0 +1,36 @@
|
|||
#######################################################################
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2017.01
|
||||
### Updated: Sun Jan 29 11:35:32 SAST 2017
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Author: Mitchell Krog <mitchellkrog@gmail.com> - https://github.com/mitchellkrogza/
|
||||
|
||||
# Include this in a vhost file within a server {} block using and include statement like below
|
||||
|
||||
# server {
|
||||
# #Config stuff here
|
||||
# include /etc/nginx/bots.d/blockbots.conf
|
||||
# include /etc/nginx/bots.d/ddos.conf
|
||||
# #Other config stuff here
|
||||
# }
|
||||
|
||||
#######################################################################
|
||||
|
||||
limit_conn addr 200;
|
||||
limit_req zone=flood burst=200 nodelay;
|
||||
|
|
@ -0,0 +1,45 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO WHITELIST YOUR OWN DOMAIN NAMES AND SPARE THEM FROM ANY REFERRER CHECKING ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.04
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Add One Entry Per Line - List all your own domains of the sites you host on the server
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# Automatic updates will never be able to remove this custom list of yours
|
||||
# Add One Entry Per Line
|
||||
|
||||
# Make sure any domains have dots and special characters escaped as per the Regex examples below.
|
||||
# For example myfirstowndomainname.com should be entered as myfirstowndomainname\.com
|
||||
# and my-second-owndomainname.com should be entered as my\-second\-owndomainname\.com
|
||||
|
||||
# *****************************************************************************************
|
||||
# PLEASE MAKE SURE that you use word regex boundaries to avoid false positive detection !!!
|
||||
# *****************************************************************************************
|
||||
|
||||
# As you can see in the examples below the domain "myfirstowndomainname\.com" is entered with a preceding \b and an ending \b
|
||||
# this makes it now "\bmyfirstowndomainname\.com\b". It is crucial to use the word boundaries regex formatting.
|
||||
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
# ---------
|
||||
# EXAMPLES:
|
||||
# ---------
|
||||
# "~*\bmyfirstowndomainname\.com\b" 0;
|
||||
# "~*\bmy\-second\-owndomainname\.com\b" 0;
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,37 @@
|
|||
# EDIT THIS FILE AS YOU LIKE TO WHITELIST ALL YOUR IP ADDRESSES AND IP RANGES ###
|
||||
|
||||
### VERSION INFORMATION #
|
||||
###################################################
|
||||
### Version: V3.2018.03
|
||||
### Updated: 2018-08-21
|
||||
###################################################
|
||||
### VERSION INFORMATION ##
|
||||
|
||||
##############################################################################
|
||||
# _ __ _ #
|
||||
# / |/ /__ _(_)__ __ __ #
|
||||
# / / _ `/ / _ \\ \ / #
|
||||
# /_/|_/\_, /_/_//_/_\_\ #
|
||||
# __/___/ __ ___ __ ___ __ __ #
|
||||
# / _ )___ ____/ / / _ )___ / /_ / _ )/ /__ ____/ /_____ ____ #
|
||||
# / _ / _ `/ _ / / _ / _ \/ __/ / _ / / _ \/ __/ '_/ -_) __/ #
|
||||
# /____/\_,_/\_,_/ /____/\___/\__/ /____/_/\___/\__/_/\_\\__/_/ #
|
||||
# #
|
||||
##############################################################################
|
||||
|
||||
# Add One Entry Per Line - List all your IP's and IP Ranges you want to whitelist
|
||||
# This file must exist on your system or Nginx will fail a reload due to a missing file
|
||||
# Automatic updates will never be able to remove this custom list of yours
|
||||
# Add One Entry Per Line as per the example
|
||||
# Only add actual IP addresses and ranges here
|
||||
|
||||
# BY DEFAULT ALL THE EXAMPLES BELOW ARE COMMENTED OUT AND HENCE NOT ENABLED
|
||||
# REFRAIN FROM USING 127.0.0.1 AS IT MAY CAUSE UNDESIRABLE RESULTS ON SOME SYSTEMS
|
||||
# ---------
|
||||
# EXAMPLES:
|
||||
# ---------
|
||||
# 111.111.111.111 0;
|
||||
|
||||
|
||||
35.193.7.13 0;
|
||||
104.154.120.187 0;
|
||||
Loading…
Add table
Add a link
Reference in a new issue