Anti Spam

CC WordPress Anti-spam Documentation.

1. Introduction
2. Installation
3. License activation
4. Management panel
5. Protection of comments
6. Protection of user registration
7. Integration with external forms
8. IP blocking system
9. Log management
10. Statistics and reports
11. Automatic tasks (CRON)
12. Advanced settings
13. Troubleshooting
14. FAQ

1. introduction

• Protecting WordPress comments from spam
• Securing user registration forms
• Integration with Contact Form 7 and Gravity Forms
• Advanced IP blocking system (temporary and permanent)
• Honeypot field invisible to users
• Checking the time of filling the forms
• Filtering content based on banned words
• Detailed logging of all anti-spam activity
• IP check cache system for better performance
• Automatic cleaning tasks (CRON)
• White list of allowed IP addresses
• Statistics and activity reports
• License management system

2 Installation

• WordPress 5.0 or later
• PHP 7.4 or later
• MySQL database 5.6 or later
• Permission to create tables in the database
• Access to CRON settings (optional)

1. Download the ZIP file of the plugin from the official site cocos.codes
2. Log in to your WordPress admin panel
3. Go to: Plugins → Add New → Upload plugin to server
4. Select the downloaded ZIP file and click "Install Now".
5. Once the installation is complete, click "Activate Plugin"
6. The plug-in will automatically create the necessary tables in the database
7. Go to Settings → CC Anti-spam to configure the plugin

3. license activation

1. After installation, go to Settings → CC Anti-Spam
2. Select the "License" tab
3. Enter the license key you received after purchase
4. Click "Activate License"
5. After successful activation, a confirmation message will be displayed
6. All features of the plug-in will be unlocked

4. management panel

• Settings - configuration of all anti-spam protection features
• Logs - viewing activity logs with filtering and pagination
• Statistics - detailed reports and blocking statistics

• Documentation - link to full online manual
• License - plug-in license management
• Plugins - information on other COCOS extensions
• Support - access to technical support

5. protection of comments

• Honeypot field - invisible field that only bots fill in
• Fill time check - blocking forms that are filled out too quickly or too slowly
• Content filtering - checking for banned words in the body of the comment
• Limit the number of links - blocking comments with excessive URLs
• IP checking - verification that the IP address is not blocked

1. Under the "Settings" tab, check "Protect comments from spam."
2. Set the minimum time for filling out the form (default is 3 seconds)
3. Specify the maximum number of links in a comment (default is 2)
4. Add forbidden words (one per line)
5. Save your settings

6. protection of user registration

• Honeypot field - As in comments, invisible to real users
• Checking the registration time - minimum form filling time (default is 5 seconds)
• Validation of user fields - checking username, email and URL for suspicious patterns
• Filtering temporary emails - blocking of known temporary email services

• Username: patterns like "user123", very short/long names, spam-related words
• Email: addresses from 10minutemail, tempmail, guerrillamail, .tk/.ml/.ga/.cf domains
• URL: link shorteners, gambling/crypto-related domains, suspicious parameters

7 Integration with external forms

• Automatically add honeypot fields to all forms
• Fill time check (default min. 2 seconds)
• Filtering message content based on banned words
• Validation before shipment with appropriate error messages

• Adding honeypot fields to form tags
• Fill time control (default min. 3 seconds)
• Filtering form text fields
• Marking form as invalid with messages

1. Plugin automatically detects active form plugins
2. In the "External Forms Protection" section, enable protection for detected plug-ins
3. Set minimum fill times for each form type
4. Enable message content filtering
5. Save your settings

8. IP blocking system

• Time locks - automatic expiration after a specified time (30 min - 24h)
• Fixed locks - permanent blockages that require manual removal
• White list - IPs allowed will never be blocked
• Automatic interlocks - The system automatically blocks IPs when they exceed the spam threshold

• Single IPv4 addresses: 192.168.1.100
• Single IPv6 addresses: 2001:db8::1
• CIDR IPv4 ranges: 192.168.1.0/24
• CIDR IPv6 ranges: 2001:db8::/32

1. Enable "Automatically block IPs after multiple spam attempts"
2. Set the lockout threshold (default is 5 attempts in 24 hours)
3. Select the type of automatic lock (temporary/permanent)
4. The system will automatically block IPs when the threshold is exceeded

