# EDIT THIS FILE AS YOU LIKE TO ADD OR REMOVE ANY BAD WORDS YOU WANT TO SCAN FOR ###

##############################################################################
#        ___                 __                                              #
#       / _ | ___  ___ _____/ /  ___                                         #
#      / __ |/ _ \/ _ `/ __/ _ \/ -_)                                        #
#     /_/ |_/ .__/\_,_/\__/_//_/\__/                                         #
#        __/_/        __   ___       __     ___  __         __               #
#       / _ )___ ____/ /  / _ )___  / /_   / _ )/ /__  ____/ /_____ ____     #
#      / _  / _ `/ _  /  / _  / _ \/ __/  / _  / / _ \/ __/  '_/ -_) __/     #
#     /____/\_,_/\_,_/  /____/\___/\__/  /____/_/\___/\__/_/\_\\__/_/        #
#                                                                            #
##############################################################################

# 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

SetEnvIfNoCase Referer ~*adultgalls spam_ref
SetEnvIfNoCase Referer ~*bigblackbooty spam_ref
SetEnvIfNoCase Referer ~*cookie-law-enforcement spam_ref
SetEnvIfNoCase Referer ~*free-share-buttons spam_ref
SetEnvIfNoCase Referer ~*free-social-buttons spam_ref
SetEnvIfNoCase Referer ~*fuck-paid-share-buttons spam_ref
SetEnvIfNoCase Referer ~*law-enforcement-bot spam_ref
SetEnvIfNoCase Referer ~*law-enforcement-check spam_ref
SetEnvIfNoCase Referer ~*share-buttons-for-free spam_ref
SetEnvIfNoCase Referer ~*social-buttons- spam_ref
SetEnvIfNoCase Referer ~*vvakhrin-ws1 spam_ref
SetEnvIfNoCase Referer ~*xxxrus spam_ref