Owners should see the basics before they pay for a review
A security review is the right answer for a business that handles customer data, and it costs money. Before that, an owner should be able to see the basics in a few seconds: is the certificate healthy, are the security headers set, can someone send email that looks like it came from the domain.
Free scanners often return a letter grade and stop there. We wanted every finding to say how serious it is and what to change, in plain English, without the scan ever acting like an attacker.
A passive scan with a plain-English fix for every finding
The scanner checks nine areas: the HTTPS redirect chain, the certificate and its expiry, security headers, cookie flags, DNS records that stop email spoofing, signs of a subdomain takeover, error messages and file listings visible to anyone, JavaScript libraries with publicly known vulnerabilities, and the security.txt file.
Findings are weighted by severity, and low-severity items are capped, so nice-to-haves cannot sink a site that gets the important things right. Every finding comes with the change that fixes it.
The network boundary was built first. The scanner resolves an address once, checks every answer against the private and cloud-metadata ranges, then connects only to the address it checked, so it cannot be turned against internal systems. It only requests what any visitor would see, it never tries to get past a login, reports are deleted after 30 days, and any domain can opt out with one DNS record.
What a scan gives an owner
How the scanner works today. It is a first look, not a substitute for a security review or a penetration test.
What we would do next
For clients, the same checks can run on a schedule across every domain they own, with an alert when a certificate nears expiry or a header disappears, and a full security review when the findings call for one.
This is our own tool, so nothing here is a client commitment. It is where we would take the same build for a client who wants one like it.
Team on this project
The same people who scoped it built it. No handover to a delivery pod.
Related work
Questions about this project
No. It requests only what your site publishes to every visitor, never guesses at paths and never tries to get past a login. That is why it is safe to run, and also why it cannot find everything.
No. A penetration test needs written authorisation and goes much further. The scan is a first look; the cybersecurity service covers reviews and authorised testing.
Each finding carries a severity weight. Low-severity items are capped so they cannot sink an otherwise well-run site, and a passing check costs nothing.
The report, for 30 days, and never the contents of a file it flags, cookies, credentials or authorisation headers. The full notice is on the scanner's terms page.