> For the complete documentation index, see [llms.txt](https://docs.dis.tf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dis.tf/scanner-types/avatar-scanner.md).

# Avatar scanner

Using pHash to scan and match against blacklisted profile picture

## How Global/Local avatar scanner works

Munio scans profile picture(avatar) when new user join your server and when they are in your server and changes to a new profile picture. Bot will now match any profile pictures with the aforementioned conditions against the bots database of blacklisted profile pictures using similarity comparison that works like Google reverse image search. 

The blacklisted profile picture will only get added to the database if DM BOT spammers uses multiple accounts with the same profile picture. This feature will be extremely useful protecting your server against **DM SPAMMERS** that impersonate discord staff or any known dm spammers.

## Default: <mark style="color:green;">Enabled</mark>

Bot will by default auto kick users from all servers if the users profile picture match against the profile picture database.

**Default punishment type**: Kick

\
To configurate this scanner, follow these steps:

> **Step 1:** /settings\
> **Step 2:** \
> Option 1: Global Scanners\
> Option 2: Local Scanners\
> **Step 3:** Avatar Scanner


---

# 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.dis.tf/scanner-types/avatar-scanner.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.