Check accounts and permissions

List the people and services that can change the site. Remove accounts that no longer need access. Use individual accounts, strong authentication and the lowest permission level that supports each person’s work.

Review the domain registrar, hosting panel, content management system, deployment tool and email accounts used for password recovery. These systems can all affect control of the website.

Review software and configuration

Record the content management system, plugins, themes, framework and server runtime. Apply supported security updates and remove components that are not required. Check whether the site has test copies or old subdomains that remain public.

Review HTTPS, redirect behaviour, security headers, exposed administration pages and the services reachable from the internet. Do not rely on a padlock icon as proof that the application is secure.

Prove that recovery works

Check when backups run, what they contain, who can access them and how long they are kept. Restore a copy in a controlled environment. Record the steps and the time needed to bring the site back.

The audit should produce an owner, a priority and a due date for each fix. If the site stores customer data or supports sales, consider a scoped website vulnerability assessment to validate technical risks beyond routine maintenance.