Comprehensive and Easy-To-Use WordPress Security - Comes With Business Grade Support, with no "premium" restrictions
Please see the dedicated help centre for details on features and some FAQs.
Easy - we're just better! ;)
We don't have a premium version and we offer full support - see our Reviews for our users' opinions!
Secondly, we don't modify a single core WordPress or web hosting file. This is important and explains why randomly you upgrade your security plugin and your site dies.
Ideally you shouldn't use this along side other Anti-SPAM plugins or security plugins. If there is a feature you need, please feel free to suggest it in the support forums.
This plugin is an application layer firewall, not a server/network firewall. It is designed to interpret web calls to your site to look for attempts to circumvent it and gain unauthorized access.
Your network firewall is designed to restrict access to your server based on certain types of network traffic. The WordPress Simple Firewall is designed to restrict access to your site, based on certain type of web calls.
Any IP address that is on the whitelist will not be subject to any of the firewall processing. This setting takes priority over all other settings.
Yes. To specify a range you use CIDR notation. E.g. ABC.DEF.GHJ.KMP/16
You can't. The plugin runs an automatic black list IP system so you don't need to maintain any manual lists.
This happens when any the following 3 conditions are met:
You can completely turn OFF (and ON) the WordPress Simple Firewall by creating a special file in the plugin folder.
If you want to turn the firewall on in the same way, create a file called "forceOn".
Remember: If you leave one of these files on the server, it will override your on/off settings, so you should delete it when you no longer need it.
Whitelist. So if you have the same address in both lists, it'll be whitelisted and allowed to pass before the blacklist comes into effect.
The changelog outlines the main changes for each release. We group changes by minor release "Series". Changes in smaller "point" releases are highlighted using (v.1) notation. So for example, version 4.4.1 will have changelog items appended with (v.1)
Yes! We actively develop our plugin on Github and the best thing you can do is submit pull request and bug reports which we'll review.
It is a comma-separated list of pages and parameters. A NEW LINE should be taken for each new page name and its associated parameters.
The first entry on each line (before the first comma) is the page name. The rest of the items on the line are the parameters.
The following are some simple examples to illustrate:
On the edit.php page, the parameter with the name 'featured' will be ignored.
admin.php, url, param01, password
Any parameters that are passed to the page ending in 'admin.php' with the names 'url', 'param01' and 'password' will be excluded from the firewall processing.
*, url, param, password
Putting a star first means that these exclusions apply to all pages. So for every page that is accessed, all the parameters that are url, param and password will be ignored by the firewall.
When enabled the plugin will prevent more than 1 login attempt to your site every "so-many" seconds. So if you enable a login cooldown of 60 seconds, only 1 login attempt will be processed every 60 seconds. If you login incorrectly, you wont be able to attempt another login for a further 60 seconds.
More Info: http://icwp.io/2t
This is best described on the blog
The Automatic (Background) WordPress updates happens on a WordPress schedule - it doesn't happen immediately when an update is detected. You can either manually upgrade, or WordPress will handle it in due course.
You can add some custom code to your functions.php exactly as the following:
add_filter( 'icwp_wpsf_print_admin_ip_footer', '__return_false' );
Requires: 3.5.0 or higher
Compatible up to: 4.4
Last Updated: 1 week ago
Active Installs: 30,000+
35 of 52 support threads in the last two months have been resolved.
Got something to say? Need help?