# 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="https://content.gitbook.com/content/9YqpOAGBLJOyH9qZZG0X/blobs/uBBP6Ux9AyKmmVrEouUf/image" 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="https://content.gitbook.com/content/9YqpOAGBLJOyH9qZZG0X/blobs/vHKdqXcJ2EVRsCXGXtnt/image" 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="https://content.gitbook.com/content/9YqpOAGBLJOyH9qZZG0X/blobs/tz9zA34BfyrcTElCGN6X/image" alt="Guardian also filters out links in names"><figcaption><p>Restricted due to links in name</p></figcaption></figure></div>
