by accessnow 1 (0 reviews)

AccessNow Spam Eater

Name: AccessNow Spam Eater
Author: accessnow

Stops form spam without CAPTCHAs, using hidden fields, JavaScript and timing checks. Works with core forms, WooCommerce and popular form plugins.

AccessNow Spam Eater ranks #68,736 among WordPress.org plugins with 1+ active installations, is #7,179 of 13,811 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Oct 17, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1

v2.4.3 Current Version v2.4.3

Updated 1 week ago Last Update on 17 Oct, 2026

Refreshed 7 hours ago Last Refreshed on

#7,179 of 13,811 in E-commerce Actively maintained

View on WordPress.org

Rank

#68,736

— No change

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

103

+1 today

Support Resolved

— No change

Rating

20%

Review 1 out of 5

1 (0 reviews)

Next Milestone 10

Total Progress 10%

0+ 10+

55,799

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 9 more installs to reach 10+

Rank Changes

Current #68,736

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0

0 reviews

Overall 20%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 2.4.3
Last Updated: Oct 17, 2026
Requires WP: 6.0+
Tested Up To: 7.1
PHP Version: 7.4 or higher
Author: accessnow

Support & Rating

Rating: ★ ☆ ☆ ☆ ☆ 1
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

anti-spam contact form honeypot spam woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,762

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)

Google for WooCommerce

800K+ installs

#74

WooPayments: Integrated WooCommerce Payments

800K+ installs

#76

WooCommerce PayPal Payments

800K+ installs

#81

WooCommerce Stripe Payment Gateway

700K+ installs

#85

WooCommerce Tax (formerly WooCommerce Shipping & Tax)

500K+ installs

#116

View all Ecommerce plugins

Frequently Asked Questions

Common questions about AccessNow Spam Eater

Step-by-step help articles, with screenshots, are at https://support.accessnow.com.au/help/workspace-accessnow/accessnow-spam-eater. The plugin's own screens link to the article for each one, under the Help tab at the top right. To ask a question, use Get support on https://accessnow.com.au/projects/spam-eater/.

Yes. The hidden fields work on cached pages. If a cached page is more than about 12 hours old, the script fetches fresh tokens from your own site (admin-ajax.php) before the form is sent. Tokens last up to two days; developers can change this with the accessnow_spam_eater_token_lifetime filter.

The script loads only on pages that show a protected form. If a form is fetched after the page loads, for example a pop-up that loads its content when opened, the page had no form to begin with and the script never loaded. Turn on Load the Spam Eater script on every page under Settings → Spam Eater.

Yes. Some payment gateways place the order through their own endpoint, with their own data, instead of the checkout form. Spam Eater recognises those orders and only applies the IP block list and honeypot checks to them.

Yes. Print the hidden fields inside your form, and check the submission where you handle it: <?php echo accessnow_spam_eater_field( 'my-form' ); ?> if ( accessnow_spam_eater_is_spam() ) { /* refuse it, quoting accessnow_spam_eater_fail_code() */ } Send the form as normal form data (a regular POST, or FormData through fetch() or a REST route), not as a JSON body. Multi-step forms send the fields with every step. If your form is drawn in the browser after the page loads, call window.accessnowSpamEater.fill() once it is in the page. The functions are documented in includes/api.php, and can be switched off under Settings → Spam Eater → Custom forms.

No. All checks run on your own server.

Add the proxy IP addresses or ranges (for example 173.245.48.0/20) under Settings → Spam Eater → Trusted proxies, one per line. Spam Eater then reads the visitor's address from the X-Forwarded-For header, but only for requests that come from those proxies. The settings page shows the address your own request came from, which helps you tell whether a proxy is in use.

The error message includes a short reference code (for example SE-C2). Turn on the spam log to see why submissions are blocked, and use the Unblock button in the blocked IP list if needed. Only a filled-in honeypot field counts towards an IP block, so a visitor whose browser failed another check can simply try again.

Yes, since 2.4.0. The script adds its values to the order the Checkout block sends through WooCommerce's Store API, and the order is checked before it is created, so card-testing bots that post straight to the Store API are refused. Express payment buttons in the Checkout and Cart blocks that use WooCommerce's own checkout flow send the same values. If a gateway's express button posts its own data and is refused with SE-C2, developers can give it the lighter checks with the accessnow_spam_eater_store_api_context filter.

Yes. List words, links or /regular expressions/ under Settings → Spam Eater → Your own rules. A matching submission is refused with reference SE-K5. What people type is only checked in memory and never stored.