Panel protection
An extra login layer in front of the wp-login screen. It effectively limits brute-force attacks on the panel, since bots are blocked at the server level. Complements WordPress login protection.
Generate a user:password entry for an .htpasswd file that protects a directory with a password (HTTP Basic Auth). The most common uses are protecting the wp-admin panel, a staging site, or a directory before publishing. The password is hashed entirely in your browser and never leaves your device.
APR1-MD5 is Apache's native format and works everywhere. SHA-1 is sometimes needed on unusual setups. Both are computed locally.
The user:hash entry will appear here…
.htpasswd file (outside the public directory if possible), and in the .htaccess of the protected directory add:AuthType Basic
AuthName "Restricted area"
AuthUserFile /full/path/.htpasswd
Require valid-userAuthUserFile path as a full, absolute path on the server. Multiple users = multiple lines in the file.The .htpasswd file stores pairs of a username and a hashed password that the Apache server uses to protect a directory with a password in the HTTP Basic Auth mechanism. When a directory is protected, the browser asks for a login and password before it shows any content, independently of the WordPress login itself. It is a simple and reliable barrier used wherever you want to restrict access at the server level. The password in this generator is hashed only in your browser and does not leave your device.
An extra login layer in front of the wp-login screen. It effectively limits brute-force attacks on the panel, since bots are blocked at the server level. Complements WordPress login protection.
Closes a staging environment to third parties and bots before the site goes live. Better than noindex alone, because it actually blocks access.
Protection for directories with downloadable files, tool panels or work in progress. Works on any directory, not just WordPress.
Basic Auth is a supplement, not a replacement for strong passwords and updates. It works best as part of layered security.
It stores usernames and hashed passwords to protect a directory with a password (HTTP Basic Auth) on Apache. Combined with rules in .htaccess, it forces a login and password before access.
Most often to secure wp-admin with an extra login layer, protect a staging site and hide a directory before publishing. It is a barrier independent of WordPress itself.
APR1-MD5 ($apr1$) is Apache's native format, works everywhere and is recommended. SHA-1 ({SHA}) only for unusual setups without APR1 support. Both are computed locally.
Yes. The password is hashed in the browser with JavaScript and is never sent or stored. Only the ready user:hash entry is produced, to copy or download.
Each user is a separate line in the user:hash format. Generate an entry for each and place the consecutive lines one under another in the same .htpasswd file.
Tool and write-up: Marcin Szewczyk-Wilgan, WebOptimo. APR1-MD5 hashing verified for Apache compatibility. The password is computed entirely in the browser, with nothing sent to a server.
We help deploy protection for wp-admin, staging sites and sensitive directories. No obligation — a concrete proposal after a short conversation.
VAT ID: PL6391758393