Antispam Bee vs CIDRAM

Say Goodbye to comment spam on your WordPress blog or website. Antispam Bee blocks spam comments and trackbacks effectively, without captchas and without sending personal information to third party services. It is free of charge, ad-free and 100% GDPR compliant. Feature/Settings Overview Trust approved commenters. Trust commenters with a Gravatar. Consider the comment time. Allow comments only in a certain language. Block or allow commenters from certain countries. Treat BBCode links as spam. Use regular expressions. Search local spam database for commenters previously marked as spammers. Notify admins by e-mail about incoming spam. Delete existing spam after n days. Limit approval to comments/pings (will delete other comment types). Select spam indicators to send comments to deletion directly. Optionally exclude trackbacks and pingbacks from spam detection. Optionally spam-check comment forms on archive pages. Display spam statistics on the dashboard, including daily updates of spam detection rate and a total of blocked spam comments. Support Community support via the support forums on wordpress.org Read the documentation We don’t handle support via e-mail, Twitter, GitHub issues etc. Contribute Active development of this plugin is handled on GitHub. Pull requests for documented bugs are highly appreciated. If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the support forums first. If you want to help us translate this plugin you can do so on WordPress Translate. Credits Author: Sergej Müller Maintainers: pluginkollektiv

CIDRAM (Classless Inter-Domain Routing Access Manager) is a PHP script designed to protect websites by blocking requests originating from IP addresses regarded as being sources of undesirable traffic, including (but not limited to) traffic from non-human access endpoints, cloud services, spambots, scrapers, etc. It does this by calculating the possible CIDRs of the IP addresses supplied from inbound requests and then attempting to match these possible CIDRs against its signature files (these signature files contain lists of CIDRs of IP addresses regarded as being sources of undesirable traffic); If matches are found, the requests are blocked. Requirements PHP >= 7.2.0 PCRE Updating Note: CIDRAM does not interact in any way with your database, and stores its own configuration settings, customisations, and related materials as flatfiles within its own directory. If you’ve not changed any of the default configuration settings and if you’re not using any customisations for this plugin, updating normally via the plugins dashboard, without need for any additional steps, should be sufficient and shouldn’t cause any problems. However, if you’ve modified the configuration settings for CIDRAM, or if you’ve made any customisations, I would recommend making backups of all of these prior to updating, due to that updating will overwrite all settings and customisations (after updating, you can then restore your customisations from your backups). Alternatively, if you update via the CIDRAM front-end updates page, all settings and customisations should be preserved.