MyIPScan
IANA registry

Reserved and private IP addresses

Some addresses never appear on the public internet: private ranges for home and office networks, loopback for your own machine, link-local for a network with no router. What the common ones mean, then every special-purpose block IANA records.

127.0.0.1 (localhost)

Block 127.0.0.0/8

The loopback address: traffic sent to it never leaves the device, it goes straight back to the same machine. The name localhost points to it. Seeing 127.0.0.1 in a log or a browser bar means software on that same computer made or answered the request. The whole 127.0.0.0/8 block is loopback, and IPv6 has a single loopback address, ::1.

0.0.0.0

Block 0.0.0.0/32

“This host on this network”: a device uses it as its source address before it has an address of its own, for example while asking DHCP for one. It is never a valid destination. A server configured to listen on 0.0.0.0 accepts connections on all of its IPv4 addresses, and 0.0.0.0/0 in a routing table is the default route, two conventions that reuse the same numbers.

192.168.1.1 and 192.168.0.1

Block 192.168.0.0/16

Private-use addresses: they work only inside a local network and are not routed on the internet. Many home routers use 192.168.1.1 or 192.168.0.1 as their own address, which is why typing it into a browser while connected to that network opens the router’s admin page. From outside the network the address reaches nothing.

10.0.0.1

Block 10.0.0.0/8

Part of the largest private-use block, 16.7 million addresses. Some ISP-supplied routers use 10.0.0.1 as their LAN address, and offices and cloud networks use 10.x.x.x internally. Like every private address, it is reachable only from inside its own network.

172.16.0.1

Block 172.16.0.0/12

Private-use, covering 172.16.0.0 to 172.31.255.255. Corporate networks use it, and Docker places containers on 172.17.0.0/16 by default. Addresses from 172.32.0.0 upward are ordinary public addresses.

169.254.x.x

Block 169.254.0.0/16

Link-local: a device gives itself an address here when nothing answers its DHCP request, so seeing 169.254.x.x on your own computer usually means it got no address from the router. Cloud platforms also serve instance metadata at 169.254.169.254, reachable only from inside the virtual machine.

100.64.x.x to 100.127.x.x

Block 100.64.0.0/10

Shared address space for carrier-grade NAT. If your router’s WAN address falls in this range, your provider puts several customers behind one public address, which is why sites see an IP different from the one on your router. Some VPN overlays, Tailscale among them, also number their devices from this block.

255.255.255.255

Block 255.255.255.255/32

Limited broadcast: a packet sent to it reaches every device on the local network segment and is never forwarded by a router.

192.0.2.x, 198.51.100.x, 203.0.113.x and 2001:db8::

Reserved for documentation and examples, so manuals and tutorials can show addresses that will never belong to anyone. An address from these blocks in real traffic is a configuration copied from an example.

fc00::/7, fd00::/8 and fe80::

Block fc00::/7

IPv6’s private ranges. Unique-local addresses (in practice fd00::/8) play the role of 192.168.x.x inside a site; fe80:: link-local addresses exist on every IPv6 interface and work only on its own link. Neither is routed on the internet.

Every special-purpose IPv4 block

From the IANA IPv4 Special-Purpose Address Registry, read 21 Oct 2026. “Reachable from the internet” is the registry’s Globally Reachable column.

BlockNameDefined inReachable from the internet
0.0.0.0/8This networkRFC 791, Section 3.2No
0.0.0.0/32This host on this networkRFC 1122, Section 3.2.1.3No
10.0.0.0/8Private-UseRFC 1918No
100.64.0.0/10Shared Address SpaceRFC 6598No
127.0.0.0/8LoopbackRFC 1122, Section 3.2.1.3No
169.254.0.0/16Link LocalRFC 3927No
172.16.0.0/12Private-UseRFC 1918No
192.0.0.0/24IETF Protocol AssignmentsRFC 6890, Section 2.1No
192.0.0.0/29IPv4 Service Continuity PrefixRFC 7335No
192.0.0.8/32IPv4 dummy addressRFC 7600No
192.0.0.9/32Port Control Protocol AnycastRFC 7723Yes
192.0.0.10/32Traversal Using Relays around NAT AnycastRFC 8155Yes
192.0.0.170/32, 192.0.0.171/32NAT64/DNS64 DiscoveryRFC 8880, RFC 7050, Section 2.2No
192.0.2.0/24Documentation (TEST-NET-1)RFC 5737No
192.31.196.0/24AS112-v4RFC 7535Yes
192.52.193.0/24AMTRFC 7450Yes
192.88.99.0/24Deprecated (6to4 Relay Anycast)RFC 7526Retired 2015-03
192.88.99.2/326a44-relay anycast addressRFC 6751No
192.168.0.0/16Private-UseRFC 1918No
192.175.48.0/24Direct Delegation AS112 ServiceRFC 7534Yes
198.18.0.0/15BenchmarkingRFC 2544No
198.51.100.0/24Documentation (TEST-NET-2)RFC 5737No
203.0.113.0/24Documentation (TEST-NET-3)RFC 5737No
240.0.0.0/4ReservedRFC 1112, Section 4No
255.255.255.255/32Limited BroadcastRFC 8190, RFC 919, Section 7No

Every special-purpose IPv6 block

From the IANA IPv6 Special-Purpose Address Registry, read 21 Oct 2026. “Depends” marks blocks whose reachability depends on the address embedded in them, such as Teredo and 6to4.

BlockNameDefined inReachable from the internet
::1/128Loopback AddressRFC 4291No
::/128Unspecified AddressRFC 4291No
::ffff:0:0/96IPv4-mapped AddressRFC 4291No
64:ff9b::/96IPv4-IPv6 Translat.RFC 6052Yes
64:ff9b:1::/48IPv4-IPv6 Translat.RFC 8215No
100::/64Discard-Only Address BlockRFC 6666No
100:0:0:1::/64Dummy IPv6 PrefixRFC 9780No
2001::/23IETF Protocol AssignmentsRFC 2928No
2001::/32TEREDORFC 4380, RFC 8190Depends
2001:1::1/128Port Control Protocol AnycastRFC 7723Yes
2001:1::2/128Traversal Using Relays around NAT AnycastRFC 8155Yes
2001:1::3/128DNS-SD Service Registration Protocol AnycastRFC 9665Yes
2001:2::/48BenchmarkingRFC 5180, [RFC Errata 1752]No
2001:3::/32AMTRFC 7450Yes
2001:4:112::/48AS112-v6RFC 7535Yes
2001:10::/28Deprecated (previously ORCHID)RFC 4843Retired 2014-03
2001:20::/28ORCHIDv2RFC 7343Yes
2001:30::/28Drone Remote ID Protocol Entity Tags (DETs) PrefixRFC 9374Yes
2001:db8::/32DocumentationRFC 3849No
2002::/166to4RFC 3056Depends
2620:4f:8000::/48Direct Delegation AS112 ServiceRFC 7534Yes
3fff::/20DocumentationRFC 9637No
5f00::/16Segment Routing (SRv6) SIDsRFC 9602No
fc00::/7Unique-LocalRFC 4193, RFC 8190No
fe80::/10Link-Local UnicastRFC 4291No

Why IP lookups show nothing for these addresses

Geolocation and WHOIS describe addresses that are routed on the internet. A private, loopback or link-local address belongs to whichever network it is used in, so there is no owner or location to report; a registry lookup returns IANA’s reservation instead.

Source

The IPv4 and IPv6 Special-Purpose Address Registries, maintained by IANA under RFC 6890, read 21 Oct 2026. The explanations above paraphrase the RFC named next to each block. How the data pages are built.