# BEGIN iThemes Security - Do not modify or remove this line
# iThemes Security Config Details: 2
	# Ban Hosts - Security > Settings > Banned Users
	SetEnvIF REMOTE_ADDR "^3\.92\.4\.192$" DenyAccess
	SetEnvIF X-FORWARDED-FOR "^3\.92\.4\.192$" DenyAccess
	SetEnvIF X-CLUSTER-CLIENT-IP "^3\.92\.4\.192$" DenyAccess

	SetEnvIF REMOTE_ADDR "^194\.26\.192\.169$" DenyAccess
	SetEnvIF X-FORWARDED-FOR "^194\.26\.192\.169$" DenyAccess
	SetEnvIF X-CLUSTER-CLIENT-IP "^194\.26\.192\.169$" DenyAccess

	SetEnvIF REMOTE_ADDR "^91\.92\.247\.2$" DenyAccess
	SetEnvIF X-FORWARDED-FOR "^91\.92\.247\.2$" DenyAccess
	SetEnvIF X-CLUSTER-CLIENT-IP "^91\.92\.247\.2$" DenyAccess

	<IfModule mod_authz_core.c>
		<RequireAll>
			Require all granted
			Require not env DenyAccess
			Require not ip 3.92.4.192
			Require not ip 194.26.192.169
			Require not ip 91.92.247.2
		</RequireAll>
	</IfModule>
	<IfModule !mod_authz_core.c>
		Order allow,deny
		Allow from all
		Deny from env=DenyAccess
		Deny from 3.92.4.192
		Deny from 194.26.192.169
		Deny from 91.92.247.2
	</IfModule>
# END iThemes Security - Do not modify or remove this line

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /home/
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /home/index.php [L]
</IfModule>

# END WordPress