What happens when you ping an unreachable IP like 2.2.2.2? What does the response (or lack thereof) tell you?
Either silence (timeout) or an ICMP "Destination Unreachable" message — depending on where in the path the packet dies.
Possible outcomes:
| Result | Meaning |
|---|---|
| Timeout (no reply) | Packet got somewhere but no response came back. Could be filtered, blackholed, or host down |
| "Destination host unreachable" | Your gateway/router knows the network exists but no path to the host |
| "Destination net unreachable" | No route to that network at all |
| "Request timed out" | No router could even tell you what went wrong |
Why the ICMP error matters:
These error replies are also ICMP messages — different types from echo:
- Type 3, Code 0: Net unreachable
- Type 3, Code 1: Host unreachable
- Type 3, Code 3: Port unreachable (used by traceroute via UDP)
The diagnostic value:
A clear ICMP error tells you how far the packet got before dying. Silence tells you nothing — could be filtered anywhere.
Modern reality:
Many hosts and ISPs filter ICMP entirely — pings of public IPs often "fail" even when the host is reachable via TCP. Use tcping or nmap -sT instead when ICMP is blocked.
Tip: 2.2.2.2 is a real, routable public IP (in a block allocated to a European provider) that typically returns no echo reply — a handy "looks valid but won't answer" target. Compare with 1.1.1.1 (Cloudflare) which does reply — both are valid IPs, but reachability depends on filtering at the destination. (True documentation/example addresses are ranges like 192.0.2.0/24, not 2.2.2.2.)
Go deeper:
ICMP (Wikipedia) — the Destination Unreachable types/codes that explain how far a packet got before dying.