> For the complete documentation index, see [llms.txt](https://dexcore.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexcore.gitbook.io/guide/dexcore-guide-fr/setup/best-practices/proxies.md).

# Proxies

{% hint style="info" %}
**What is a proxy?** A proxy is a middleman server that connects to the internet on your behalf. The bot uses proxies so that Outlook doesn't see all your accounts coming from the same location.
{% endhint %}

{% hint style="danger" %}
**Dead proxies cause silent stops.** If the bot stops without showing any error message, your proxies are likely dead. Replace them in `proxy.txt` and restart the task.

This can happen on any function — Set Rule, Check, and others.
{% endhint %}

***

## Which Proxies to Use

We recommend using only **ISP proxies** (Internet Service Provider proxies). They give the best performance and speed.

{% hint style="warning" %}
Residential proxies cause account locks with Outlook. Stick to ISP proxies.
{% endhint %}

***

## Which Country?

* If you **don't know** where your accounts were created → use **USA proxies**
* If you **know** the country → use proxies from **the same country** where the accounts were created

***

## Proxy-to-Account Ratio

{% hint style="info" %}
The bot can handle a **1:60 ratio** — meaning one proxy for up to **60 accounts**.

**Example:** If you have 600 accounts and 10 ISP proxies, you can safely run **5–7 threads**. Always keep a few threads in reserve to avoid the "Too many requests" error.
{% endhint %}

If you have a limited number of proxies, simply reduce the number of **threads** (the number of accounts the bot processes at the same time).

***

## Quick Reference

| Proxies | Accounts | Recommended Threads |
| ------- | -------- | ------------------- |
| 10      | 600      | 5–7                 |
| 50      | 3,000    | 20–30               |
| 100     | 6,000    | 30–40               |

{% hint style="warning" %}
These are guidelines, not exact rules. If you see "Too many requests" errors, reduce threads.
{% endhint %}

***

## 📧 Domain Throughput Limits

When DexCore sends OTPs to recovery emails, your catch-all domain receives a large number of incoming messages. Too many threads on a single domain causes the domain to get throttled — the bot will fail to read OTP codes even though they arrive in your inbox.

**Recommended limits:**

| Domains | Max Threads |
| ------- | ----------- |
| 1       | 5           |
| 3       | 15          |
| 6       | 30          |

{% hint style="warning" %}
**If OTP codes are visible in your inbox but the bot doesn't read them** — reduce your thread count or add more domains to your config.
{% endhint %}