saxtus

Hmm, finally an official answer!

What about auto-blocking attackers through deny rules at .htaccess file?
It’s gone with Falcon engine?

Falcon engine’s ability to block brute force attacks at Apache level, instead of PHP/MySQL level, was the most important thing for me to keep Wordfence installed.

Caching was a nice addition, but I’ve quickly reverted today back to WP Fastest Cache that also sets correctly cache headers, something that Falcon engine didn’t do (among other things — feel free to check your sites on gtmetrix.com with each cache solution).

Now I will probably seek an alternative to Wordfence, one that also blocks brute force attackers at Apache level. Any suggestions?

I thought Falcon engine is the only option to block attacking IPs at .htaccess level and stop bottlenecking PHP/MySQL.

Will be an alternative that will offer .htaccess level IP block or we are heading to replace Wordfence with another plugin that does that?

I suppose you’ve discussed this privately but do you care to update us about the reason why WF free didn’t detect them?