Skip to content

vulnetix surface

Check from inside your own network that the routes, operations and hosts registered on your attack surface still answer, and report what responded.

Updated 04 Nov 2026Markdown

vulnetix surface liveness checks that the routes and hosts on your organisation’s attack surface still answer. It runs on your infrastructure, so it can reach internal hosts that Vulnesis’s own checker cannot.

vulnetix surface liveness [flags]

It reads the targets from your attack surface, sends one safe request to each, and reports what answered. The verdicts are worked out by the platform; the command only observes.

Flags

Flag Type Default Description
--repo string Check only the targets of one repository, as owner/name
--scheme string https Scheme used to reach each host

What each request is

Target method Request sent
GET, HEAD The same method
Any method that is not idempotent, such as POST OPTIONS

Every request carries no credentials and no body, and redirects are not followed, so the result is what the endpoint itself answered. A request that cannot connect is reported as status 0.

Requirements

A signed-in organisation. Community credentials are refused. See Authentication.

Examples

# Check every registered target
vulnetix surface liveness

# One repository's routes, over plain HTTP inside a test network
vulnetix surface liveness --repo acme/payments --scheme http
esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.