payless.host
Security basics every site owner can do today
Updated Nov 22, 2026
Keep automatic backups running
A site without recent backups is one malware infection or failed update away from disappearing. Enable automatic daily or weekly backups through your hosting control panel, and test a restore once so you know the process works. Most hosts include backup tools in shared plans — DreamHost includes automated backups on its DreamPress 1 managed WordPress plan at 14.99 EUR/month — but some require manual setup. Ignoring backups means risking total data loss.
Update everything the day patches arrive
Outdated WordPress cores, plugins, and themes are how most sites get compromised. Attackers scan for known vulnerabilities and exploit them within hours of a patch being announced. Turn on automatic updates for minor releases, and run major updates manually within a day or two of release. Delaying updates leaves a public invitation to anyone scanning for that version number.
Use long, unique passwords and two-factor authentication
Short or reused passwords are broken through credential stuffing — attackers try leaked passwords from other breaches until one works. Generate a unique 16-character password for every admin account using a password manager, and enable two-factor authentication on hosting accounts, WordPress logins, and email. A compromised admin password gives an attacker full control; two-factor authentication stops that even when the password leaks.
Run HTTPS everywhere, not just on checkout pages
HTTPS encrypts traffic between browser and server, preventing interception of login credentials and session cookies. Install a free Let's Encrypt certificate through your hosting panel — every provider here offers this — and force all traffic to HTTPS in your site settings. Visitors on HTTP are vulnerable to session hijacking on public networks. Search engines also penalise sites without HTTPS.
Lock down file permissions and user roles
WordPress files should never be writable by the web server except where the CMS requires it, and admin accounts should exist only for people who configure the site. Set file permissions to 644 for files and 755 for directories, limit wp-config.php to 400, and give content editors the Editor role rather than Administrator. Overly permissive settings let an attacker who compromises one plugin rewrite core files.
Monitor login attempts and block repeat offenders
Brute-force bots try thousands of username-password combinations until one succeeds. Install a plugin that limits login attempts to five per IP address per hour, logs all failed attempts, and temporarily blocks repeat offenders. This stops automated attacks cold. Review the log weekly for patterns — a spike in failed logins from one country can indicate a targeted campaign.
Delete unused plugins, themes, and user accounts immediately
Every installed plugin is a potential entry point, even when deactivated. Attackers exploit vulnerabilities in code that hasn't been touched in years. Delete anything not actively in use, including old themes, deactivated plugins, and user accounts for people who no longer work on the site. A plugin that hasn't been updated in two years is likely unmaintained and unsafe.
Scan for malware weekly and know what normal looks like
Run a malware scan through your hosting panel or a security plugin once a week. More important than the scan itself is knowing your site well enough to spot changes — a new admin account, a file that appeared in wp-content, unusual traffic spikes. Many compromises sit undetected for months because nobody looked. InterServer includes malware scanning on its Standard Web Hosting plan; if your host does not, install Wordfence or Sucuri. Catching an infection early means cleaning one compromised file rather than rebuilding from scratch.
