Where could IP 0.0.0.0 come from??

Question

Google

Google shows such strange things:



How can this be, where did 0.0.0.0 come from ??
Could this mean that someone else logged into my account?
Thank you!

Answer 1

This most likely means that there was a failure on Google, as a result of which the IP was not determined.
0.0.0.0 is an IP that denotes all interfaces on the machine, so it shouldn't be in the list, which means it's a failure.
Write to their support service, there is probably a chance that they still react to bug reports.

Answer 2

Anything happens in nature.
Somehow, the provider dynamically gave me an IP address, the last bit of which was 0. And everything worked while ...

Answer 3

most likely it is "on its own".
virtlib.odessa.net/subbook/nag-20/ipaddr.htm
There are two more reserved addresses: 0.0.0.0 and 127.0.0.0. The first one is named default route, the last one is loopback address. default route is used when routing IP packets, which we will deal with a little later.
usually 0.0.0.0 has a mask of 255.255.255.255, which tells us about "roaming" packages that were released somewhere on purpose or inadvertently and got lost, or were aimed specifically at you.
www.opennet.ru/openforum/vsluhforumID6/17380.html
Also here is a similar problem and its explanation. it boils down to the fact that under some conditions the stack of your machine begins to incorrectly identify incoming packets. when can this happen? answer yourself.
however, here's a hint
en.wikipedia.org/wiki/DHCP
DHCP Discovery
First, the client broadcasts a request over the entire physical network in order to discover available DHCP servers. It sends a DHCPDISCOVER message with 0.0.0.0 as the source IP address (because the computer does not yet have its own IP address) and the destination address as the broadcast address 255.255.255.255.
I think you were just too lazy to google. these days even a coffee grinder is emitting DHCP packets in the morning.