Website Security Check: What to Test and How, for Free
An attacker doesn’t need a password to learn how your website is built. The server tells every visitor whether it forces HTTPS, which headers protect the page, and which files can be downloaded. A security check reads those same answers. You can read them too.
Start with the padlock and the redirect
Type your address with http:// at the front, without the s. A
safe site sends you on to https://. If the page stays on http,
the redirect is missing and anyone on the same network can read what
visitors send.
Then click the padlock and look at the certificate’s end date. An expired certificate shows visitors a full‑page warning. For a deeper look at the encryption settings, Qualys runs a free SSL Server Test that grades any public site.1
See who can send mail as you
Three DNS records decide whether a mail server believes a message
from your domain: SPF, DKIM and DMARC. To read two of them, run
dig +short TXT example.lv for SPF and
dig +short TXT _dmarc.example.lv for DMARC. No DMARC record
means anyone can forge your address. The full fix order is in
DMARC Check Failed.
Look for files that shouldn’t be public
Some sites leave working files in the web folder. Try your own
address followed by /.env, then /.git/config, then a backup name
like /backup.zip. A download or readable text means the file is
exposed. These files can hold passwords and the site’s whole source.
Test your own site only.
Read the headers
Open your browser’s developer tools, go to the Network tab, reload,
and click the first request. The response headers list what the
server tells the browser to enforce. Two matter first.
Strict-Transport-Security makes the browser use HTTPS on every
visit. Content-Security-Policy limits which scripts the page may
run. A missing one isn’t a break‑in. It’s a door left unlocked that
costs nothing to lock.
Cookies get the same look. A session cookie should carry the
Secure and HttpOnly flags.
Know what you can change
Here the platform decides a lot. On Wix, Shopify, Squarespace, Webflow, Mozello and Tilda you control your DNS records and your page content. The headers and the TLS settings belong to the platform, so a missing header on a Wix site isn’t yours to fix. On WordPress or a custom site you own all of it, unless a host such as Netlify or Cloudflare Pages sets that header for you.
Two items are yours on every platform. Renewing the domain, which
happens at your registrar. And a robots.txt file, which every
builder lets you edit.
Where the free scan fits
The OATS scan reads these same things in one pass. It uses only public information and changes nothing on your site. Each finding comes in plain language with what it means, and a separate card lists what your platform controls so you don’t chase a fix you can’t make. The AI readability half checks how AI assistants read your page. Prices for fixes are confirmed by email before any work starts.
FAQ
Can I check my website’s security for free?
Yes. The checks above need only a browser and a terminal, and the OATS scan runs them for you at no cost.
Does a scan change anything on my website?
No. The OATS scan is passive. It reads public information and doesn’t alter your site.
Sources and notes
-
Qualys SSL Labs, “SSL Server Test”, a free analysis of a public site’s TLS configuration. https://www.ssllabs.com/ssltest/ ↩