A website security routine is easier to maintain when it is treated as a schedule rather than a one-time setup task. This checklist shows what to review weekly, monthly, and quarterly, including SSL certificate status, HTTPS redirects, user access, software updates, backups, file permissions, malware alerts, security headers, and uptime. Use it as a recurring maintenance record, especially after a plugin installation, hosting change, suspicious login, or failed backup.
Overview
Website security depends on several connected layers. Your domain and DNS settings direct visitors to the correct service, web hosting provides the server environment, the content management system and plugins process requests, and user accounts control administrative access. A weakness or configuration change in any one layer can affect the whole site.
The purpose of a website maintenance security checklist is not to guarantee that every threat can be prevented. It is to make important checks visible and repeatable. Regular reviews help you identify expired certificates, outdated software, unreliable backups, unexpected accounts, and performance or availability changes before they become larger operational problems.
Keep a simple log with the date, person responsible, result, and follow-up action for each check. Record both successful checks and unresolved issues. This is particularly useful when more than one person manages a WordPress site, hosting account, domain registration, or DNS management.
What to track
Use the following reference table as the core of your website security checklist. The exact controls available will depend on your hosting plan, CMS, plugins, registrar, and security tools.
| Area | What to check | Warning signs |
|---|---|---|
| SSL and HTTPS | Confirm the certificate is valid for the correct domain and that the site loads over HTTPS. Test the main domain, www version if used, and important forms or account pages. | Browser warnings, certificate mismatch messages, mixed-content warnings, or pages that still load over unsecured HTTP. |
| HTTPS redirects | Check that HTTP requests redirect to the intended HTTPS URL and that redirects do not create loops or send visitors to an old domain. | Duplicate HTTP and HTTPS versions, redirect chains, broken pages, or inconsistent canonical URLs. |
| Admin accounts | Review administrator and hosting-panel users. Remove former users, identify shared accounts, and confirm each person has only the access required for their role. | Unknown users, inactive accounts, shared passwords, or more administrator privileges than necessary. |
| Authentication | Use unique passwords and enable multi-factor authentication where it is available for the registrar, hosting account, CMS, email, and security tools. | Repeated failed logins, password reuse, login notifications you do not recognize, or accounts without a recovery method. |
| Updates | Review the CMS core, themes, plugins, server components, and other installed software. Apply updates through a tested process and remove software that is no longer needed. | Outdated components, abandoned plugins, update errors, or changes made without a recent backup. |
| Backups | Confirm backups are completing, stored separately from the live site where practical, and retained according to your recovery needs. Test restoration rather than checking only that a backup file exists. | Failed jobs, incomplete archives, inaccessible storage, backups stored only on the same server, or restoration steps nobody has tested. |
| File permissions | Review sensitive configuration files, upload directories, and writable folders using the permissions recommended by your hosting or CMS documentation. | Unexpected writable locations, modified core files, unfamiliar scripts, or permission changes with no documented reason. |
| Malware and security alerts | Review alerts from your host, CMS security tools, firewall, email provider, and monitoring services. Confirm that notifications reach a monitored inbox. | New files, unexpected redirects, injected links, suspicious administrator activity, or alerts that are being ignored or filtered. |
| Security headers | Review the headers configured by your hosting platform, application, or reverse proxy. Check that they support your site’s scripts, frames, forms, and other required functions. | Headers missing from important responses, browser console errors, or a security policy that breaks legitimate site features. |
| Uptime and DNS | Check uptime alerts, domain renewal details, nameservers, and critical DNS records after planned changes. Make sure the alert destination is current. | Unexpected downtime, DNS changes you did not authorize, expired domain details, or email and website records pointing to obsolete services. |
For WordPress sites, include plugins and themes in every update review. Keep a record of the site version, the update date, and any compatibility testing. If you are changing hosts or DNS, document the current records first. The guides on DNS records and connecting a domain to web hosting can help you distinguish an intended change from an unexpected one.
Cadence and checkpoints
Weekly checks
- Review uptime, malware, firewall, and failed-login alerts.
- Confirm the latest backup completed and that its storage location is accessible.
- Look for unfamiliar admin accounts, login notifications, files, redirects, or content changes.
- Open the homepage, contact forms, checkout or booking flows, and key account pages over HTTPS.
Monthly checks
- Review SSL certificate dates, domain renewal details, and HTTPS redirect behavior.
- Check CMS, plugin, theme, and hosting updates. Remove unused components after confirming they are not required.
- Review user roles, multi-factor authentication status, password recovery details, and hosting-panel access.
- Review storage, bandwidth, and resource alerts. A sudden change can indicate growth, a configuration issue, or unwanted traffic.
- Check security headers and important DNS records after any site, email, or hosting change.
Quarterly checks
- Perform a controlled backup restoration test on a staging environment or other safe location.
- Review the full recovery process: who has access, where credentials are stored, how DNS is changed, and how the site is returned to service.
- Audit all third-party integrations, API keys, form destinations, analytics accounts, and connected applications.
- Review file permissions and compare important configuration files with a known-good version where possible.
- Test the site from more than one device or network and investigate availability, certificate, or redirect differences.
Run an extra review after a website migration, domain transfer, hosting plan change, major CMS update, new plugin installation, or administrator departure. Before moving a WordPress site, document the current environment and backup status; the WordPress migration guide provides a useful planning reference.
How to interpret changes
Not every warning means the site has been compromised, but every unexpected change deserves a clear explanation. Start by comparing the timing of the change with your maintenance log. A new redirect may follow a planned domain update; a new administrator account may belong to a recently added team member; an update failure may explain a broken form. If there is no documented explanation, treat the item as unresolved.
Prioritize issues that affect control of the site or the ability to recover it. An unknown administrator, suspicious login, invalid SSL certificate, failed backup, or unexpected DNS change should be investigated before lower-impact cosmetic issues. Preserve relevant logs and avoid deleting suspicious files before you have recorded what happened or consulted your hosting provider or security specialist.
When an update causes a problem, use the documented backup and rollback process rather than making several unrelated changes at once. If a backup cannot be restored, do not count it as a reliable recovery copy. If alerts are too frequent to review, adjust thresholds and recipients so genuine events are not lost among routine notifications.
When to revisit
Use this checklist weekly, monthly, and quarterly, but revisit the article itself at least every six months. Review it sooner after a significant browser, hosting platform, CMS, authentication, or certificate-management change. Security settings and recommended workflows can evolve, so confirm that the controls in your hosting panel and WordPress installation still match the tasks recorded here.
Return to the checklist immediately when a browser displays an SSL warning, a user reports a suspicious redirect, a login alert looks unfamiliar, a backup fails, uptime falls, or a domain or DNS record changes unexpectedly. Also use it before and after a migration or launch. For launch-related checks, compare your work with the domain-to-hosting launch checklist.
To put the routine into action, create four columns in a maintenance log: check, date, result, and next action. Assign an owner for each task, set calendar reminders, and record the location of backups and recovery instructions without placing sensitive passwords in the log. A small, consistently maintained record is more useful than an extensive checklist that nobody reviews.