Optionally bind bots to specific IP addresses through the dev portal

[ImNimboss]

For example if my IP address was 69.42.06.942 then I could optionally bind my bot to that IP address through the developer portal.

By "binding" I mean making it so that any requests with the Authorization header as the bot's token would ONLY be accepted if they were from said whitelisted IP address, otherwise they'd be rejected with a 403 - Forbidden.

This is a great way of preventing disaster from token leaks as no one else would be able to request from the token, because Discord only accepts requests for that bot from that specific IP address.

Another idea is you could make it so multiple IP addresses could be whitelisted, if this were to get implemented of course.

[Lypt0x]

Even whether it is just optionally, how should it be handled when your ip is dynamic?
I think making an allow list for that is not really the way, to handle these issues

[ImNimboss]

Well you can't really do anything about your IP being dynamic, so you'd have to change it every so often or work on a VPS with a static IP

But yes you're right about dynamic IPs being an issue that can't be solved

[advaith1]

• dupe of IP whitelisting #3220