Somebody will eventually threaten your server. Almost always it is noise, and the useful response is neither panic nor ignoring the one part of it that is a real risk — which is your own home connection, not the server.
What is exposed and what is not
Your server's address is public by design: people need it to connect. It sits behind advanced DDoS protection, and an attack against it is a problem handled at the network level rather than by you.
Your personal home address is a different matter. It is not exposed by running a server — but it can be exposed by voice chat services, by clicking links people send you, or by anything that connects you directly to someone else.
Reading a threat
| They say | Reality |
|---|---|
| «I have your IP» | If it is the server address, so does everyone. It is public. |
| «I'll take your server down» | The network handles this. It is not your job to fix. |
| «I have your home IP» | Possible only if you connected to something of theirs. Worth taking seriously. |
| «I know where you live» | Almost always bluffing, and a matter for a platform report rather than a server setting. |
The two habits that actually matter
- Do not join voice servers or click links from people you are in conflict with
A direct connection to something they control is how a home address gets exposed. Declining is free and removes the only realistic route.
- Ban and stop replying
Threats are an attempt to get a reaction. Ban the account, save a screenshot if it crosses into something reportable, and stop responding. Continuing the conversation is the reward they were looking for.
Trying to identify someone by their connection details is the same behaviour in the other direction, and it puts you on the wrong side of both the rules and the law. Report it and let it be handled.
Screenshots with timestamps and usernames, and the platform's own report function. A threat that names a real person or place is a matter for the platform and, if it goes further, for the police — not for a server setting.