# Output options

`secator` is built to be flexible in terms of output options.

***

### Console

The default `secator` output is the [Output types](/in-depth/concepts/output-types.md) `repr` function. It is supposed to be pretty and readable to quickly understand `secator`'s findings:

<div align="left"><figure><img src="/files/eFDht4syMbuRcbqAF0E2" alt=""><figcaption><p>Console output</p></figcaption></figure></div>

Unicode icons are printed before each result to distinguish each output type:

* [Output types](/in-depth/concepts/output-types.md#exploit)
* [Output types](/in-depth/concepts/output-types.md#ip)
* [Output types](/in-depth/concepts/output-types.md#port)
* [Output types](/in-depth/concepts/output-types.md#record)
* [Output types](/in-depth/concepts/output-types.md#subdomain)
* [Output types](/in-depth/concepts/output-types.md#tag)
* [Output types](/in-depth/concepts/output-types.md#url)
* [Output types](/in-depth/concepts/output-types.md#useraccount)
* [Output types](/in-depth/concepts/output-types.md#vulnerability)

When an output type has a low `confidence`, the output will be dimmed:

<div align="left" data-full-width="false"><figure><img src="/files/AOw6aQSmBQBuKYwJWuAU" alt=""><figcaption></figcaption></figure></div>

***

### JSON lines (`-json`)

You can use `-json` to output live results as JSON lines:

```bash
secator x httpx example.com -json
```

{% hint style="info" %}
JSON lines output is pipeable / streameable to other tools like `jq`.
{% endhint %}

***

### Raw (`-raw`)

You can use `-raw`to output live results in plaintext format:

```
secator x httpx example.com -raw
```

{% hint style="info" %}
Raw output is saveable to txt files or can be used for chaining tasks using UNIX pipes.
{% endhint %}

***

### Custom format (`-fmt`)

You can use `-fmt`to output live results in a format of your choice:

```bash
secator x naabu example.com -fmt '{host}:{port} -> {service_name}'
```

{% hint style="info" %}
Custom formatting is based on the [Output types](/in-depth/concepts/output-types.md) fields.
{% endhint %}

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.freelabz.com/runner-options/output-options.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.