WebSecure
Scanning · Proof of what we checked

Get started

Scanning

Agents and API

Account

Scanning

Proof of what we checked

Server-log header, signed scan record, threat data sources and the safe / not safe verdict.

Every scan leaves a record you can check yourself: each request we made, what came back, every check we ran and what it found, all signed by us. You don't have to trust the report on our word.

Three ways to check a scan

Your own server logsEvery request carries the header X-WebSecure-Scan: s_… with the scan id, and comes from 46.225.187.204 with the user agent WebSecureScanner/1.0. Search your access logs for the id to see every request.
The report itself"What we did" at the top says when we scanned, how many requests we made and which threat data we used. "Every check we ran" at the end lists each check and its result.
The signed proofOn the scan page, Download signed proof gives a JSON file with the full record and an Ed25519 signature. Change one character and the signature no longer verifies.

What the signed record contains

Verify a proof

Download our public key once, then verify any proof file with Node.js. No account needed.

curl -sO https://scan.hoopgram.com/.well-known/websecure-signing-key.pem
node -e "const c=require('crypto'),f=require('fs');const p=JSON.parse(f.readFileSync(process.argv[1]));console.log(c.verify(null,Buffer.from(p.record),f.readFileSync('websecure-signing-key.pem','utf8'),Buffer.from(p.signature,'base64'))?'valid':'INVALID')" websecure-proof-s_XXXX.json

To check the report matches, compare report_sha256 in the record with shasum -a 256 of the report body.

Where the threat data comes from

SourceWhat we use it forHow fresh
OSV.devKnown vulnerabilities and malicious versions of npm packages (GitHub advisories, npm, OpenSSF malicious-packages).Looked up live at scan time.
CISA KEV catalogMarks bugs that attackers are exploiting right now. These go to the top of the report.Refreshed every 12 hours.
WebSecure rulesPatterns for leaked keys (Stripe, OpenAI, Anthropic, AWS, GitHub, Supabase and others) and database setups that need review.Version shown in every report.

Is my site safe?

Each report starts with one of three answers: