> For the complete documentation index, see [llms.txt](https://docs.stoik.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stoik.io/prevention-tools/external-scan/false-positive-assets.md).

# Excluding false positive assets

In rare cases, a domain name, subdomain, IP address or service scanned by the External Scan is not part of your infrastructure. You can then remove or exclude it.

{% hint style="info" %}
Not directly managing a domain name or IP address linked to your infrastructure does not mean it should be removed from the scan. If a vulnerability is detected on a service managed by a third-party provider, it can still impact your IT system: contact the provider to resolve it.
{% endhint %}

## Prerequisites

* The `View and edit prevention tools` right, set in your Stoïk Protect settings.

## Why an asset is in your scope

The scan starts from the domains you entered, then automatically adds what is publicly linked to them:

* subdomains of your domains
* domains that redirect to one of your domains
* IP addresses your domains point to
* mail servers listed in your email configuration (SPF record)

If an asset no longer belongs to you, the cleanest fix is at the source: remove the redirect, the DNS record or the SPF entry. The asset drops out of scope after the next scan. Otherwise, exclude it as described below.

## Removing a domain name or IP address

From the `External Scan` > `Settings` page, you can directly access and remove scanned domain names and IP addresses.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FEOb71TPY7vLuqcHr2RrO%2FScreenshot%202025-12-30%20at%2017.35.16.png?alt=media&amp;token=f31b6491-619e-4619-93ce-c352a9bc8005" alt=""><figcaption></figcaption></figure>

## Excluding an asset

From the `External Scan` > `Assets` page, click the relevant resource.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FZq9xTAaSJkOyxFTibJA7%2FScreenshot%202025-12-30%20at%2017.34.27.png?alt=media&amp;token=95f96a0b-4dcd-4847-9c9f-6611c0c40d5b" alt=""><figcaption></figcaption></figure>

Select the reason for the exclusion, then click `Exclude`. We analyze your request within 48 business hours. Once approved, the asset is removed from the results during the next scan.

<figure><img src="https://2582414397-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaDGGQ49Oui29Ft0kJjSm%2Fuploads%2FmF9m1mUd9wdIII0rdj37%2FScreenshot%202025-12-30%20at%2017.36.39.png?alt=media&amp;token=3468c87a-460d-4389-ad62-558a509b0bf5" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If a scan is in progress, the `Exclude` button is disabled. Wait for the scan to complete before you submit an exclusion request.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stoik.io/prevention-tools/external-scan/false-positive-assets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
