Bearded Zo Co

Blog · Vulnerabilities

What a free website vulnerability scan checks, and what it can’t

Most small business owners have never seen their website the way an attacker sees it. A passive vulnerability scan is the quickest way to get that view, without touching anything on your site. Here is what one actually looks at, in plain English.

By Alonzo Miller (Bearded ZO) ·

First, what “passive” means

A passive scan only looks at what your website already shows to anyone who visits it: the pages, the code your server sends back, your protection settings and your public DNS records. It does not log in, guess passwords, submit forms or try to break anything. That is why it is safe to run on a live site that customers are using, and why we can do it for free with your permission.

What the scan looks at

Every site is different, but a good passive scan covers the same core areas.

1. Your HTTPS and certificate

Is the padlock there on every page, is the certificate current and issued for the right name, and does the plain http:// address send visitors to the secure version? An expired or mismatched certificate is one of the fastest ways to lose a customer’s trust, because browsers show a full-page warning.

2. Browser protection headers

These are short instructions your server sends with every page, telling the browser how to protect visitors. The scan checks for the important ones, such as HSTS (always use HTTPS), a content policy, or CSP (which scripts are allowed to run), protection against your site being loaded inside someone else’s page, and safe referrer and permission settings. Missing headers don’t mean you have been hacked. They mean an easy layer of protection is switched off.

3. Software that shows its age

Many sites announce which content management system, plugins, themes or JavaScript libraries they run, sometimes with the exact version number. If a version is old and has published vulnerabilities, attackers can find you with the same automated tools we use. The scan flags what it can see, so you know what to update first.

4. Files and pages that shouldn’t be public

Backup files, old test pages, exposed admin logins, directory listings and leftover configuration files are common on small business sites, usually because someone was trying to be careful during a redesign. The scan checks for the well-known ones.

5. Email spoofing protection

Your domain’s SPF, DKIM and DMARC records decide whether someone else can send email that looks like it came from you. This is not strictly part of your website, but it is the same domain, and invoice fraud using a business’s own name is one of the most common and expensive attacks on small companies. The scan reads these public records and tells you whether they are set to actually block fakes.

6. Cookies, forms and mixed content

The scan checks whether cookies are marked secure, whether forms send over HTTPS, and whether secure pages pull in anything over plain HTTP, which browsers may block or flag.

What the results mean

A raw scanner report can be hundreds of lines of jargon, and much of it doesn’t matter for a small business. That is the part we do by hand. We check each finding, drop the noise, and rank what is left by what actually puts your business at risk: the two or three things worth fixing this week, then the rest. Every finding comes with what it means and how to fix it, written for an owner, not an IT department.

What a passive scan can’t tell you

Being honest about limits matters as much as the findings:

  • It doesn’t test behind your login. Customer portals, booking systems and admin areas need permission and hands-on testing.
  • It doesn’t try to break in. Finding out whether a weakness can actually be exploited is the job of a penetration test, done by a person with written authorization.
  • It isn’t a guarantee. A clean scan means nothing obvious is showing from the outside. It doesn’t mean nothing is wrong inside.

Think of the scan as a walk around the outside of the building: you will spot the unlocked windows, but you won’t know what is inside the safe.

How often should you scan?

At least once a year, and again after any redesign, new plugin, new hosting provider or new payment page. Those are the moments when settings quietly change. If your site takes payments, bookings or logins, ongoing monitoring is worth more than an occasional check.

// next step

See what your own site is showing

Our free scan is passive: it looks at what anyone on the internet can already see, and touches nothing on your site. You get a plain-English report ranked by what actually puts your business at risk.