Targets & Scope

Deprecated Target Verification

Historical note for DNS, file, and meta-tag ownership verification.

Retired Flow

The managed APVISO flow used DNS TXT records, hosted files, meta tags, and Domain Connect to prove ownership before pentests could run. Self-hosted deployments no longer require target authorization or ownership verification inside APVISO.

Current Flow

Add the target, choose its visibility, and make sure an eligible self-hosted runner can reach it. Pentest starts are gated by license state, target visibility, and runner readiness.

Deprecated Verification Endpoints

Older DNS, file, meta-tag, and Domain Connect verification endpoints now return compatibility responses only.

Good Scoping Practice

Before pentesting, make sure the target is part of an approved test scope, the runner network can reach it, and any authenticated credentials are approved for testing use.