Author: Leon Wimmenhoeve
Locked out after renaming the admin username
When attacking WordPress websites, guessing usernames and passwords is still a commonly used method to gain access to a WordPress back-end. It goes without saying, that using easy to guess passwords like ‘12345’ or ‘Welcome2022’ will make it really easy for attackers to login to your administrator account. The same goes for usernames; using easy to guess usernames like ‘Admin’ will make it too easy for attackers. This is why Really Simple SSL allows you to prevent usage of the
Really Simple SSL per Page and Social no longer supported
Really Simple SSL Per Page and Really Simple Social, bot Premium add-ons for Really Simple SSL are no longer supported after updating to Really Simple SSL 6.0 and, or Really Simple SSL Pro 6.0 our upcoming major release. The plugins will still work, but not in conjunction with our main plugins or future WordPress or PHP updates. The plugins will no longer receive any updates and are deprecated as of October 1st 2022. We recommend all users to update to
Meet Really Simple SSL 6
Meet Really Simple SSL Our major release Really Simple SSL 7 is coming soon. Pricing Really Simple SSL 6 is coming! Join our Beta Release Program. Learn more 5+ Million Happy Users Awesome Support Easy Configuration for Complex Features By WordPress & Security Experts Really Simple SSL 6 5/5 out 7000+ reviews 5/5 Hardening Advanced WordPress tweaks Fortify your website Always in the background Keep WordPress fortified and safe by tackling its weaknesses. Hardening features are available in Really
About the Security Scan
In the last five years, Really Simple SSL has positioned itself as one of the leading authorities on Security Headers. We gave talks about the importance of Security Headers on WordCamp Europe, and have always aspired to give everyone in the (WordPress) ecosystem an easy way to configure Security Headers as it’s a fundamental part of securing the web for everyone. We have relied on securityheaders.com for a while to quickly access a list of available Security Headers on any given
How to set Security Headers on Apache and NGINX
Below we will discuss the challenges and solutions of setting security headers in a WordPress environment. Methods for setting http security headers There are different ways to set security headers on both Apache and Nginx. Usually, security headers on Apache are set in the .htaccess file in the root of your WordPress installation, for Nginx servers they are usually set in the nginx.conf file. Some servers combine Nginx and Apache so they can be set in either of those files.