# Account Checks

Guardian can screen new members before they even reach the verification step, blocking common bot patterns at the door.

{% columns %}
{% column valign="middle" %}
Pretty sure you've seen this before...

Bots joining groups with contract addresses in their display names, in effect mass-spamming scrapers scanning for new tokens. It's irritating, and it can affect traders scanning for legitimate tokens.

{% endcolumn %}

{% column %}

<div align="left"><figure><img src="/files/c33921ad14313339304f6d8c7b76b1cc05dad6fb" alt="Bots join groups with Contract addresses in their names to trigger scans"><figcaption><p>Bots joining group</p></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

Enabling **0x Address Check** will solve the problem.

Enabling this check blocks any account using an Ethereum-style 0x address as their display name from passing verification.

<div align="left"><figure><img src="/files/cc26d95e149fc85a6e1424abdea1952f25c33a0c" alt="This appears when a bot is prevented from joining"><figcaption><p>Restricted due to CA in name</p></figcaption></figure></div>

Similarly, **Link Check** blocks accounts whose display names contain URLs or website-like text.

Both checks can be enabled in your Guardian settings.

<div align="left"><figure><img src="/files/cdaf33746bee47180381929b7482bf70b063162e" alt="Guardian also filters out links in names"><figcaption><p>Restricted due to links in name</p></figcaption></figure></div>


---

# 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.tokenscan.app/guardian/account-checks.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.