dika283

This plugin’s function is to check the IP address of the comment sender, gravatar, comment content.
How this plugin works : 1. Getting IP blacklist from stopforumspam.org This step determines the IP is a spammer or not by checking the IP on http://api.stopforumspam.org/api?ip=(the IP sender) using curl. The result will be appear on the form of .txt Non spammer IP will be marked by “no”
<ol>
<li>
Validating the gravatar Access https://secure.gravatar.com/avatar/(encoded email) Later,you can get the data of the registered email by using curl.
</li>
<li>
Validating the comment content Create hook on ‘wp_blacklist_check’ to check if the content of the comment contains the word listed on the Comment Blacklist on wp-admin Comment Blacklist is stored on Beon Intermedia’s server that is copied on the user’s wp-admin. User can add and delete the keyword listed on Comment Blacklist from wp-admin. Meanwhile, user can see only the keyword of Comment Blacklist on http://db1.andhikamw.com/ The updated Comment Blacklist keyword is shown on the column ‘update_secure_discussion’ of wp-option table
</li>
</ol>
After the comment is submitted, the plugin will determine whether the comment is a spammer or not from its IP , gravatar and comment content. Next, this plugin will change automatically the status into approve, moderation, or spam. However, the user can change the default status by himself on wp-admin (sub menu ‘Beon Comment Option’) as shown on Screenshot_2.png At the end, the plugin will force the default status (generated by the plugin) into the same setting of the wp-admin (managed by user) by using hook ‘pre_comment_approved’

Beon Comment Protection

Detect the comment which potentially recognized as spam

Blobfolio

CAPTCHA fields inhibit both human and robot participation in important kitty-related discussions. Sock’Em SPAMbots exists to take a more seamless approach to SPAM blocking, placing the burden on the robots, not the humans. Any combination of the following can be enabled:
<ul>
<li>Javascript: require basic Javascript support, and in the process prove the user visited the actual comment form (instead of just submitting straight to WP).</li>
<li>Cookies: require basic cookie support, and again, prove the user visited the site before submitting a comment.</li>
<li>Honeypot: generic formbots will often populate all form fields with gibberish, so we can assume that if text is added to an invisible field, something robotic is happening!</li>
<li>Speed: automated scripts complete comment forms with inhuman speed, thus if submissions happen really quickly, we can assume it is a robot doing the submitting!</li>
<li>Links: reject comments with excessive number of links.</li>
<li>Disable trackbacks or pingbacks independently of one another.</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 3.6 or later.</li>
<li>PHP 7.3 or later.</li>
</ul>
Please note: it is not safe to run WordPress atop a version of PHP that has reached its <a href="http://php.net/supported-versions.php" rel="nofollow ugc">End of Life</a>. Future releases of this plugin might, out of necessity, drop support for old, unmaintained versions of PHP. To ensure you continue to receive plugin updates, bug fixes, and new features, just make sure PHP is kept up-to-date. 🙂
<h3>Privacy Policy</h3>
This plugin makes use of the same “Personal Data” WordPress does when parsing comment form submissions.
When the optional debugging mode is enabled — which should never be the case on a public-facing site! — all comment form submissions are logged to a file on the local server.
When the optional cookie requirement test is enabled, a small cookie will be placed on each visitor’s machine. These cookies are not personally identifiable or used for any kind of tracking purposes; they merely enable the plugin to answer the question, “Do you support cookies?”

Sock'Em SPAMbots

A more seamless approach to deflecting the vast majority of SPAM comments.

Beon Comment Protection vs Sock'Em SPAMbots