It has no geolocation because it's reserved for multicast traffic, i.e. sending the same stream of data to multiple recipients. There's no technical reason it couldn't be used for something else, but it would not be used in any typical or default configuration, as it's reserved for specific purpose. It's interesting to see an HTTP POST to an IP reserved for multicast...
It has no geolocation because it's reserved for multicast traffic, i.e. sending the same stream of data to multiple recipients. There's no technical reason it couldn't be used for something else, but it would not be used in any typical or default configuration, as it's reserved for specific purpose. It's interesting to see an HTTP POST to an IP reserved for multicast...