Ip Address
An IP address is the numeric label that identifies a network interface on an Internet Protocol network, serving two purposes at once: it names which interface a packet is meant for, and it encodes where that interface sits in the network, which lets routers decide which direction to forward each packet. Every device that talks over the Internet or a local network, from a phone to a cloud server, uses at least one.
IPv4, specified in RFC 791 in 1981, uses 32-bit addresses written as four decimal numbers from 0 to 255 separated by dots, such as 192.168.1.20. The 32 bits allow about 4.3 billion unique addresses, which seemed vast in an experimental research network and proved far too few once billions of people and devices connected. An address has two parts, a network prefix and a host portion, and the split is written with CIDR notation: 203.0.113.0/24 means the first 24 bits identify the network and the remaining 8 identify hosts within it. Routers keep tables of prefixes rather than individual machines, which is what keeps global routing tractable.
IPv6, whose core specification dates from 1998 and was later revised as RFC 8200, uses 128-bit addresses written as eight groups of hexadecimal digits separated by colons, with runs of zeros collapsible to a double colon. The 128-bit space is about 3.4 × 10^38 addresses, enough that every subnet can be generously sized and addresses need not be rationed. IPv6 also drops header fields, removes router fragmentation and builds in autoconfiguration. The IANA handed out its last free blocks of IPv4 space in 2011, and most regional registries have since run out of their own pools, yet adoption of IPv6 has been gradual, with the two protocols running side by side in what is called dual stack.
Not every address is meant to be reachable from the Internet: RFC 1918 reserves 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 for private networks, and the same ranges are reused in millions of homes and offices. Network address translation (NAT) is the workaround that let IPv4 stretch for decades: a home router holds one public address, rewrites the source of outgoing packets, and tracks port numbers so that returning replies reach the right device. Other special addresses include the loopback address 127.0.0.1 (IPv6: ::1), which always means this machine itself and is what "localhost" resolves to, and the 169.254.0.0/16 link-local range, which a device assigns itself when no DHCP server answers.
Addresses are usually assigned dynamically by DHCP (Dynamic Host Configuration Protocol), which leases an address, along with the default gateway and DNS server, to each device that joins a network. Servers and printers, by contrast, are often given static addresses so they remain findable. Containers and virtual machines in cloud environments receive addresses from software-defined networks, and a Kubernetes cluster running machine-learning workloads may assign thousands of short-lived internal addresses, which is why address planning and subnet sizing still matter to engineers in the IPv6 era.
Several misconceptions are worth correcting: an IP address is not a permanent identity, not a precise location, and not the same as a hostname. Home addresses often change, many people share one public address behind NAT or carrier-grade NAT, and geolocation databases only estimate a city or region. Names such as example.org are mapped to addresses by DNS, a separate system, and one name may map to many addresses or one address to many names. Also, a private address does not mean a device is secure; NAT incidentally blocks unsolicited inbound traffic but is not a firewall, and IPv6 deployments generally rely on firewall rules instead.
Read an IP address as a hierarchical postal address for packets: a prefix that tells routers which direction to send traffic, a host part that picks the interface at the end, and a set of conventions (DHCP, NAT, private ranges, IPv6) that decide who gets one and how far it can be seen.