La Sentinelle antispam vs Spam_BLIP

Feel safe knowing that your website is safe from spam. La Sentinelle will guard your WordPress website against spam in a simple and effective way. It has antispam filters for comment forms and registration forms and can be extended to support plugins. The default settings should catch most spambots, and there is a settingspage to set it up according to your wishes. Current features include: 3 antispam features; Honeypot, Nonce, Form Timeout. These 3 spamfilters depend on JavaScript on the frontend. 1 antispam feature; Stop Forum Spam. Settingspage to set things up according to your wishes. Transparent to the visitor, no nagging with Captcha’s or other annoying things. By default no use of third-party services and no tracking of visitors. Lightweight and simple code. Logging for WordPress Comments and which spamfilter marked it as spam. Logging for Custom forms and which spamfilter marked it as spam. Statistics for every form how many spam submissions were blocked. WordPress forms that are protected: WordPress Comments form. WordPress Login form. WordPress Register form. WordPress Lost Password form. Form Plugins that are protected: Caldera Forms. Clean Login (Login form). Contact Form 7. Easy Digital Downloads (Login form, Register form). Everest Forms. Formidable Form Builder. Forminator. Newsletter Optin Box plugin (noptin) (standalone forms). Ultimate Member (Login form, Register form and Lost Password form). WooCommerce (Login form, Lost Password form). WPForms Lite. WP Job Manager plugin (submit job form when registering is enabled). Support If you have a problem or a feature request, please post it on the plugin’s support forum on wordpress.org. I will do my best to respond as soon as possible. If you send me an email, I will not reply. Please use the support forum. Translations Translations can be added very easily through GlotPress. You can start translating strings there for your locale. They need to be validated though, so if there’s no validator yet, and you want to apply for being validator (PTE), please post it on the support forum. I will make a request on make/polyglots to have you added as validator for this plugin/locale. How to choose an antispam plugin When you look through the WordPress Plugin Repository you will see more than a hundred antispam plugins. Which one is the best one? Short answer, there is no “best one”. No spamfilter and no method for spamfiltering is perfect. Slightly longer answer, you could try about twenty and choose the one that fits your needs best. But there is also a really long answer. There are different methods that can be used against spam, and every method has its drawbacks. In my opinion, having a low number of false positives is more important than perfectly marking all spam, you don’t want to miss out on important people or information. Nagging the user in some way has a similar effect, the user might not even want to bother with that and just walk away. Third party services: Services like Akismet, OOPSpam, Stop Forum Spam and also reCAPTCHA offer third party services to check for spam. This can be very effective, but you are giving user submitted data away to these third parties and are also giving your users up for tracking them. Captcha’s, reCAPTCHA and Quizz Questions: You are annoying your users and probably sending some of them away. This especially counts for reCAPTCHA for visitors who have third party cookies disabled. Blacklists: Often running behind the facts. That goes for the way of getting users off that list, and also in getting users on that list. Referer check: check if the Referer header is set correctly. You can never trust it is set correctly. Modern browsers are limiting the use of Referers, though for now that is mostly for third-party domains. JavaScript methods: Spammers often (always?) don’t use JavaScript, they just post the form with spammy data. Drawback for this method is that statistics say that about 1 percent of users has JavaScript disabled. Also, some websites have broken JavaScript, which might make the spamfilter break as well. Activation email for registering users. Users only get activated after clicking a link in an activation email. You still have all the non-activated users in your site however. You could have a bright idea about combining several methods, but then you get the drawbacks of all the methods you use. Another complication of choosing a good plugin is that most antispam plugins don’t tell you what methods they use. The documentation doesn’t tell you, and looking at the source code just leaves you confused at the chaos that it often is. My main motivation for writing this plugin is to offer a plugin that does spamfiltering with JavaScript methods in a simple and effective way. The claimed 1 percent of users that has JavaScript disabled will also be tech-savy enough to enable it again for your website. Compatibility This plugin is compatible with ClassicPress. Contributions This plugin is also available in Codeberg.

Spam BLIP stops comment and ping spam from being posted, primarily by checking the IP address attempting to post a comment in one or more of the public DNS blacklists. A number of options are available to refine the check, and with the option defaults, a DNS lookup is only performed the first time an address attempts to post a comment; thereafter, the address might quickly ‘pass’ because it was not listed, or quickly be rejected because it was listed. Spam BLIP creates, and maintains, a database table for this purpose, and database lookups are quite fast. Therefore, concerns about DNS lookup time can be limited to an initial comment attempt. Here are some features of Spam BLIP to consider if you are not yet falling over yourself to get it installed: When WordPress is producing a page for a visitor, it checks whether comments are open for each post, and it allows plugins to “filter” the check. Spam BLIP uses that filter, but does not do DNS lookups at this stage, because DNS lookups can take perceptible time. Spam BLIP does check optional user-set black and white lists, and optionally existing comments that are marked as spam, and of course Spam BLIP’s own database records. Those checks are fast, so they should not have a perceptible effect on page loading. Furthermore, on pages with multiple posts, WordPress runs the filter for each, but Spam BLIP stores the first result, so even the fast checks are not repeated. When a comment is actually submitted, Spam BLIP does the above checks, then the DNS lookup only if necessary. At this stage, if the DNS lookup causes a perceptible delay, a real human (or very clever pet) making the comment should perceive it as mere server-side processing. As for spammer robots . . . let them wait. Spam BLIP comes configured with blacklist domains that have worked well during development, so a user should not need to be concerned with the blacklists, but there is an advanced option to add or delete, activate or disable (yet save) list domains, and configure the interpretation of a return from a successful lookup. Spam BLIP provides user-set whitelist and blacklist options. Spam BLIP provides options to check for pings/trackbacks, and for user registrations. (The option to blacklist-check user registration is off by default. See “Tips” under the help tab on the Spam BLIP settings page.) Spam BLIP provides options to configure a ‘Time To Live’ (TTL) for its database records, and a maximum number of records. The TTL is important because, generally, an IP address should not be marked permanently. Consider an ISP that quickly disables any account that is found to be spamming. An honest ISP is also a victim of spammer abuse, and will need to reuse addresses. DNS blacklist operators provide means for IP address owners to get records removed — Spam BLIP provides a configurable TTL for its records. (Database table maintenance is triggered approximately hourly by a WordPress cron event.) Spam BLIP will optionally check if a commenter address is a TOR exit node. TOR (The Onion Router) is an important protection for people who need or wish for anonymity. You may want to accept comments from TOR users (you should), but unfortunately spammers have exploited and abused TOR, which has led some DNS blacklist operators to include TOR exit node addresses whether or not it is known that the address is spamming. If you enable this option (you should), it might let some spam get through. In this case, mark the comment as spam, and use the Spam BLIP option to check existing comments marked as spam; or use Spam BLIP in concert with another sort of spam filter, such as one that analyzes comment content. (Please report any conflict with other, non-DNS blacklist type spam plugins. Note that Spam BLIP is not expected to work in concert with other DNS-type anti-spam plugins.) Spam BLIP includes a widget that will show options and records information. The widget might or might not be an enhancement to your page, but in any case it should provide feedback while you evaluate Spam BLIP, so it might be used temporarily.