# Example list of IP blockers
192.168.1.100
10.0.0.0/8
2001:db8::1
suspicious-domain.com (unsupported - IP only)

9. log management

• Form type - filtering by protected form type
• Reason for blocking - filtering by reason of spam detection
• IP address - searching for the activity of a specific IP
• Date range - restriction to a specific period
• Pagination - review of large sets of logs (50 records per page)

• Automatic cleaning - By default, logs older than 30 days are deleted
• Log limit - A maximum of 5000 logs in the database (the oldest are deleted)
• Manual cleaning - ability to clear all logs
• Data export - all data available through the administration panel

10. statistics and reports

• Fixed locks - number of permanently blocked IP addresses
• Active time locks - Number of IPs with active time blocks
• Allowed IPs - number of addresses on the white list
• Expired blockades - number of time blocks that have expired

• Ranking of IP addresses by number of spam attempts in the last 30 days
• Last spam attempt for each IP
• Current IP status (active/ temporarily blocked/permanently blocked)
• Ability to quickly add IPs to blockers or whitelists

• Breakdown of spam attempts by form type (comments, registration, contact)
• Most common reasons for blockages (honeypot, time_check, content_filter)
• Daily trend - spam activity in the last 7 days
• Comparison with previous periods

• List of 10 latest blockchain with expiration time
• Lockout type (temporary/permanent) and reason
• Remaining time for time locks
• Direct links to blockchain management

11. automated tasks (CRON)

• Removal of expired IP time-locks
• Enforcing the limit of 5,000 logs in the database
• Deleting logs older than 90 days
• Fast operations without affecting performance

• Advanced log cleaning with type prioritization
• Limiting logs per IP (max 100 per IP)
• Optimization of database structures
• Generating a cleaning report

// The plugin automatically adds a custom "weekly" interval
add_filter('cron_schedules', 'cc_anti_spam_add_weekly_cron_schedule');
// Schedule: 604800 seconds = 7 days
$schedules['weekly'] = array(
'interval' => 604800,
'display' => 'Weekly'
);

12. advanced settings

• Check IP only at POST - Restricts IP checking to shipping forms
• Skip logged in users - disables anti-spam checking for those logged in
• IP check cache - stores the results of IP checks in cache memory (30-300 seconds)

1. Enable "IP Check Cache" for better performance
2. Set the cache time (default is 60 seconds)
3. Cache reduces database load on multiple requests from the same IP
4. Cache is automatically invalidated when IP status changes

• IP detection by proxy - HTTP_CF_CONNECTING_IP, HTTP_X_FORWARDED_FOR header support.
• Validation of IP formats - validation of IPv4, IPv6 and CIDR ranges
• Private IP filtering - exclusion of private ranges from locks

13 Troubleshooting

1. Check if the plug-in has an active license under the "License" tab
2. Make sure protection is enabled in general settings
3. Check whether specific form types are enabled in the protection of the
4. Verify that the protection level is not set too low
5. Check logs for blocking information
6. Make sure the spammer's IP is not whitelisted

1. Reduce the protection level from "High" to "Medium" or "Low"
2. Increase minimum times for completing forms
3. Check the list of banned words - remove terms that are too general
4. Add IPs of valid users to the whitelist
5. Disable user field validation if it blocks real accounts
6. Review logs to identify causes of blockages

1. Enable IP check cache (60 seconds)
2. Enable "Check IP only at POST"
3. Enable "Skip logged-in users"
4. Reduce log retention time to 7-14 days
5. Increase the frequency of CRON cleaning tasks
6. Check PHP limits (memory_limit, max_execution_time)

1. Check if WordPress CRON is enabled
2. Verify server settings - whether CRON can perform tasks
3. Check PHP error logs for problems
4. Make sure WP_CRON is not disabled in wp-config.php
5. Consider using the actual system CRON instead of WP_CRON

1. Make sure Contact Form 7 or Gravity Forms is active
2. Check if protection for a specific plug-in is enabled
3. Clear plugin and browser cache
4. Check browser error consoles for JavaScript conflicts
5. Test with other plugins disabled for conflict detection

14 FAQS.