Seven simple checks you can do yourself, with no hacking tools and no technical knowledge. Only on your own website.
Before you start
At work I test applications against OWASP, so I know that a good share of the most common leaks are visible to the naked eye if you know where to look. A full security test, however, is a job for a specialist.
Check only a website that belongs to you or your company. Probing the security of someone else’s site without the owner’s consent can be a crime, even if you break nothing.
1. What Google knows about your website
Type site:yourdomain.com into the search engine and go through the results. Then add filetype:pdf, then filetype:xls and filetype:doc. You are looking for documents that were not meant to be public: partner price lists, customer lists, scanned contracts, CVs from a recruitment form.
If you find something like that, delete the file from the server and request removal of the URL in Google Search Console. Simply removing the link from the page is not enough, because the file still sits at the same address.
2. Forms and what happens to them
Send a test submission through every form on the site and check three things. Whether the address starts with https on the page with the form, too. Whose inbox the message goes to, and whether that person still works for you. And whether form data piles up for years in a panel or database that more people can access than should.
3. Error messages
Add something that doesn’t exist to your site’s address, for example /test-123, and see what appears. An ordinary “not found” page is fine. If instead you see a technical message with file names, a software version or a fragment of a database query, the site is telling more about itself than it should.
4. Files left behind after the work
Contractors sometimes leave copies of the site, archives or configuration files with database passwords on the server. You don’t have to look for them yourself. Ask whoever has access to the server whether the site directory contains zip archives, database copies or directories with the history of code changes, and ask them to remove everything that isn’t needed for the site to run.
5. Security headers
The free Mozilla HTTP Observatory tool checks whether the server sends headers that make popular attacks harder, for example embedding your site inside someone else’s or injecting a foreign script. Enter the address and see the grade. A low one doesn’t mean you were hacked, but it is a good starting point for a conversation with your developer. This site checks its own headers live in the 05:15 chapter.
6. Whether your passwords leaked elsewhere
On Have I Been Pwned you can check whether your email address appeared in known leaks from other services. If it did, and the password from that service was the same as for your site’s panel or your email, change it right away and turn on two-step login.
7. Who has access
Open the list of accounts in the site’s panel, on the server and at your domain registrar. The previous agency, a former employee, an intern from two years ago: every unused account is an open door that nobody remembers. Delete them or change the passwords.
When to call a specialist
These checks catch the most common negligence, but they don’t replace a test in which someone deliberately tries to get around the protections: log in without a password, see someone else’s order, write something into the database. If the site has customer accounts, payments or stores personal data, such a test is worth doing at least once, and then after every major change.
Key takeaway
Check what Google knows about your site, what is left over from forms, what the error messages say and who has access. It is an hour of work that catches most of the common leaks.