# IP Masking Typically, when connecting to a server, the server console would print out your IP address as you connect to it. For example, let's say the user **md5nake**'s IP is 127.0.0.1. Then the server console would output: ``` [16:14:12 INFO]: UUID of player md5nake is 12ff72a5-13a7-4d42-a41f-999466d64097 [16:14:12 INFO]: md5nake joined the game [16:14:12 INFO]: md5nake[/127.0.0.1:44290] logged in with entity id 77 at ([world]7.5, 111.0, -5.5) ``` As knowing a player's IP address allows for DDoS attacks, as well as knowing one's approximate (city/region-level) location, MineKeep employs a hashing algorithm when forwarding player IPs to user servers. This preserves the identity aspect of an IP (e.g allowing alt detectors and /ban-ip to function), whilst protecting the privacy of the player. Here's an example of a masked/hashed IP: ``` [16:14:12 INFO]: UUID of player md5nake is 12ff72a5-13a7-4d42-a41f-999466d64097 [16:14:12 INFO]: md5nake joined the game [16:14:12 INFO]: md5nake[/123.123.123.123:0] logged in with entity id 77 at ([world]7.5, 111.0, -5.5) ``` In summary: Player IP addresses are not forwarded to user servers. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.minekeep.net/player-protection/ip-masking.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.