Website Security Checklist: 30 Checks for 2026
Whether you run a marketing site, a web shop or a SaaS app, these checks cover the issues attackers exploit most often. Work through them once, then automate what you can.
HTTPS and transport
- HTTPS on every page and subdomain, with HTTP redirecting to HTTPS.
- TLS 1.2 and 1.3 only, with modern ciphers.
- Certificates renewing automatically, with expiry monitoring.
- HSTS enabled.
Security headers
- Content Security Policy, starting in report-only mode.
X-Content-Type-Options: nosniff.- Framing protection with
X-Frame-Optionsorframe-ancestors. Referrer-Policy: strict-origin-when-cross-origin.
Authentication
- MFA available for users and required for admins.
- Rate limiting on login, signup and password reset.
- Uniform error messages that do not reveal whether accounts exist.
- Password reset tokens that are random, short-lived and single-use.
- Secure session cookies with
HttpOnly,SecureandSameSite.
Access control
- Every server endpoint checks permissions, not just the UI.
- Users cannot access other users' data by changing IDs.
- Admin areas restricted by network or SSO, not exposed openly.
Input and output
- Parameterised database queries everywhere.
- User content escaped or sanitised before rendering.
- Forms protected against CSRF.
- Server-side validation on every input.
Files and exposure
- No
.env,.git, backup or debug files accessible publicly. - Directory listing disabled.
- Uploads stored outside the web root, validated and served safely.
Software and dependencies
- CMS, plugins, themes and frameworks up to date.
- Unused plugins and software removed.
- Dependency vulnerability alerts enabled.
DNS and email
- No dangling DNS records pointing to deleted services.
- SPF, DKIM and DMARC configured.
Monitoring and recovery
- Logs for logins, admin actions and errors, with alerts on anomalies.
- Backups taken automatically and restores tested.
Prioritising
If you can only do five things today:
| Priority | Check |
|---|---|
| 1 | Update CMS, plugins and frameworks |
| 2 | MFA on all admin accounts |
| 3 | Confirm no .env or .git exposure |
| 4 | Check access control with two accounts |
| 5 | Verify backups restore |
Automate the checklist
Many of these checks can be automated and run continuously, across every subdomain, not just your homepage. SecurityInfinity tests headers, TLS, exposed files, outdated software, authentication weaknesses and access control, and gives a fix for each finding. Start free.
Frequently asked questions
How often should I check website security?
Continuously for automated checks, and after any significant change, such as a redesign, new plugin or new feature.
Do small websites get attacked?
Yes. Most attacks are automated and opportunistic, scanning the entire internet for known weaknesses regardless of company size.
Is a website firewall enough?
A WAF adds protection but does not fix vulnerable software or broken access control. Use it alongside this checklist.