# Checker

The Checker module verifies the status of your accounts. It connects to Telegram with each account and reports whether it is alive, frozen (restricted), banned, or dead (session expired).

![Checker settings](/files/FDw7YwCb91GR7M1yAY02)

## Settings Reference

| Setting             | Description                                                                                                                                      |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Threads**         | How many accounts to check at the same time. Checking is lightweight, so you can safely use high values like 50.                                 |
| **Account Limit**   | Maximum number of accounts to check. Set to **0** to check all selected accounts.                                                                |
| **Timeout**         | How long to wait for each account check (seconds). Default: 120. Increase if you have slow proxies.                                              |
| **Check SpamBlock** | When enabled, the checker also contacts @SpamBot to find out if the account has an active spam restriction. This adds 10-15 seconds per account. |
| **Set Passkey**     | Automatically register a FIDO2 passkey on alive accounts that do not already have one. Useful for future session recovery.                       |

{% hint style="info" %}
When you enable **Check SpamBlock**, the timeout is automatically increased to at least 60 seconds.
{% endhint %}

## How to Use

1. Go to **Checker** in the sidebar
2. Set the number of **Threads** (e.g., 50)
3. Optionally enable **Check SpamBlock** and/or **Set Passkey**
4. Select a **Proxy list** from the dropdown
5. In the **Accounts** section below, filter and select which accounts to check (or leave the selection empty to check all)
6. Click the green **Start** button

## Understanding the Results

The checker assigns one of these statuses to each account:

| Result                                 | What It Means                                                                             |
| -------------------------------------- | ----------------------------------------------------------------------------------------- |
| **ALIVE**                              | Account is working normally. Shows username, Premium status, and spam block info.         |
| **FROZEN / RESTRICTED / SCAM**         | Account is restricted by Telegram. It still exists but has limitations.                   |
| **BANNED / DEACTIVATED / DELETED**     | Account is permanently disabled. All sessions for this phone are marked as banned.        |
| **AUTH\_KEY\_DEAD / SESSION\_REVOKED** | Only this specific session is dead. The account itself may still work on another session. |
| **EMPTY\_RESPONSE**                    | Telegram returned no data. Usually temporary -- try again later.                          |

The checker also automatically detects and updates:

* **Platform correction** -- if the account was registered on a different platform than recorded
* **Account creation date** -- extracted from Telegram service messages
* **Spam block details** -- when and why the restriction was applied

{% hint style="info" %}
**Run the Checker on newly imported accounts** to fill in missing information like username, premium status, and account age.
{% endhint %}

For a step-by-step walkthrough, see [How to Check Your Accounts](/mvs-docs/guides/checker-guide.md).


---

# 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://mvs-3.gitbook.io/mvs-docs/modules/checker.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.