What an IP allowlist actually does
Binance's 'restrict access to trusted IPs' field is a server-side filter. After it is set, Binance ignores any API request that does not come from the listed IPs — even if the request carries a valid API key. The key becomes useful only when paired with the right IP.
This is the single most effective defence against an API key leak. A leaked key without an IP restriction is immediately exploitable; a leaked key with the restriction is essentially inert.
How to find HalalCrypto's IP
It lives in your dashboard at Settings → API Connection → 'IP for Binance allowlist'. The dashboard always shows the current IP. We do not change it lightly — when we do, you receive an email at least 7 days before the cutover.
What if my IP changes (Dynamic ISPs)
The IP allowlist applies to the bot's outbound IP, not your home IP. Whatever your ISP does at home is irrelevant — Binance is checking the IP that placed the API request, which is always the bot's static IP.
What to do during a planned IP migration
If we ever need to move infrastructure — for example, a regional cluster relocation — the dashboard shows both the old and the new IP for a transition window. Add the new IP to the Binance allowlist before the cutover. After the cutover, the old IP can be removed.
What to do during an unplanned IP migration
Rare. If our infrastructure has to fail over to a backup IP (for example during a cloud-provider incident), the dashboard updates the displayed IP and we email every affected customer. Until you add the new IP to the Binance allowlist, the bot cannot trade — but existing positions stay safe and managed positions hold their stops via Binance-side OCO when applicable.