Hi @username12,
The post above is certainly useful and shows why we don’t block VPNs outright. Generally speaking you shouldn’t need a manual blocking regime as Wordfence works on intent and type of visit. Your own Brute Force or Rate Limiting settings can be tweaked to be as strict/lenient as you prefer – so long as it works for your legitimate visitors without blocking them.
In terms of bot registrations, it’s very common for them to come through XML-RPC, which can be disabled. “Disable XML-RPC authentication” appears in Wordfence > Login Security > Settings. You can also block this route entirely using .htaccess, provided you don’t use the WordPress app or a plugin that requires it such as Jetpack:
# Block WordPress xmlrpc.php requests
<Files xmlrpc.php>
order deny,allow
deny from all
</Files>
You could also enable reCAPTCHA for registration/logins using our Login Security module to ensure humans are able to complete the form, but it should be effective at blocking automatic bot registrations.
Thanks,
Peter.