Overview

A network address is any label used to identify a node, interface, service, or group on a communications network so that data can be directed and delivered correctly. Addresses appear at different layers of networking — for example, link-layer hardware addresses, Internet Protocol addresses, and port numbers — and work together to establish end-to-end communication.

Types and structure

Common examples include:

  • IP addresses: numeric identifiers used by the Internet Protocol. IPv4 uses 32 bits while IPv6 uses 128 bits; an IP address may be split into a network prefix and a host identifier.
  • MAC addresses: flat, usually hardware-assigned link-layer identifiers used on Ethernet and other LANs for local delivery.
  • Port numbers: transport-layer selectors appended to an IP address to target a specific service or application on a host.
  • Special addresses: broadcast, multicast, anycast, and reserved/private ranges used for particular delivery behaviors or administrative needs.

History and development

Addressing evolved with networking: early networks used simple fixed identifiers; the IP family introduced structured addressing that supports routing across many interconnected networks. Growth of the global Internet exposed limits in older schemes, driving classless addressing, dynamic assignment, and the development of IPv6 to expand address capacity.

Uses and practical considerations

Network addresses enable routing, access control, logging, and policy enforcement. They are essential for name resolution (mapping hostnames to addresses), address translation (NAT), and address allocation (static versus DHCP). Addressing decisions affect scalability, performance, and privacy: public addresses expose endpoints to the wider Internet while private ranges and NAT can obscure internal topology.

Distinctions and notable facts

Addresses are distinct from names: a hostname or domain name is a human-friendly label resolved to an address by directory services. An address is also distinct from an identifier that might be independent of location. Understanding which layer an address belongs to and how it is allocated helps diagnose connectivity, security, and configuration issues.