Ben Treder

Secure Login Shield helps you lock down your WordPress login page. 
By default, WordPress exposes <code>/wp-login.php</code> and <code>/wp-admin/</code>. Bots hammer these URLs every day.
This plugin gives you a private login slug (e.g. <code>/dragon-lair</code>) and hides the default login endpoint:
<ul>
<li>Defaults to <code>/wp-login.php</code> until you change it.</li>
<li>Once changed, only your custom slug works.</li>
<li>Direct access to <code>/wp-login.php</code> shows a 404 Not Found (stealth mode).</li>
<li>Logged-out visitors hitting <code>/wp-admin/</code> are redirected to the homepage.</li>
<li>Deactivate the plugin → everything reverts to normal.</li>
</ul>
Made with ❤️ by <a href="https://BenTreder.com" rel="nofollow ugc">Ben Treder</a>
<h3>Features</h3>
<ul>
<li>Private login slug (e.g. <code>/dragon-lair</code>, <code>/control-center</code>, <code>/secret-gate</code>)</li>
<li>Stealth 404 protection: Bots hitting <code>/wp-login.php</code> see “Not Found”</li>
<li>Homepage redirect: <code>/wp-admin/</code> (logged out) → homepage</li>
<li>Easy settings page under Settings → Secure Login Shield</li>
<li>Safe activation/deactivation: no core hacks, auto-reverts when disabled</li>
</ul>
<h3>Contribute & Support</h3>
<ul>
<li>Website: <a href="https://BenTreder.com" rel="nofollow ugc">BenTreder.com</a> </li>
<li>Author: <a href="https://profiles.wordpress.org/bentreder/" rel="nofollow ugc">Ben Treder</a> </li>
<li>Issues & Feature Requests: Please open a ticket on <a href="https://BenTreder.com" rel="nofollow ugc">BenTreder.com</a> </li>
<li>Like this plugin? ⭐ Leave a review and help spread the word! </li>
<li>☕ Support development: <a href="https://www.buymeacoffee.com/bentreder" rel="nofollow ugc">Buy Me a Coffee</a></li>
</ul>

Secure Login Shield

Create a private login URL and hide /wp-login.php with stealth 404s. Logged-out /wp-admin/ visits redirect to your homepage.

Marc Armengou

Security Hardener is inspired by the official WordPress hardening guide (Advanced Administration / Security / Hardening). It uses the platform’s standard functions and does not override core. Applies a prudent set of defenses:
<ul>
<li>Security headers: <code>X-Frame-Options</code>, <code>X-Content-Type-Options</code>, <code>Referrer-Policy</code>, <code>Permissions-Policy</code>, <code>COOP/CORP</code>. </li>
<li>HSTS (optional; HTTPS only). </li>
<li>Basic nonce-based CSP (optional; requires testing). </li>
<li>Disable XML-RPC and pingbacks (optional; enabled by default). </li>
<li>Hide the WordPress version in the <code><head></code>. </li>
<li>Block user enumeration via <code>/?author=</code> by returning 404. </li>
<li>Generic login errors (prevents information leakage). </li>
<li>IP-based login rate limiting with transients (configurable threshold and window). </li>
<li>Restrict the REST API to authenticated users, with a minimal allowlist for oEmbed/index.</li>
</ul>
<blockquote>
⚠️ Important: The restrict REST API option and CSP can affect integrations and plugins. Test it in staging first.
</blockquote>
Privacy: the plugin does not send data to external services or create new tables. It only uses transients to count failed login attempts.

Security Hardener

Basic hardening: secure headers, enumeration blocking, generic login errors, IP-based rate limiting, and optional restriction of the REST API.

Secure Login Shield vs Security Hardener