CaptchaCore icon
Actively maintained Tested with WP 7.1 #51 in bot protection

CaptchaCore

Bot protection without tracking, cookies or image puzzles. Proof of work and behavioural analysis, processed on servers in Germany.

Active installs<10New
Downloads Β· 30d96β–Ό -68.9% vs prev. 30d
Ratingβ€”0 reviews
Health score60/100Fair
All-time downloads458Since Sep 2026
Support resolvedβ€”No recent threads
RequiresWP 6.0PHP 8.1+
Downloads Β· 7d13β–Ό -35% week over week
Our verdict

Use with caution

CaptchaCore works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.

  • Tested with the latest WordPress (7.1)
  • Small user base (<10 active installs)
  • Very few reviews so far
  • Needs PHP 8.1 or newer

How does it stack up?

Side-by-side on installs, updates, ratings & support

Daily downloads

102030Sep 17Oct 17Nov 17
Yesterday1
Daily average (1y)7
Peak day41Oct 1, 2026
Last 12 months459

Download spikes usually follow a new release β€” each site that auto-updates counts as a download.

Rankings

Where CaptchaCore stands today

WordPress.org search rankings

Live position in the plugin search, top 100
KeywordPositionCompeting pluginsCategory
bot protection >100 1,505 Best bot protection plugins β†’
captcha >100 1,626 Best captcha plugins β†’
GDPR >100 4,139 Best GDPR plugins β†’
security >100 10,000 Best security plugins β†’
spam >100 4,246 Best spam plugins β†’

About CaptchaCore

From the official readme Β· v2.6.5

Description

CaptchaCore protects WordPress forms against bots and spam without showing image puzzles and without tracking your visitors.

Instead of asking people to identify traffic lights, the browser solves a small cryptographic computation in the background while the plugin observes whether the interaction looks human. A single visitor never notices it. A bot farm sending millions of requests pays for every single one.

  • Proof of work (SHA-256) in a web worker, so the interface never blocks
  • Behavioural and environment signals: mouse movement, typing rhythm, scrolling, canvas timing, WebGL renderer
  • No cookies and no image puzzles in normal operation
  • Processing on our own servers in Germany, no transfer to the United States
  • Widget of 16 KB gzip with no external dependencies
  • Keyboard operable and marked up for screen readers

Integrations

WordPress core:

  • Login form (also custom login forms rendered by wp_login_form)
  • Registration
  • Lost password
  • Comments and WooCommerce product reviews

WooCommerce (each one switchable):

  • Login and registration on the My Account page
  • Lost password on the My Account page
  • Checkout, on the classic checkout page ([woocommerce_checkout] shortcode). The block-based checkout is not supported yet; the settings page tells you if your shop uses it.

Form builders and page builders:

  • Formidable Forms β€” a native field type you drag into any form
  • Elementor β€” a CaptchaCore widget for the page builder and a field for Elementor Pro forms
  • Contact Form 7 β€” the form tag [captchacore], or added automatically in front of the submit button of every form

Beyond WordPress, the same service has packages for Laravel and Symfony, a plugin for WoltLab Suite and a REST API for everything else: https://captchacore.eu/docs/integrationen

The plugin ships with English source strings and is ready for translation on translate.wordpress.org.

CaptchaCore is a hosted service. The plugin does nothing until you enter your own credentials, which you can create free of charge for private websites.

External services

This plugin connects your site to CaptchaCore, a service operated by SpeedIT Solutions UG (haftungsbeschrΓ€nkt), Isernhagen, Germany. Without that service the plugin cannot verify anything. It stays inactive until you enter your own credentials in the settings.

1. Form verification β€” https://api.captchacore.eu

When: every time one of the forms you protect is submitted (login, registration, comment, lost password, WooCommerce account forms and checkout, Formidable, Elementor, Contact Form 7).
What is sent: the token created by the widget, the type of the form, the IP address of the visitor, the page URL without its query string, and the visitor’s Accept-Language and Sec-Fetch-Site request headers (forwarded as X-Forwarded-Accept-Language and X-Forwarded-Sec-Fetch-Site).
Why: to decide whether the request comes from a human or from a bot.
The service never stores IP addresses in plain text: only truncated (IPv4 /24, IPv6 /48) and as a hash with a random salt that changes every 6 hours. These IP-related fields are cleared after 30 days; the remaining statistics without personal data are kept for 7 to 365 days depending on your plan.

