Available now
Inspect files and configuration.
Understand what they expose.
Basic+ includes all Basic checks, with deeper file and archive inspection and additional checks for database disclosures and risky settings in exposed cloud and container configuration. Human-reviewed findings explain the evidence, recommended response and inspection limits. We draw the line at exploitation.
We’re accepting a limited number of clients so every assessment receives personal review and follow-up.
Pricing in five-target blocks- 1–5 targets
- Base package
- 6–10 targets
- Base + one block
- 11–15 targets
- Base + two blocks
- 16+ targets
- Scoped quote
One target is an approved hostname or IP, not each page or API route. Target counting, scope, schedule, and fixed price are confirmed in writing before work begins.
Basic+ inspection volume and archive limits are confirmed in the quote.
Basic+ scope
Everything in Basic, with these additional checks:
- Files found during the assessmentDownload approved files within the agreed scope, such as backups, configuration files and supported archives.
- Nested archive inspectionInspect ZIP, TAR and GZIP archives inside another archive, within shared safety limits.
- Safe file inspectionInspect files in an isolated environment without running their contents.
- Passwords, keys and tokensCheck file contents and supported archive members for supported credential patterns.
- Database error disclosureIdentify database details exposed in web responses.
- Docker configurationFlag Dockerfiles that explicitly set
USER root. - Amazon S3 configurationIdentify public-access risks in exposed infrastructure files for Amazon S3.
- Kubernetes configurationIdentify privileged containers in exposed Kubernetes manifests.
Supported examples and limits
Supported patterns include AWS access-key identifiers and assigned secret-key material, Azure storage connection-string keys, GitHub tokens, contextual generic API keys, Slack webhook URLs, Stripe secret or restricted keys, JWT-shaped tokens, database URLs containing passwords, and private keys. Coverage depends on discovered files, agreed scope, retrieval and supported formats. Each match receives human review. Credentials are not used to log in or tested to see whether they work. Incomplete inspections are recorded, not treated as clean results. Coverage excludes a review of every repository, source-code review and logged-in assessment.