Recon automation for authorized testing

Map first.
Test smarter.

Klyrek is a modular Python ecosystem that automates web application reconnaissance: pages, APIs, auth flows, JS endpoints, headers, misconfigurations, so you spend your time validating findings, not hunting for them.

$ pip install klyrek-cli
shop.sandbox.klyrek.com — zsh
klyrek-report/index.html generated
19endpoints
27technologies
136findings
3 critical 1 high 51 medium

Modular by design

Each capability ships as its own package. Install only what a job needs.

Pure Python

No binaries to trust, no black boxes. Extend it, or ship a plugin of your own.

Authorized use only

Declared-scope enforcement runs before a single request goes out, including every redirect hop.

Production-ready

Typed, tested, and built to run unattended in CI and internal pipelines.

The problem

Recon still eats the first day of every engagement.

Before a tester can validate a single finding, someone has to answer the boring questions: what's actually here, what does it talk to, and what changed since last time. That work is repetitive, easy to under-scope, and rarely gets faster with experience, it just gets more tedious.

  • 01Manual crawling in a browser tab, copying URLs into a spreadsheet by hand.
  • 02Re-running the same tools across engagements with no shared memory between them.
  • 03Missed JS-only routes that never render in a plain HTML crawl.
  • 04No structured output, findings live in scattered notes instead of one map.
  • 05Scope drift when a scanner wanders past what was actually authorized.
How it works

A pipeline, not a black box.

Every stage writes to the same scan result, so you can stop after any step and inspect exactly what Klyrek found.

01

Input

A URL and optional --include-host flags define the authorized scope, no separate scope file required.

02

Crawl

klyrek-crawler's breadth-first crawl builds the initial site graph within that scope.

03

Discover

api, auth, js, assets pull API surfaces, auth flows, secrets, and exposed files into the result.

04

Analyze

tech, headers fingerprint the stack and check every response against security header best practice.

05

Report

report, monitor export Markdown, JSON, or HTML, and diff it against the next scan.

Stop mapping by hand.

Install Klyrek, point it at a target you're authorized to test, and start your next engagement already knowing the terrain.