IP Addressing Explained: How Devices Find Each Other on a Network

Every time you load a page, send a message, or stream a video, your device and a server somewhere find each other among billions of machines and exchange data in milliseconds. That works because of a small stack of cooperating systems — IP addressing, subnets, DNS and ports. This guide is the map of how they fit together; each piece links to a deeper article.

Throughout, you can put the ideas to work with the IP Lookup and Subnet Visualizer tools — all running in your browser.

What an IP address is

An IP address is a numeric label that identifies a device on a network — the equivalent of a postal address for data. When your computer sends a packet, it stamps it with a destination IP (where it is going) and a source IP (where replies come back to), and the network’s routers pass it hop by hop toward its destination.

There are two versions in use. IPv4 writes the address as four numbers 0–255 separated by dots — 192.168.1.10. IPv6 is much longer, written in hexadecimal groups — 2001:0db8:85a3::8a2e:0370:7334. Why two? Because the internet ran out of the first kind, a story told in IPv4 vs IPv6.

How an IPv4 address is built

An IPv4 address is really a single 32-bit number, split into four 8-bit octets for readability. Each octet is 0–255 because 8 bits hold 256 values:

Crucially, an address has two parts: a network portion (which network you are on) and a host portion (which device on that network). Where the split falls is decided by the subnet mask — the single most important concept for actually working with addresses, covered in Subnetting Explained.

Public vs. private addresses

Not every address is reachable from the internet. Specific ranges are reserved as private, for use inside home and office networks:

Your laptop, phone and TV each get a private IP from your router. To the outside internet, they all share one public IP — the address your router was given by your ISP. The router juggles the traffic using NAT (Network Address Translation), rewriting addresses so replies find their way back to the right internal device. An IP Lookup shows the public address the world sees, along with its approximate location and network owner.

A few addresses with special jobs

• 127.0.0.1 (“localhost”) — your own machine, used for testing.
• 0.0.0.0 — “any address,” often meaning “listen on every interface.”
• The first and last address of a subnet — the network and broadcast addresses, which is why a subnet’s usable host count is always two less than its size (see Subnetting).

From names to numbers: DNS

You never type 142.250.72.14 — you type a domain name. The Domain Name System (DNS) is the internet’s phone book, translating human names like example.com into the IP addresses machines route by. It happens invisibly before every connection, and when it is slow or broken, the whole internet feels down even though it is not. How that lookup works is in How DNS Works.

One address, many services: ports

A single server hosts many services at once — a website, email, a database. The IP address gets data to the machine; a port number gets it to the right program on that machine. Web traffic uses port 443, email and other services have their own. Addresses plus ports are what a connection is really made of, explained in Ports & Protocols.

Putting it together

So a single click sets off a precise chain: DNS turns the name into an IP, your device wraps the request with source and destination IP addresses and a destination port, your router applies NAT, and routers forward it across networks — each using subnet maths to decide where it goes next — until it reaches the server, which replies back along the same path. Each link in that chain has its own article, and the networking tools let you inspect every piece live. Start with whichever one you need next.