Login Security & 2FA
Asks for an authenticator-app code after the password at sign-in, with single-use recovery codes; shows every sign-in and failed attempt, who is locked out and lets you unlock them, and emails people and administrators about sign-ins.
Not open yet No card
Description
Asks for an authenticator-app code after the password at sign-in, with single-use recovery codes; shows every sign-in and failed attempt, who is locked out and lets you unlock them, and emails people and administrators about sign-ins.
What it does
- Login attempt log
- Brute-force lockouts: Core already locks an account after 5 wrong passwords and an address after 20, for 15 minutes; this module shows who is locked and unlocks them
- Custom login notifications: an email to the person on each sign-in, and to administrators on repeated failures
- Two-factor auth (TOTP) at sign-in: after the password, a person who has set up an authenticator app is asked for its six-digit code or a single-use recovery code; each code works once; a wrong one counts as a failed sign-in
- Two-factor set-up: authenticator app secret kept encrypted, QR code drawn on the site, ten single-use recovery codes, reset by a user manager (recorded), and a per-role 'asked to set up' rule with a dashboard notice
- Refusing someone in an asked role who has not set up yet: they are let in with a notice, because set-up happens inside the admin and a module cannot send a person to another screen there. Not built yet.
- Two-factor by email: only authenticator apps for now. Not built yet.
- Whitelist/blacklist: a module cannot allow or refuse a sign-in, and Core does not pass it the address, so a list would do nothing. Not built yet.
- Changing the lockout numbers: Core's limits are fixed. Not built yet.
- Address and browser in the attempt log: Core's record of a sign-in holds the account and the time only. Not built yet.
Stands in for
Limit Login Attempts Reloaded, Loginizer.
These are other companies' products, named only to say what job this module does. WebHD is not affiliated with them.
What comes across
What this module brings over from the plugin a site used before, and what it leaves behind. Each import ends with a report that names anything it could not carry.
- From Limit Login Attempts Reloaded
- Comes across: The email alert, turned into 'email administrators after N failed sign-ins in 15 minutes'.
- Does not: The number of retries and the lockout lengths (Core's are fixed), allowed and blocked addresses and usernames (the report counts them), and the old lockout log.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From WP 2FA
- Comes across: Which roles must use two-step sign-in, as the roles that are asked to set it up here. Each person then sets up their own authenticator app, and is asked for a code from then on.
- Does not: Each person's secret and backup codes (encrypted with a key that stays on the old site, so everyone sets up again), codes by email, grace periods, rules for named users, and roles that do not exist here.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Loginizer
- Comes across: Its lockout email, turned into 'email administrators after N failed sign-ins in 15 minutes' (its retries times the lockouts it waited for).
- Does not: Retry counts and lockout lengths (Core's are fixed), its allowed and blocked address ranges (the report counts them), the failed-attempt table, and its paid two-step sign-in.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Limit Login Attempts
- Comes across: The email alert, turned into 'email administrators after N failed sign-ins in 15 minutes'.
- Does not: The number of retries and the lockout lengths (Core's are fixed), the proxy header choice, and the lockout counters and statistics.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From WPS Limit Login
- Comes across: The email alert, turned into 'email administrators after N failed sign-ins in 15 minutes'.
- Does not: The number of retries and the lockout lengths (Core's are fixed), allowed and blocked addresses (the report counts them), and the lockout counters.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From CloudSecure WP Security
- Comes across: Its sign-in email, as 'email a person each time their account is signed in to' (left off when it went to administrators only).
- Does not: The email's own subject and wording, the lockout numbers (Core's are fixed), the renamed sign-in page, its firewall and logs, and each person's two-step set-up.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Two Factor
- Comes across: Each person's authenticator app: the key their app was given is stored here, encrypted, so they keep signing in with the same app and are asked for its code after the password. People are matched by email address.
- Does not: Recovery codes (the old site kept only scrambled copies, so each person makes new ones), codes by email, people with no account here or whose role here cannot open the admin, and anyone already set up here.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- From Google Authenticator
- Comes across: Each person's authenticator app, when it was switched on: the key is stored here, encrypted, so they keep the same app. People are matched by email address.
- Does not: Relaxed mode (codes here may be 30 seconds off, not 4 minutes), its app passwords for XML-RPC, people with no account here or whose role here cannot open the admin, and anyone already set up here.
- Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
- In place of SiteGuard WP Plugin
- Its settings are lockout numbers, a renamed sign-in page, an image CAPTCHA and alert switches; Core's lockout numbers are fixed, and its sign-in history stays with the old site. Turn on the sign-in emails here under Settings if you used its alerts.
- In place of Login Lockdown
- It keeps retry and lockout numbers, an allow list and its lockout tables. Core's lockout numbers are fixed and a module cannot allow or refuse a sign-in, so nothing it stores has a home here; this module shows who is locked out and unlocks them.
Using a plugin that is not named here? It is built for your site On The Fly. How that works
Changelog
1.1.0 November 17, 2026
Login Security & 2FA 1.1.0: the settings importer now also reads Loginizer, the original Limit Login Attempts, WPS Limit Login and CloudSecure WP Security: their lockout email becomes the administrators' alert and CloudSecure's sign-in email becomes the per-person sign-in email. Retry counts, lockout lengths and address lists cannot apply here and are reported. SiteGuard, Login Lockdown and Two Factor are listed as replaced; with Two Factor each person sets up their authenticator app again.
1.2.0 November 17, 2026
Login Security & 2FA 1.2.0: an importer for Two Factor and Google Authenticator. Each person who used an authenticator app keeps it: the key their app was given is stored here encrypted, matched by email address, and signing in asks for its code after the password. Recovery codes do not carry (the old site kept only scrambled copies), so each person makes new ones; anyone already set up here is left alone. The key never appears in the report, the activity record or the site export.
1.0.0 November 17, 2026
Login Security & 2FA: two-factor sign-in with an authenticator app and single-use recovery codes, sign-in history, a locked-out list with unlock, email alerts on sign-in and on repeated failures, and a reminder for roles asked to use it. Imports Limit Login Attempts Reloaded and WP 2FA settings.
Get Login Security & 2FA when WebHD opens
One form on the home page: your WordPress address, then your email.
No card Takes a minute No fake scan