Prevent people from registering via your comment moderation blacklist.
| Author: | Mika Epstein (profile at wordpress.org) |
| WordPress version required: | 5.5 |
| WordPress version tested: | 6.1.1 |
| Plugin version: | 3.1.2 |
| Added to WordPress repository: | 03-05-2009 |
| Last updated: | 18-11-2022 |
| Rating, %: | 92 |
| Rated by: | 39 |
| Plugin URI: | http://halfelf.org/plugins/ban-hammer/ |
| Total downloads: | 104 905 |
| Active installs: | 8 000+ |
 Click to start download |
|
We’ve all had this problem: a group of spammers from mail.ru are registering to your blog, but you want to keep registration open. How do you kill the spammers without bothering your clientele? While you could edit your theme’s functions.php and block the domain, once you get past a few bad eggs, you have to escalate.
Ban Hammer helps you do that by preventing unwanted users from registering.
On a single install of WordPress, instead of using its own database table, Ban Hammer pulls from your list of prohibited emails from the Disallowed Comment Keys feature, native to WordPress. Since emails never equal IP addresses, it simply skips over and ignores them.
On a network instance, there’s a network wide setting for banned emails and domains. This means you only have one place to update and maintain your blocked list. When a listed user attempts to register, they get a customizable message that they cannot register.
For advanced documentation, including how to use on WooCommerce, please visit the Ban Hammer Wiki.
Privacy Policy
This plugin does not track data outside of what WordPress already collects. It utilizes the submitted email address to validate the domain and compares it to the list of prohibited domains and emails. No additional data is processed.
Credits
Ban Hammer is a very weird fork of Philippe Paquet’s No Disposable Email plugin. The original plugin was a straight forward .dat file that listed all the bad emails (generally ones like mailinator that are disposable) and while Ban Hammer doesn’t do that, this would not have been possible without that which was done before.
Many thanks are due to WP-Deadbolt, for making me think about SQL and TTC for StopForumSpam integration. MASSIVE credit to Travis Hamera for the StopForumSpam/cURL fix! And then props to Helen Hou-Sandà for not using curl at all. Protip? Use WP_http instead!