What a store security check covers
Outside and inside
Attackers look at a store from the outside first. They search for old versions, open admin pages, forgotten backup files and weak HTTPS settings, with bots that visit thousands of stores a day.
This check sees the store the same way and tells you which doors are open. What it cannot see is code already inside, such as skimmers in the database or backdoors in files. For that you need a scan on the server, like WhizzyScan.
The checklist
- HTTPS everywhere, with HTTP redirected and a valid certificate that is not about to expire.
- HSTS, so browsers never fall back to plain HTTP.
- Headers against clickjacking and MIME sniffing, and a Content Security Policy that limits where scripts load from.
- No version numbers in headers or files that tell attackers which known holes to try.
- No public .git folders, .env files, database dumps, phpinfo pages or install wizards.
- An admin that is not at the default /admin or /backend address, ideally behind an IP allow list and two-factor sign-in.
How serious is each finding?
Red items are open doors: an exposed .env or .git, an expired certificate or a platform that no longer gets patches. Fix them today. Amber items make an attack easier or a leak worse, such as missing headers or a guessable admin address. Grey items are notes.
The risk level at the top works like MageReport's: any red item means high risk, several amber items mean medium.
Keeping a store safe
Install security patches when they come out, remove extensions you do not use, review admin users and API keys, use two-factor sign-in and keep daily backups somewhere else. Scan files and the database regularly: a store can look fine from outside while a skimmer copies card details at checkout.
Our managed hosting runs malware scans every night and keeps the server patched.