# Scan a user

## Scan a user

To scan a user, you just need to run the command `/scan` and waiting, as in the example below, that the bot search the user.

<figure><img src="/files/WsQdFbTR0vvUGdJ3Djn5" alt=""><figcaption><p>Example of the command <code>/scan</code> if the user is blacklisted</p></figcaption></figure>

If the user is not blacklisted, you will receive this message.

<figure><img src="/files/ttaKpJ3g0K4DlWjYkdVO" alt=""><figcaption><p>Example of the command <code>/scan</code> if the user is not blacklisted</p></figcaption></figure>

## The data of the scan

There is some important data when you scan a blacklisted user.

1. **Tags** : these are the categories that the examiners gave to the report; they are important in determining user toxicity (like `Scamming`, `Doxing`, `DDoS` etc...).
2. **Author** : it's the author report, which makes it possible to establish the level of confidence that can be placed in the report.
3. **Date** : it's the date approval report,  you can draw a conclusion about how long the report lasts and what change can be accomplished.

{% hint style="warning" %}
You are **free** to **trust** us or not on the **report** ! This will **not impact** your server in any way unless you **run** commands for it.
{% 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.protectlist.xyz/blacklist-module/scan-a-user.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.