Reserved & Special IP Addresses (127.0.0.1 and More)

Not every IP address is fair game for the open internet. This is a friendly tour of the reserved and special IP addresses — loopback, private ranges, link-local and more — and the quiet jobs they do behind the scenes.

If you have spent any time around computers, you have probably met 127.0.0.1 or typed 192.168.1.1 into a browser to reach a router. These are examples of reserved IP addresses: blocks of the address space that the internet's standards bodies have carved out for special purposes rather than handing to the public internet. They are the internet's utility rooms — unglamorous, essential, and mostly invisible until you know they are there.

If addresses in general are still fuzzy, our beginner guide to what an IP address is lays the groundwork. Here we zoom in on the special cases and what makes each one special.

Why reserved IP addresses exist

An IP address is just a number, but numbers only mean something when everyone agrees on the rules. To keep the system orderly, the organisations that steward the internet — you can read about them in who runs the internet — set aside certain ranges for defined technical jobs. Public routers are configured to treat these ranges specially, most often by simply refusing to forward them. That is what makes a reserved address behave differently from an ordinary one: the network as a whole has agreed on what it means.

127.0.0.1: the loopback address (localhost)

The most famous special address of all is 127.0.0.1, known as the loopback address or by its nickname localhost. Anything you send to it never touches the network — your device's own software loops it straight back to itself. In fact the entire 127.0.0.0/8 range (every address starting with 127.) is reserved for loopback.

Loopback is used everywhere. Developers run a website on their own machine and view it at http://127.0.0.1 before it ever goes live. Programs on the same computer use it to talk to one another as if over a network. It is a safe, private sandbox that always points back home.

Private ranges: the addresses inside your home

The reserved addresses you meet most often are the private ranges. These are set aside for use inside private networks — homes, offices, schools — and are never routed on the public internet. Because they are reused by millions of separate networks at once, they are the backbone of how NAT lets many devices share one public address. There are three blocks:

This is why your laptop might be 192.168.1.24 and your router 192.168.1.1. Those addresses have meaning only within your own network; the same numbers are in use on countless other networks at the same time. Our guide to public versus private IP addresses digs into how the two work together, and if you want to understand the /8 and /16 notation above, see what a subnet mask is.

169.254.x.x: link-local addresses

Sometimes a device is told to get an address automatically but no address server answers. Rather than give up, it assigns itself one from the link-local range 169.254.0.0/16. This mechanism is often called APIPA on Windows. A link-local address only works on the immediate local segment and is never routed anywhere.

In practice, seeing a 169.254.x.x address is usually a symptom rather than a goal: it typically means your device failed to reach a DHCP server and fell back to talking only to whatever is directly attached. If your internet has stopped working and you spot one of these, that is a strong clue about where to look.

Documentation addresses: the ones in every example

Have you noticed that this site keeps using 192.0.2.1 in its examples? That is deliberate. Three ranges are reserved specifically for documentation and examples, so that tutorials and manuals never accidentally point at a real, live address someone owns:

• 192.0.2.0/24
• 198.51.100.0/24
• 203.0.113.0/24

For IPv6, the equivalent documentation range gives us the familiar 2001:db8:: prefix — which is exactly why an example IPv6 address looks like 2001:db8::1. Whenever you see these in a guide, you know they are stand-ins, safe to use because they can never clash with anyone's real network.

Other special-purpose addresses

Several more reserved ranges do specific jobs you will run into eventually:

• 0.0.0.0 — a catch-all meaning "this network" or "any address." Servers use it to mean "listen on every available interface."
• Broadcast (255.255.255.255) — a message sent here goes to every device on the local network at once.
• Multicast (224.0.0.0/4) — a range for sending one stream of data to many interested devices efficiently, used in streaming and service discovery.
• Shared address space (100.64.0.0/10) — set aside for providers running large-scale NAT, so their internal plumbing does not collide with customers' own private ranges.
• IPv6 loopback (::1) — the IPv6 counterpart of 127.0.0.1.

How to recognise a reserved address at a glance

You do not need to memorise every range. A few quick mental checks cover most encounters:

• Starts with 127.? That is loopback — it points back at the device itself.
• Starts with 10., 192.168., or 172.16.–172.31.? That is a private address inside a local network.
• Starts with 169.254.? That is link-local, and often a sign something went wrong getting a real address.
• Looks like 192.0.2.x, 198.51.100.x, or 203.0.113.x? That is a documentation example, not a live address.

Everything else is most likely an ordinary, routable address — the kind you would see if you checked your own connection over at IP Animals. These quiet, reserved corners of the address space are what let the noisy, public part run smoothly.