In this article from the TripleZero iT knowledge base we explain: Protecting a website against hacks. We describe the purpose, the preparation and a clear method that you can follow step by step.
This manual is written for customers of TripleZero iT and assumes common configurations on shared hosting, reseller environments and control panels such as DirectAdmin, CyberPanel and Plesk.
What you need
- Access to the customer panel or the TripleZero iT customer panel.
- Your domain name and any login/mailbox details.
- A current browser and, where applicable, FTP/SSH access.
- Preferably a recent backup before making structural changes.
Step-by-step approach
- Log in to the appropriate panel at TripleZero iT and select the domain or account affected by the change.
- Check that you have the correct environment (production vs. test) and note the current settings.
- Perform the action that corresponds to “Protect website against hacks”. Work calmly and do not change multiple critical options at the same time.
- Save changes and test the result: website, email or DNS — depending on the subject.
- Document what you changed so you can roll back later or help support more quickly.
Deeper explanation
The topic “Protecting websites against hacks” often touches multiple layers: DNS, web server, mail server, application (for example WordPress) and account limits. Problems usually arise when one layer is changed without checking the others.
For TripleZero iT, we recommend first verifying that DNS points to the correct name servers, then checking control panel settings, and only then changing application settings (plugins, themes, .htaccess).
Security and certificate checking
Check certificate chain, renewal date and whether www and apex domain are covered. Do not force HTTPS until the certificate is valid.
Restrict admin access, use unique passwords and enable 2FA where available in panel and WordPress.
Post-completion checklist
- Does the website work over HTTP and HTTPS without certificate errors?
- Are test emails delivered and not marked as spam?
- Are limits (disk, inodes, bandwidth) still within the package limits?
- Are there no unintentional redirects, firewall blocks or PHP errors in the logs?
Common bottlenecks
- DNS propagation: changes are not immediately visible everywhere.
- Wrongly selected domain or user in a reseller environment.
- Cache (browser, CDN, LiteSpeed/OpenLiteSpeed, WordPress plugins) showing old content.
- Missing permissions on directories or wrong document root.
When to enable support
If you get stuck after these steps — for example with persistent mail errors, SSL problems, or an unreachable site — open a ticket at TripleZero iT. Please include domain name, time, error message (screenshot or exact text) and what you have already tried.
Do you still have questions after following these steps? Contact TripleZero iT support via the ticket system or email. Always mention your domain name and a clear description of the problem, so that we can help you faster.
View other articles in the knowledge base for additional explanations about hosting, email and security.