What my website security scanner checks
things the scanner checks from the outside
In short
Every website I hand over gets an inspection, and one of its points is security. Part of it is done by my own scanner: 15 things that can be seen from the outside, the way a browser sees them. Here is what it checks, what it does not do and what it found on tfagency.pl on 15 November.
The rule: it only looks
The scanner attacks nothing. It does not guess passwords, does not send forms and does not try to break in. It only sends ordinary requests for pages and files, the same as a browser, with a 400 millisecond pause between them, so it looks like a calm visitor rather than an attack. I run it only on my own sites or with the owner’s permission.
I run it twice: before a new version goes live and right after. Every result is PASS, WARN or FAIL. A single FAIL means the site is not ready.
What it checks
The connection
- Whether the http address redirects to https, the encrypted connection.
- HSTS: whether the site tells the browser to always use https, even when someone types the address without it.
- Mixed content: whether a page served over https loads anything over plain http.
Headers, or instructions for the browser
- CSP: a list of places the site may load scripts, images and fonts from. If someone slips in a foreign script, the browser will not run it.
- Protection against framing, so nobody can put the site inside their own and trick someone into clicking.
- nosniff: the browser does not guess a file’s type, it trusts what the server says.
- Referrer-Policy: how much of the page address is passed to other sites when someone clicks a link.
- Permissions-Policy: switching off what the site does not need, such as the camera or microphone.
- Server version: whether the site reveals what software and which version it runs on.
- Cookies: whether they have the flags that stop them from being intercepted or read by foreign scripts.
Things that should not be visible
- Exposed files: a file with database passwords, the code history, backups, the WordPress configuration file. The scanner asks for them by address and tells a real file apart from an ordinary error page.
- Directory listing: whether the server shows a list of the files in a folder.
- Unsigned foreign scripts: a script from someone else’s server should have a checksum, so the browser rejects it if somebody swaps it.
- Old jQuery, a popular library whose old versions have known holes.
- WordPress basics: whether the old xmlrpc interface is on and whether the site shows a list of user accounts.
My own sites do not run on WordPress, but the scanner also checks sites people bring to me before a rebuild. That is where these points are most useful.
The result for tfagency.pl
The scan on 15 November: 0 FAIL, 2 WARN. I know both warnings and both have a reason.
- The CSP allows scripts written into the page itself. Next.js, which the site is built with, puts such scripts into finished pages on its own. This can be tightened, but then every page has to be put together again on each visit instead of waiting ready on the server, and the site opens more slowly. On a business website I leave it, because the rest of the list still blocks scripts from foreign addresses. My rules say a shop or a client panel with a login gets the strict version.
- The hosting firewall interrupted the file checks. After a series of requests for addresses like “password file”, the firewall took the scanner for a bot and started checking it. In a way that is good news, because that is how it should work. But this point then has to be checked differently, in the code itself and in what goes onto the server.
What the scanner does not replace
From the outside you cannot see whether a form checks data on the server, whether a panel really lets in only logged-in users or whether passwords are sitting in the code. I check that separately, against a checklist, by reviewing the code. The scanner catches what is easiest to miss when a site goes live: a missing header or a file that should never have reached the server.
What you can check yourself
Type your site’s address with http:// at the start instead of https://. If the browser does not take you to https and you see a note next to the address saying the connection is not secure, that is the first thing to fix. If you would like me to look at your site in more detail, get in touch.