wpgear

Adaptive Login Form: Adjusting compromise between Comfort and Paranoia.
Conception: 
1. “Zero Trust Mode” 
Recommended for small groups of regular Users with a Static IP Address. 
Not recommended for Dynamic IP Addresses or Mobile Users.
If my current IP address is not marked as Dangerous since my last successful login, then there is no need to distrust me and force me to go through Quests to solve different types of Captchas. 
In this case, the standard “Password” field is sufficient for one attempt.
But if the Attempt is unsuccessful, then we mark the IP address as Dangerous, and then it is possible and necessary to trick me (or the one who is trying to be me) with a more thorough login procedure.
There may be multilevel options. It doesn’t matter (this will be gradually added to the functionality). We are now talking about the General Principle.
Separate statistics are generated for each IP address and the ratio “Successful number of entries” / “Total number of entries” is determined. Depending on how close this parameter is to 100%, we can talk about the need for the Toughness of the Mistrust process.
This mechanism starts before the User enters his Login.
The more Unsuccessful Login attempts occur from a given IP Address, the more thoroughly it is checked. 
Conversely, the Login procedure can be simplified as much as possible if there is no obvious reason.
<ol>
<li>“Dynamics IP Mode” 
Recommended for mobile Users with a Dynamic IP Address. 
Not recommended for Static IP Addresses.</li>
</ol>
If the User’s previous login was successful, their next authentication is performed using a simplified method. 
Simply enter the correct password. However, only one attempt is allowed. 
If the password was entered incorrectly, an additional security element is added to the login form: the “Secret Key” field.
<h4>Futured</h4>
<ul>
<li>Regardless of what kind of Authentication Error occurred, be it:</li>
<li>Invalid Username;</li>
<li>Invalid User Password;</li>
<li>Incorrectly specified additional security elements: “Secret Key” / Captcha / etc. 
This will not be indicated in the error message. There will always be only one message: “Authentication Failed”. 
Thus, we do not explicitly indicate to the potential Villain / Bot the reason for the denial of access. And the more such Reasons there are, the more complicated the Entry procedure becomes.</li>
<li>If multiple consecutive unsuccessful login attempts occur, a Restrictive Timeout may be activated for the given User.</li>
<li><a href="https://wordpress.org/plugins/new-users-monitor/" rel="ugc">Integration with “New Users Monitor”</a></li>
</ul>

Adaptive Login Action

Adaptive Login Form: Adjusting compromise between Comfort and Paranoia.

checkify

Checkify helps WordPress site owners reduce CAPTCHA friction by using privacy-first human verification.
Instead of asking visitors to solve puzzles, Checkify lets visitors complete a verification flow and return a verification result to the WordPress site. This can be used on pages, forms, or custom flows where the site owner wants to request human verification or age verification.
Checkify is designed around privacy-first verification. The WordPress site receives a verification result, not unnecessary personal identity data.
<h4>Features</h4>
<ul>
<li>CAPTCHA alternative for WordPress</li>
<li>Privacy-first human verification</li>
<li>Age verification profiles (18+, 21+, 25+)</li>
<li>Site connection using a QR code</li>
<li>Local QR rendering in the browser</li>
<li>Shortcode support using [checkify_verify]</li>
<li>Live Checkify API integration</li>
<li>No external QR code generation service</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install and activate the Checkify plugin.</li>
<li>Open the Checkify settings page in WordPress.</li>
<li>Generate a connection QR code.</li>
<li>Scan the QR code in the Checkify app to connect your WordPress site.</li>
<li>Copy your Checkify Pass ID and paste it into the plugin settings.</li>
<li>Add [checkify_verify] to the page where you want to show human verification.</li>
</ol>
The shortcode creates a verification request, renders a QR code locally in the visitor’s browser, polls for verification status, and stores a temporary local verification result for that visitor.
<h3>External services</h3>
This plugin connects to Checkify services to provide human verification.
Service used:
<ul>
<li>Checkify API: https://checkify.me</li>
<li>Checkify website: https://checkify.me</li>
</ul>
The plugin connects to Checkify when:
<ul>
<li>A site administrator creates a site connection claim.</li>
<li>A site administrator polls the status of a site connection claim.</li>
<li>A connected WordPress site creates a verification request.</li>
<li>A connected WordPress site checks the status of a verification request.</li>
<li>A connected WordPress site confirms a completed verification result.</li>
</ul>
The plugin may send the following data to Checkify services:
<ul>
<li>The WordPress site domain.</li>
<li>A Checkify site identifier.</li>
<li>A Checkify installation identifier.</li>
<li>A Checkify Pass identifier configured by the site administrator.</li>
<li>Verification request identifiers.</li>
<li>Verification status tokens.</li>
<li>Request timestamps.</li>
<li>Cryptographic signatures used to authenticate the WordPress installation.</li>
</ul>
The plugin does not use an external QR code generation service. QR codes are generated locally in the visitor’s browser using the bundled QRCode.js library.
Checkify privacy policy: https://checkify.me/privacy-policy
Checkify terms: https://checkify.me/terms_and_conditions
<h3>Third-party libraries</h3>
This plugin includes QRCode.js by davidshimjs to render QR codes locally in the browser.
Library: QRCode.js
Source: https://github.com/davidshimjs/qrcodejs
License: MIT
The QRCode.js license is included in <code>qrcode-license.txt</code>.

Checkify

Replace CAPTCHA with privacy-first human verification from Checkify.

Adaptive Login Action vs Checkify