WordPress plugin intelligence profile

Takumi Private Gate

Lock down your private WordPress site. Force login for all visitors, block REST API and XML-RPC, and lock out repeated failed login attempts.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.2.4
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.0 · PHP 7.4
Directory statusactive
Last directory update13 Sept 20261mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Takumi Private Gate version 1.2.4 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Takumi Private Gate turns a WordPress install into a fully private site: nothing is reachable without logging in first. It’s built for people running a diary, notes site, or internal tool on WordPress that should never be publicly visible or crawlable.

Unlike most “force login” or “password protect” plugins, Takumi Private Gate combines four protections in a single, dependency-free plugin:

  • Site-wide lockdown: every page, post, and feed redirects unauthenticated visitors to the standard WordPress login screen.
  • REST API blocking: unauthenticated requests to /wp-json/ receive a 401 Unauthorized response.
  • XML-RPC turned off: every XML-RPC method that requires authentication is refused, so /xmlrpc.php cannot be used to log in, post, or brute-force credentials.
  • Failed-login lockout: an IP address is locked out for a configurable amount of time after too many failed login attempts, and by default the plugin says nothing that would tell an attacker they’re locked out.

Developed and maintained by Yoshiro Moriyama, founder of Takumi Web Services, a WordPress development studio based in Toronto, Canada.

Features

  • Redirects every unauthenticated front-end request to wp-login.php.
  • Returns 401 Unauthorized for unauthenticated REST API requests.
  • Turns off XML-RPC by refusing every authenticated XML-RPC method ( xmlrpc_enabled ), which closes the login, publishing, and brute-force paths. WordPress still answers /xmlrpc.php for its own unauthenticated introspection methods such as system.listMethods; blocking the file outright is a job for the web server.
  • Locks out an IP address after a configurable number of failed login attempts (default: 5 attempts / 30 minutes).
  • Counts failed Application Password attempts (REST and XML-RPC) toward the same per-IP limit, and refuses Application Password authentication while an IP is locked out.
  • Lockout state is stored per IP address, not per username.
  • Lists every currently locked-out IP with a one-click unlock button.
  • Keeps a rolling log (most recent 1000 attempts) of login attempts with date, IP, username, and result.
  • Emails the site admin address whenever an IP gets locked out (can be turned off).
  • IP whitelist (single IPs or CIDR ranges) that bypasses the lockdown, the API blocking, and the lockout entirely.
  • Optional per-user TOTP two-factor authentication (compatible with Google Authenticator, Authy, 1Password, etc.) enrolled from each user’s own profile screen.
  • Network-activation aware: sets up per-site defaults and its login-log table on every site of a multisite network.
  • Single screen of its own in the admin sidebar.
  • Uninstalling the plugin removes its options, its login-log table, and any 2FA secrets.
WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • rest api
  • lockout
  • login
  • private
  • security
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.0 · PHP 7.4
Update activity13 Sept 20261mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

Version1.2.31.2.4
Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.