# Run a check against a target



Choose an isolated example target or connect a tool to a reachable application.

 

## 1. Check the available target profiles



Inspect the tool’s readiness response for its installed `targets`. The downloadable network-tool examples select an isolated demonstration target and use loopback addresses such as `127.0.0.1:8000`.

 

## 2. Try the isolated example



For [Nmap](https://www.security.run/docs/tool-nmap.html), the example selects `web-fixture` and scans two local ports. Expect one listening port and one closed port in `report.xml`. No external target is required.

 

## 3. Use your own application



Remove `target_profile`, replace the loopback address with your target’s IP or hostname, and keep the tool’s native target arguments. Your deployment must permit that route and name resolution. Only run checks against systems you are authorized to assess.

 

## If the target cannot be reached



Check the port, protocol, DNS and VPC egress policy with your operator. Changing a target argument does not grant network access. In the initial AWS installation, external egress is denied until the operator configures it.

 

A selected example target starts fresh for that invocation. It does not provide shared state for a later run. See [Limits and environments](https://www.security.run/docs/isolation.html) when a tool needs a different OS or privilege level.

## Try the isolated web target

```json
{
  "tool": "nmap",
  "timeout_seconds": 30,
  "target_profile": "web-fixture",
  "invocation": {
    "executable": "nmap",
    "args": [
      "-sT",
      "-Pn",
      "-n",
      "-p",
      "8000,8001",
      "--reason",
      "-oX",
      "report.xml",
      "127.0.0.1"
    ],
    "outputs": [
      "report.xml"
    ]
  }
}
```