2. Delivery of the widget script β€” https://src-eu.captchacore.eu (default) or https://src.captchacore.eu (optional, worldwide)

When: on every page that contains a protected form.
What is sent: the usual connection data of a file request, meaning the IP address and the browser identification.
Why: to deliver the JavaScript file of the widget. The default endpoint uses servers in the EU only. Enable the worldwide endpoint only if you need it.
If the file cannot be loaded from there, the plugin loads it once from https://captchacore.eu instead (same data). If you run the service yourself, enter your own address under “Widget source”; the widget is then loaded from there only.

3. Requests from the visitor’s browser β€” https://api.captchacore.eu/api/v2/challenge and /api/v2/precheck

When: on pages with a protected form, when the widget starts its check and before the form is submitted.
What is sent: the challenge request carries your public site key and the form type; the pre-check sends the widget token directly to CaptchaCore. The token contains the proof-of-work solution, condensed behaviour metrics (counters, timings and entropy values β€” no raw mouse paths, no key values, no form content), the user agent and technical environment characteristics used for bot detection (for example the webdriver flag, number of plugins and languages, screen size, number of CPU cores, whether software rendering is used). As with any request, the IP address of the visitor is visible to the service.
Why: to issue the proof-of-work task and to check the token early. The widget sends these requests without cookies and stores nothing in the browser.

4. Availability check

When: only inside the WordPress admin area, when you open the settings page β€” the plugin asks the CaptchaCore service whether your credentials work.
What is sent: your secret key for authentication. No visitor data.
Current availability of the service and past incidents: https://captchacore.eu/status

Nothing else is transmitted. The plugin sets no cookies, sends no usage statistics and reports no data about your website to us.

Terms of use: https://captchacore.eu/seite/nutzungsbedingungen
Privacy policy: https://captchacore.eu/seite/datenschutz
Data processing agreement under Art. 28 GDPR: https://captchacore.eu/seite/dsgvo

Installation

  1. Upload the plugin under Plugins > Add New
  2. Activate the plugin
  3. Open Settings > CaptchaCore
  4. Enter the service URL, the site key and the secret key

You can create an account and a key pair at https://captchacore.eu β€” free of charge for private websites.

Changelog

Security update, please install now. Closes a way around the login CAPTCHA over XML-RPC, hardens updates and script sources on multisite and checks a signature before installing updates from captchacore.eu. Elementor Pro forms protected only by the page builder widget need the CaptchaCore form field.

2.6.5

  • Security: the login CAPTCHA can no longer be skipped by adding the field woocommerce-login-nonce to an XML-RPC call or another login request. The exception for WooCommerce logins now only applies while WooCommerce itself processes its login form.
  • Security (multisite): only users allowed to update plugins can force an update check, the update source is taken from the main site (or the constant CAPTCHACORE_UPDATE_URL), and the package must come from the host of that source.
  • Security (download from captchacore.eu only): updates are signed. Before installing an update, the plugin checks the Ed25519 signature of the package against a key built into the plugin and cancels the update with a clear message if the signature is missing or does not match. A self-hosted update source can set its own key with the constant CAPTCHACORE_UPDATE_PUBLIC_KEY. The WordPress.org version is updated by WordPress.org and is not affected.
  • Security: the widget source and the service URL can only point outside captchacore.eu for users who may add unfiltered HTML (on multisite the super admin). Otherwise the previous value is kept.
  • Fix: saving the settings while WooCommerce, Formidable, Elementor or Contact Form 7 is deactivated no longer switches their protection off.
  • Fix: the local limit of 30 failed checks per IP address and minute only stops malformed tokens. Real tokens always reach the service, so junk requests from a shared IP address can no longer lock out logins or the checkout.
  • New: setting “Proxy header” with the option “X-Real-IP only” for proxies that set X-Real-IP themselves but pass X-Forwarded-For through unchanged.
  • New (multisite): with the registration protected, the signup page wp-signup.php shows the widget and checks the token.
  • Elementor: the editor note now says that Elementor Pro forms need the CaptchaCore form field; the page builder widget alone does not protect them.

