WordPress plugin
Loginizer-Security
Loginizer blocks an IP address after failed WordPress login attempts reach the configured retry limit. By default, three failed attempts trigger a 15-minute block; after multiple lockouts, the block lasts 24 hours. Administrators can change these values in the Brute Force options.
Loginizer blocks an IP address after failed WordPress login attempts reach the configured retry limit. By default, three failed attempts trigger a 15-minute block; after multiple lockouts, the block lasts 24 hours. Administrators can change these values in the Brute Force options.
Lockouts and IP access
The base plugin delivers failed-login logs, IP blacklists and whitelists, IP range controls, and an option to allow login only from trusted IP addresses. Administrators can show a blocked screen in place of the login page, tailor failed-login messages, and receive email notifications after successful logins or maximum lockouts. Loginizer also checks permissions on important files and folders.
- Review failed login attempts and manage blocked or trusted IP addresses.
- Automatically blacklist IP addresses when specified usernames are used.
- Change the administrator username and block new registrations from specified email domains.
- Use LinkedIn login, disable pingbacks, or disable XML-RPC.
Sign-in options in Loginizer-Security Pro
Passwordless Login sends a temporary sign-in link to the account email after the visitor enters a username or email address. Email-based two-factor authentication sends a temporary six-digit code after login details are entered. Users can also configure app-based two-factor authentication with apps such as Google Authenticator or Authy, or add a challenge question that must be answered after login.
The 2.1.3 changelog lists passkeys as a Pro capability. Pro also works with social login with Google, GitHub, Facebook, X, Discord, Twitch, LinkedIn, and Microsoft, including support for WooCommerce and Ultimate Member. Its keyless social authentication option supports Google, GitHub, X, and LinkedIn. Single Sign-on can make temporary dashboard access without sharing a username or password. Administrators can limit concurrent logins by setting an allowed device count and choosing whether to block or revoke access when that limit is reached.
CAPTCHA and route controls
Administrators can configure Google reCAPTCHA v2 or v3, Cloudflare Turnstile, or hCAPTCHA for login, comments, registration, and supported WooCommerce processes. Pro can rename the login slug from wp-login.php and change the administration path from wp-admin to a custom value. With Rename Login with Secrecy enabled, login URLs still point to wp-login.php, and visitors must enter the new slug directly in their browser. CSRF Protection includes a session string to the administration URL.
Pro can also rename XML-RPC, block IP addresses from selected countries, and help prevent unauthenticated access to common username lists and paths. Login page branding options include a logo, colors, background image, panel layout, message, title, and custom CSS.
File checks and setup
MD5 Checksum checks WordPress core files. Administrators can review the results and ignore files where appropriate. To configure Loginizer, install and activate it, then review the brute-force settings, logs, and IP rules. Choose any required sign-in checks next, followed by CAPTCHA and URL settings for the forms and routes in use. Run the core file checksum check and review any files that need attention.
Loginizer-Security Pro includes professional support through the Premium Support Ticket System. Documentation is available for Loginizer, and free users can use the community support forums.