Welcome to RFC 5735!

May I direct your attention to the portion thereof concerning the loopback address:

You'll notice that nowhere in that block is the word "MUST" or "SHOULD".

This has had consequences.

On MacOS, loopback is defined as 127.0.0.1, period.

On Windows, loopback is defined as 127.0.0.1/8, so you can ping 127.0.0.1 thru 127.255.255.254 as per usual /8 network allocations.

Linux is....different. Linux has opted to include 127.0.0.0 as a pingable address for loopback.

Yes.

.0

WSL 2 on Windows implements as per linux, meaning that a windows box will either allow or refuse a ping to 127.0.0.0 depending on which kernel you put it thru.

@munin but not 127.255.255.255:

$ ping 127.255.255.255
ping: Do you want to ping broadcast? Then -b. If not, check your local firewall rules
$ ping -b 127.255.255.255
WARNING: pinging broadcast address
PING 127.255.255.255 (127.255.255.255) 56(84) bytes of data.
^C
--- 127.255.255.255 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2055ms

@tiwe

yeah .255 is a reserved address for broadcast, and that one's in RFC 922 - which predates 2119, lol, so MUST and SHALL and such don't appear in it

@munin systemd-resolved (ab)uses this by listening on 127.0.0.53%lo:domain