Protect the connection, the application and your recovery path.
Website security works in layers. Pair the protections in your hosting package with careful account access, maintained software and a recovery plan you understand.
Recurring term savings apply at renewal · USD, before tax. Resources and included features depend on the selected package.
Start with the foundations
Three layers with different responsibilities.
01
HTTPS for the connection
An SSL certificate protects data in transit between a visitor and your website. Check that every page and asset uses HTTPS.
02
Protect the application
Keep your CMS, themes and plugins current. Remove software you no longer use and review access regularly.
03
Keep a recovery path
Understand the backups in your package and test how a restore works before you need one.
Know what your package covers—and what you manage.
Let.com’s published hosting plans describe SSL, scanning and other security features. Review the chosen package for the exact protections and backup schedule; no single service makes a website immune to compromise.
Limit who can change things
Use individual accounts, strong unique passwords and multi-factor authentication where available. Remove old access when someone leaves the project.
Keep an update routine
Review security updates for the CMS and extensions, take a backup and verify important journeys after changes.
Know how to respond
Keep support contact details and recovery information available. If something looks wrong, record the symptoms and ask for help before deleting evidence or restoring blindly.
HTTPS protects the connection. It does not fix weak passwords, vulnerable plugins, malicious uploads or missing backups. Use it as one part of the security plan.
Are backups the same on every plan?
Backup schedules and retention can differ. Check the detailed hosting comparison and confirm the restore procedure for your package.
Who should I contact if I suspect a problem?
Contact our 24/7 Texas support team with the affected site and the symptoms. Do not post passwords or private account details in public messages.