Spam_BLIP vs SpamJam – Anti-Spam Protection for Comments & Forms

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.

Spam should not create more work for you—or more friction for your visitors. SpamJam quietly stops automated comment spam with layered, on-site checks. There are no CAPTCHAs to solve, no puzzles to frustrate readers, and no complicated setup before protection begins. Install it, activate it, and get back to running your site. Why Site Owners Choose SpamJam 🚫 Less Spam to Moderate – Catch automated submissions before they clutter your comment queue. 👤 No Friction for Real People – Visitors can comment without image grids, challenges, or extra verification steps. ⚡ Protected from Activation – Core comment protection is enabled by default, with sensible settings already in place. 🧠 Fewer False Positives – Multiple signals work together; suspicious edge cases can be held for review instead of being discarded. 🩶 Lightweight by Design – Focused checks run where they are needed, without loading a heavy front-end framework. 🔒 Privacy-Conscious Detection – Core comment analysis runs on your WordPress site rather than sending comment content to a remote spam-scoring service. Free Comment Protection The free version gives blogs, publishers, and WooCommerce stores a strong first line of defense: Per-site salted honeypot – An invisible, site-specific trap makes generic bot scripts easier to identify. Submission timing check – Detects forms submitted faster than a person could reasonably complete them. Weighted spam scoring – Combines form, timing, token, and referrer signals instead of relying on one fragile test. Safer moderation path – Suspicious submissions below the blocking threshold can be held for review. Secure form validation – Nonces and time-boxed HMAC tokens help verify legitimate comment submissions. Built-in keyword blocklist – Stops common comment-spam patterns. WooCommerce product reviews – Protects review forms and declares compatibility with WooCommerce HPOS. No-JavaScript fallback – Visitors with JavaScript disabled are not automatically hard-blocked. Dashboard statistics – See the protection working from your WordPress admin. No account or API key is required to start protecting comments. Go Beyond Comments with SpamJam Pro When spam reaches registrations, contact forms, or a high-traffic site, SpamJam Pro adds the control and visibility you need: Protection for popular form plugins – Cover Contact Form 7, WPForms, Gravity Forms, Elementor Forms, Fluent Forms, Formidable Forms, Ninja Forms, and WooCommerce registration. Actionable spam inbox – Search and filter events, review false positives, restore recoverable comments, allow trusted senders, and use bulk actions. Source-aware rules – Allow, moderate, block, or discard submissions using conditions tailored to each protected source. Registration protection – Add honeypot checks and email confirmation to WordPress registrations. Flood and content controls – Set rate limits, minimum comment length, maximum links, and your own blocked terms. Targeted blocking – Block configured IP addresses, email addresses, domains, or countries while allowlisting trusted senders. Reports and analytics – Understand trends, sources, repeat signals, and false positives; receive weekly summaries or export PDF reports. Professional site tools – Add an automatically updated extended blocklist, multisite synchronization, and white-label controls. Every Pro feature is included. Choose a license based only on the number of sites you manage from SpamJam’s Account screen in your WordPress dashboard. Built for the Sites Spam Targets SpamJam is a practical fit for: Blogs and publications with open comments WooCommerce stores collecting product reviews Membership and community sites accepting registrations Lead-generation sites using popular form plugins Agencies managing protection across multiple WordPress sites How SpamJam Stops Bots SpamJam looks for the patterns automated submissions leave behind: A site-specific hidden field catches bots that fill every input. A signed timestamp identifies implausibly fast submissions. Secure tokens and referrer checks test whether the request came through the expected form flow. A built-in blocklist catches common spam content. A weighted scoring engine combines those signals and decides whether to allow, hold, or block the submission. Real visitors keep the familiar WordPress comment experience. The protection stays in the background. Privacy & Data Handling Core comment detection is performed on your site and does not require a remote content-scoring service. Optional logging is off by default. If you enable it, you control retention, and recovery data can be disabled for metadata-only logging. SpamJam excludes passwords, nonces, security tokens, CAPTCHA values, and CSRF fields from recoverable form data. Some optional licensing, update, geographic blocking, and premium blocklist features connect to external services when used. Review your site’s privacy obligations and enabled settings as you would with any WordPress plugin.