Login LockDown is one of the oldest brute-force defences on WordPress and the implementation is deliberately small: a failed-login table that records each rejected attempt and a lockdown table that records each active IP block. The default plugin screens show a paginated list of current lockdowns and a setting for the retry threshold, but they do not provide a queryable view across the failure history.

SleekView reads wp_loginlockdown_login_fails and wp_loginlockdown_lockdowns directly. IP, attempted username, attempt count, first-seen timestamp, lockdown-release time, and request URL become first-class columns. Filter to last 60 minutes for the on-call sweep. Sort by attempts per IP to rank the loudest attackers. Save the view and reopen the brute-force dashboard with one click.

The plugin keeps owning the retry threshold and the active-block enforcement. SleekView adds only the cross-event surface so the team can see brute-force patterns instead of one screen of current lockdowns at a time.

Login LockDown has been protecting WordPress logins for more than a decade and its data model is simple enough to be reliable on any host. The plugin's strength (a narrow, dependable feature surface) is also the source of the operational gap: failed-login history lives in wp_loginlockdown_login_fails and the plugin's own admin shows current lockdowns as a paginated list rather than the underlying log. SleekView reads both tables directly and renders the combined history as a workspace with IP, attempted username, attempt count, and release time as first-class columns.

Daily brute-force review becomes a one-click saved view. Per-client retainers get a defensible report. Junior admins get safe per-role access to triage without owning the lockdown settings.

The plugin keeps doing the small thing well. The security team gains the cross-event surface that the default admin was never designed to provide.