Browser-observable traffic
Inspect headers, routes and response context—not just static files.
These fixtures cover security headers, cookies, API descriptions, well-known metadata, stack traces, client configuration, workflows, realtime routes and other passive attack-surface signals.
Checking server mode…
Checking whether this page is running through the route-aware fixture server.
Start the runnable fixture server
From the workspace root, start the dedicated server and then open its passive page. A self-signed HTTPS endpoint is created when OpenSSL is available.
node passive/server.mjs
Default pages: http://localhost:3080/passive/ and https://localhost:3443/passive/.
Route catalogue
Passive fixture groups
— public groups backed by a larger set of exact server routes.
Loading catalogue…