2.6.4

  • Fix: with the core login protected, logins on the WooCommerce My Account and checkout pages failed every time unless the WooCommerce login was protected as well. They are now only checked when the WooCommerce login is protected.
  • Fix: login forms rendered by wp_login_form() (shortcodes, widgets, themes) now show the widget instead of rejecting every login.
  • Security: with “Behind a reverse proxy or CDN” enabled, forwarding headers are only accepted from trusted proxies: private addresses, Cloudflare and the new setting “Trusted proxies”. X-Forwarded-For is read from the right, and CF-Connecting-IP only counts when the request really comes from Cloudflare. Before, a visitor could choose the IP address reported to the risk engine.
  • Fix: the local limit of 30 checks per visitor IP now uses a fixed one-minute window and counts failed checks only, so visitors sharing an IP address are no longer locked out during normal use. The settings page warns when the site is behind Cloudflare but the proxy option is off.
  • Security: the Elementor editor preview escapes the widget label.
  • Fix: the self-updater no longer causes a fatal error when another plugin resets the update information.
  • Uninstall also removes the WooCommerce settings and the short-lived limit entries.
  • New: Contact Form 7 integration. Form tag [captchacore], or added automatically in front of the submit button (switchable). The token is checked in CF7’s spam filter; a failed check sends no mail and shows a clear message.
  • Fix: the widget of the classic WooCommerce checkout is now placed below the billing details instead of inside the payment section. WooCommerce replaces that section via AJAX on every change, which removed the widget; under attack mode the click check disappeared and “Place order” did nothing.
  • Fix: the login widget in the collapsed “Returning customer?” form on the checkout page only starts when the form is used, instead of running a second check next to the checkout.
  • Fix: the comment widget is shown in block themes (for example Twenty Twenty-Five). It now uses the comment_form_submit_field filter, which the Comments block does not override.
  • Fix: no more “translation loading triggered too early” notice (_load_textdomain_just_in_time) on sites with WooCommerce.
  • Security: new installs protect the WooCommerce login together with the WordPress login when WooCommerce is active. Existing settings are not changed, but the settings page warns when the WordPress login is protected and the WooCommerce login is not.
  • New: optional setting “Widget source” and filter captchacore_widget_src for self-hosted services. If the widget script cannot be loaded, it is loaded once from the CaptchaCore server instead (without an inline handler, so strict Content Security Policies keep working).
  • German translation: remaining messages use the formal form of address (Sie); sites set to “Deutsch (Sie)” now get the German translation as well. One missing translation added.
  • Settings: the login option explains that XML-RPC logins without an application password are rejected.

2.6.3

  • Security: the login CAPTCHA now runs after WordPress has checked the password (priority 30). Before, WordPress replaced the CAPTCHA error on wp-login.php and XML-RPC, so the check had no effect. A failed CAPTCHA now always returns the same message, whether or not the password was right.
  • Security: the lost-password CAPTCHA can no longer be skipped by adding the WooCommerce field wc_reset_password to a request to wp-login.php.
  • WooCommerce: login and checkout with account creation check the token only once per request (no false rejections).
  • Backend: comment replies by moderators and “send password reset” from the user list are not blocked any more.
  • Updates are only fetched over HTTPS.
  • Security: every protected form now requests its challenge with its own form type (login, register, password_reset, comment, checkout, elementor, formidable), so stricter profiles for single forms apply.
  • Security: a rate-limited answer (HTTP 429) from the service now blocks the request instead of letting it through. In addition, the plugin allows at most 30 CAPTCHA checks per visitor IP and minute.

2.6.2

  • German translation: formal form of address (Sie) throughout.
  • Settings: the EU-only widget endpoint is now described precisely as delivery via servers in EU member states.

2.6.1

  • Security: fail-open now applies only when the service is unreachable or overloaded (timeout, 5xx, 408, 429). A request the service rejects (4xx) is always blocked.
  • The widget script now loads only on pages that actually show a protected form. Previously, protecting comments, WooCommerce forms or using Elementor loaded it on every front-end page.

2.6.0

  • WooCommerce: captcha for login, registration and lost password on the My Account page and for the classic checkout β€” each form switchable, all off by default
  • WooCommerce product reviews are covered by the comment protection
  • Lost-password requests from the WooCommerce form are no longer rejected when only the core form is protected
  • readme: full list of integrations

Full changelog on WordPress.org β†’

For developers

Is this your plugin? Show off the numbers.

Add a live badge to your site, docs or GitHub README. It updates on its own β€” no account needed.

Active installs badge Rating badge Health score badge

Best CaptchaCore alternatives

All bot protection plugins β†’
Alternatives
Rank Plugin Active installs Rating Updated Health
1 Quttera ThreatSign – Web Malware Scanner for WordPress Quttera ThreatSign – Web Malware Scanner for WordPress WordPress multi-level security scanner detecting malware, 0-day threats, brute-force… by quttera 10K+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 3.9 (47) 3 days ago 89
2 ClickCease Click Fraud Protection ClickCease Click Fraud Protection Protect your website and ad campaigns from bots, competitors, and click fraud with… by eranfl 10K+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 3 (8) 2 weeks ago 77
3 CHEQ Essentials CHEQ Essentials Protect, analyze & block threats in real time your website from bots, click fraud, and… by eranfl 500+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… No reviews 6 months ago 36
4 Checkout Shield for WooCommerce – Stop Fake Orders, Spam Bots & Card Testing Checkout Shield for WooCommerce Stop card testing and fake orders. Blocks checkout submissions that never loaded your… by carticy 400+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 5 (5) 1 day ago 86
5 Spambargo: Anti-Spam for Forms & Comments Spambargo: Anti-Spam for Forms & Comments Block spam in Elementor, Contact Form 7, JetFormBuilder, Ninja Forms, WooCommerce and… by Aviv Digital 100+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… No reviews 1 month ago 63
6 HSArticle Login Math Verification HSArticle Login Math Verification Adds a beautiful math CAPTCHA to the WordPress login page. No API keys, no paid services —… by hsarticle 60+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 5 (1) 2 months ago 71
7 Cloud Maestro – WAF Security Suite for Cloudflare Cloud Maestro – WAF Security Suite for Cloudflare Bulk deploy powerful WAF security rules to multiple Cloudflare domains with one click… by 5 Star Plugins (Rob) 70+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 5 (4) 1 month ago 75
8 WindCodex ScraperBlock – Block AI Scrapers & Bots from WordPress & WooCommerce WindCodex ScraperBlock Block AI scrapers, price bots, and content theft from your WordPress & WooCommerce site… by WindCodex 60+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… No reviews 2 months ago 59
9 HSArticle Math CAPTCHA for Forms HSArticle Math CAPTCHA for Forms Math CAPTCHA for CF7, WPForms, and any HTML form. Zero config β€” install, add shortcode or… by hsarticle 50+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… No reviews 2 months ago 64
10 SentraIP SentraIP Block unwanted traffic by country, known bots, custom User-Agents and spam-comment IPs… by moveforwardltd 50+ β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜…β˜… 5 (1) 2 months ago 71

FAQ

CaptchaCore: quick answers

Straight answers, pulled from live WordPress.org data.

Live data from WordPress.org Β· checked Nov 18, 2026

Is CaptchaCore free?

Yes. CaptchaCore is free to download and use from the official WordPress.org plugin directory.

Is CaptchaCore safe to use in 2026?

CaptchaCore works, but test it on a staging site before relying on it in 2026. Was last updated 1 month ago, and scores 60/100 on our health check.

How many websites use CaptchaCore?

CaptchaCore is active on <10 WordPress websites and has been downloaded 458 times since it launched in September 2026. It was downloaded 96 times in the last 30 days.

Does CaptchaCore work with WordPress 7.1?

Yes. The developer has tested CaptchaCore up to WordPress 7.1.4, the latest release. It requires WordPress 6.0 or newer.

What PHP version does CaptchaCore need?

CaptchaCore requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.

When was CaptchaCore last updated?

The latest version, 2.6.5, was released on October 9, 2026 (1 month ago).

Who makes CaptchaCore?

CaptchaCore is developed and maintained by SpeedIT Solutions.

What are the best alternatives to CaptchaCore?

The most popular alternatives to CaptchaCore are Quttera ThreatSign (10K+ installs), ClickCease Click Fraud Prot… (10K+ installs) and CHEQ Essentials (500+ installs).

Powered by PageForge

Want thousands of pages that rank like these? Build them in an afternoon.

This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages β€” with schema, internal links and AI-written copy baked in.

  • CSV, Google Sheets & API data sources
  • AI content, schema & internal links per page
  • Works with Elementor, Gutenberg, Yoast & Rank Math
  • Free on WordPress.org β€” no credit card
Sarah is here to help!
Hi there! πŸ‘‹ Need help finding what you're looking for?
Sarah
Sarah
Online & Ready to Help
Hi there! πŸ‘‹ Need help finding what you're looking for?

We'll use this to continue our conversation

Just now βœ“ Verified

Join 500+ SEO Pros Scaling Their Strategy

Get exclusive programmatic SEO tactics, AI content workflows, and the latest PageForge updates delivered straight to your inbox. Stay ahead of the algorithm.

We care about your data in our privacy policy.