Who invented an IP address?

The invention of the IP address cannot be attributed to a single individual. IP addressing developed as part of the broader creation of the Internet Protocol, with contributions from researchers, engineers, government agencies, universities, and standards organizations over several decades.

The fundamental design behind IP addressing is closely associated with Vint Cerf and Robert Kahn, who are often referred to as the “fathers of the internet.” During the 1970s, they developed the core ideas that became the Transmission Control Protocol and Internet Protocol suite, commonly known as TCP/IP. This system allowed different computer networks to communicate with one another as parts of a larger interconnected network.

An IP address is a numerical identifier assigned to a device or network interface that communicates using the Internet Protocol. Its main purpose is to help data reach the correct destination. When information is sent across the internet, it is divided into packets. Each packet contains addressing information that routers use to determine where the packet should go.

Who Created the Idea Behind IP Addresses?

Vint Cerf and Robert Kahn played central roles in designing the networking architecture from which modern IP addressing emerged. In 1974, they published work describing a method for connecting separate packet-switched networks. Their design focused on creating a common communication system that could operate across networks built with different technologies.

The original design combined several responsibilities into a single protocol. As the system evolved, these responsibilities were separated. The Internet Protocol handled addressing and packet delivery between networks, while the Transmission Control Protocol handled reliable communication, including ordering packets and retransmitting missing data.

This division became the basis of TCP/IP. IP addresses were necessary because every packet needed information identifying its source and intended destination. Without a consistent addressing system, routers would not know how to move packets from one network to another.

Cerf and Kahn did not work in isolation. Many other researchers helped test, refine, document, and implement the technologies that became the modern internet. For this reason, it is more accurate to describe the IP address as the result of a collaborative engineering process rather than the invention of one person.

The Role of ARPA and Early Computer Networks

Much of the early research took place under the Advanced Research Projects Agency, commonly known as ARPA and later renamed DARPA. The agency supported experimental computer networking projects, including ARPANET, one of the earliest large packet-switching networks.

ARPANET initially connected research institutions and allowed computers at different locations to exchange information. However, ARPANET was only one network. Researchers soon faced a larger problem: how could ARPANET communicate with other packet-based networks, including radio and satellite networks, without requiring all of them to use identical equipment and internal designs?

The solution was an internetworking architecture. Instead of treating every connected system as part of one uniform network, the new approach allowed independent networks to exchange packets through shared protocols. The word “internet” originally described this concept of interconnected networks.

IP addressing became an essential part of that architecture. Each participating system needed an address that could be recognized beyond its immediate local network. Routers, originally called gateways in much of the early documentation, examined those addresses and forwarded packets toward their destinations.

Jon Postel and the Standardization of IPv4

Another major contributor was computer scientist Jon Postel. He edited and authored many of the technical documents that defined early internet protocols. Postel served as the editor of the specification published as RFC 791, which formally described Internet Protocol version 4 in 1981.

RFC stands for “Request for Comments.” RFC documents are used to publish technical specifications, proposed standards, procedures, and other information related to internet technologies. Although the name sounds informal, many RFCs contain the standards on which internet communication depends.

Postel’s role in documenting and coordinating internet protocols was highly influential, but he is not generally described as the sole inventor of the IP address. His work was part of a larger collaboration involving protocol designers, programmers, network operators, and research institutions.

By the beginning of the 1980s, the structure of IPv4 addressing had become clearly defined. On January 1, 1983, ARPANET officially changed from its earlier Network Control Protocol to TCP/IP. This transition is often treated as a major milestone in the development of the modern internet.

How IPv4 Addresses Work

IPv4 uses a 32-bit address format. A bit is a binary digit with a value of either 0 or 1. Because an IPv4 address contains 32 bits, the system provides approximately 4.3 billion possible numerical combinations.

IPv4 addresses are normally displayed as four decimal numbers separated by periods, such as 192.0.2.10. Each number represents eight bits and can range from 0 to 255. This familiar notation makes addresses easier for people to read than a continuous sequence of binary digits.

An IPv4 address contains information that helps identify the network and the device or interface within that network. Early IPv4 networks used address classes to divide the address space into networks of different sizes. This class-based system was later replaced by Classless Inter-Domain Routing, which allowed address blocks to be allocated more efficiently.

Not every numerical IPv4 address can be assigned freely to a public device. Some address ranges are reserved for private networks, testing, documentation, loopback communication, multicast traffic, and other specialized purposes. Private IPv4 addresses are commonly used inside homes, offices, and data centers. A router can use Network Address Translation to allow multiple private devices to share one public IPv4 address.

Why the Internet Needed IPv6

When IPv4 was designed, billions of possible addresses appeared to provide an enormous amount of capacity. The designers could not fully anticipate how many personal computers, phones, servers, household devices, industrial systems, and other products would eventually connect to IP networks.

As internet use expanded, the supply of unallocated IPv4 addresses became increasingly limited. Techniques such as private addressing, Network Address Translation, and more efficient allocation slowed the rate of exhaustion, but they did not increase the underlying 32-bit address space.

This limitation led to the development of Internet Protocol version 6. Work on IPv6 took place through the Internet Engineering Task Force during the 1990s. IPv6 was designed not only to provide more addresses, but also to improve several aspects of packet handling, network configuration, and protocol extensibility.

IPv6 uses a 128-bit address format. Its address space is vastly larger than that of IPv4, providing approximately 3.4 times 10 to the power of 38 possible addresses. This capacity is large enough to assign addresses across an enormous number of networks and connected devices without relying on the same level of address sharing required by IPv4.

An IPv6 address is written in hexadecimal and divided into groups separated by colons. A full address may look like 2001:0db8:0000:0000:0000:0000:0000:0010. Rules allow leading zeros and consecutive groups of zeros to be shortened, making many IPv6 addresses more manageable.

The Role of the IETF and Other Organizations

The Internet Engineering Task Force, or IETF, has played a major role in developing and maintaining standards for IP-based communication. The IETF is an open international community of network designers, engineers, researchers, vendors, and operators. Its working groups develop technical proposals that may eventually become internet standards.

Other organizations also support the operation of IP addressing. Regional Internet registries distribute address blocks within major geographic regions. Internet service providers and large organizations then assign smaller blocks or individual addresses to customers, networks, and devices.

The Internet Assigned Numbers Authority coordinates important global numbering resources, including the distribution of large IP address blocks to regional registries. These administrative systems were developed after the technical concept of IP addressing, but they are necessary for keeping address assignments organized and reducing conflicts.

No central organization controls every IP address used on every network. Private organizations can manage addresses internally, while public address allocation follows a coordinated global structure. This combination allows individual networks to operate independently while still participating in worldwide internet communication.

What an IP Address Does and Does Not Identify

An IP address is often compared to a mailing address, but the comparison is imperfect. A mailing address usually points to a relatively stable physical location. An IP address identifies a point of communication within a network and may change over time.

Internet service providers frequently assign addresses dynamically. A household may use one public IP address today and receive another later. Mobile devices can also receive different addresses as they move between cellular networks, Wi-Fi networks, and other connections.

An address may represent a router serving many devices rather than one specific computer or person. Large websites can use multiple addresses, and many websites can share the same server address. Cloud services may move applications between systems while preserving the service available to users.

For these reasons, an IP address alone does not always identify a particular person, device, or exact physical location. It provides information needed for network communication, but interpreting that information often requires additional records and technical context.

IP Addresses and Domain Names

IP addresses should not be confused with domain names. An IP address is used by network protocols to route data, while a domain name provides a readable label such as example.com. The Domain Name System translates domain names into IP addresses so that users do not need to remember long numerical identifiers.

A domain name can point to more than one IP address, and the address associated with a domain can change. This flexibility allows website operators to balance traffic, replace servers, use content delivery networks, and maintain services across different locations.

DNS and IP addressing therefore perform related but separate jobs. DNS helps users and applications discover an address, while IP uses that address to move packets toward the intended destination.

A Collective Invention

The question “Who invented the IP address?” does not have a single-name answer. Vint Cerf and Robert Kahn developed the central internetworking concepts behind TCP/IP. Jon Postel and other researchers helped document, refine, and standardize the protocols. ARPA funded and supported much of the early experimentation, while institutions and engineering groups tested the technology in real networks.

The original IPv4 addressing system emerged from this shared work and became a foundation of internet communication during the 1980s. The later development of IPv6 continued the same collaborative model through the IETF and the wider networking community.

IP addresses are therefore best understood as part of an evolving technical system created by many contributors. Their work produced a common addressing method that allows independently operated networks and billions of connected devices to exchange information across the internet.