ylsine

Do you have a blog that really only want ready by humans? Do think that 
<a href="http://google.com/" rel="nofollow ugc">robots</a> should never be able to read your blog, even if they ignore your robots.txt? Is privacy your number one concern? Do your friends think of you as “that total privacy nut…you know too much so.”? Then this plugin is for you. The 404er will make every public page of your blog return a <a href="http://en.wikipedia.org/wiki/HTTP_404" rel="nofollow ugc">404</a> instead of the normal <a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#2xx_Success" rel="nofollow ugc">200</a>. Yes, you could use the normal <a href="https://codex.wordpress.org/Settings_Privacy_SubPanel" rel="nofollow ugc">privacy subpanel</a>, but that would be sooo pedestrian. Step up to the real (excessive, <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5" rel="nofollow ugc">RFC abbusing</a>) 404!
Note: If you did not detect any humor in the above text or you do not know what a 404 is, then, in all caps, DO NOT INSTALL THIS PLUGIN!

The 404er

This plugin will send a 404 header for every public page on your blog.

Marc Armengou

Security Hardener applies WordPress security best practices based on the <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" rel="nofollow ugc">WordPress Advanced Administration / Security / Hardening</a> documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files.
<h4>Key Features</h4>
File Security: 
* Disable file editor in WordPress admin 
* Optionally disable all file modifications (blocks updates – use with caution)
XML-RPC Protection: 
* Disable XML-RPC completely (enabled by default) 
* Remove pingback methods when XML-RPC is enabled
Pingback Protection: 
* Disable self-pingbacks 
* Remove X-Pingback header 
* Block incoming pingbacks
User Enumeration Protection: 
* Block <code>/?author=N</code> queries (returns 404) 
* Secure REST API user endpoints (require authentication) 
* Remove users from XML sitemaps 
* Prevent canonical redirects that expose usernames 
* Optionally block author feed pages (<code>/author/username/feed/</code>)
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot — silently blocks bots before any credential check 
* IP-based rate limiting with configurable thresholds 
* Security event logging (last 100 events) 
* Automatic blocking after failed attempts
Security Headers: 
* <code>X-Frame-Options: SAMEORIGIN</code> (clickjacking protection) 
* <code>X-Content-Type-Options: nosniff</code> (MIME sniffing protection) 
* <code>Referrer-Policy: strict-origin-when-cross-origin</code> 
* <code>Permissions-Policy</code> (restricts geolocation, microphone, camera) 
* Optional HSTS (HTTP Strict Transport Security) for HTTPS sites — max-age set to 1 year
Additional Hardening: 
* Hide WordPress version (meta generator tag and asset query strings) 
* Remove obsolete wp_head items (RSD, WLW manifest, shortlink, emoji scripts) 
* Security event logging system 
* Optionally disable Application Passwords for API authentication
<blockquote>
⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins.
</blockquote>
Privacy: This plugin does not send data to external services and does not create custom database tables. It stores plugin settings and a security event log in the WordPress options table, and uses transients for temporary login attempt tracking. All data is preserved on uninstall by default and only deleted if the “Delete all data on uninstall” option is explicitly enabled.

Security Hardener

Basic hardening: secure headers, login honeypot, user enumeration blocking, generic login errors, rate limiting, and more.

The 404er vs Security Hardener