What is an IPv4 address?
An IPv4 address is a 32-bit identifier used by Internet Protocol version 4 to address a network interface. Routers read the destination address and a prefix length to decide where to forward a packet. An address helps identify a network location; it does not identify a person, prove ownership, or make a service reachable by itself.
Humans normally write the 32 bits as four decimal octets separated by periods, such as 192.0.2.25. Each octet represents 8 bits and can range from 0 to 255. The example is from TEST-NET-1, a block reserved for documentation, so it is safe to use in diagrams and examples.
IPv4 address format and example
| Part | Value | Meaning |
|---|---|---|
| Address | 192.0.2.25 | Four decimal octets representing 32 bits |
| Prefix length | /24 | The first 24 bits identify the routing prefix |
| Subnet mask | 255.255.255.0 | Another way to express the same 24-bit prefix |
| Prefix | 192.0.2.0/24 | The complete block described by the address and prefix length |
The address alone is incomplete routing information. Modern networks use classless addressing, so the leading digits do not reveal the network boundary. The prefix length or subnet mask must be supplied. A /24 is only one example; IPv4 prefixes can use other lengths depending on the network design.
Learn how prefix length changes address capacity in the subnetting guide.
An IPv4 address is not an IPv4 packet
An address is one value carried inside an IPv4 packet header. The packet also has fields such as source address, destination address, protocol, time to live, total length, fragmentation information, and a header checksum. Those fields describe delivery of a datagram; they are not parts of the address itself.
IPv4 provides best-effort packet delivery. It does not provide end-to-end reliability, sequencing, retransmission, encryption, or identity on its own. TCP, UDP, IPsec, TLS, applications, and network controls provide different functions above or alongside IP.
IPv4 address scopes and special-use ranges
“Public” and “private” are useful starting labels, but IPv4 contains several special-purpose ranges. Assignment, routing, filtering, and translation determine how an address can actually be used.
| Range or example | Purpose | Globally reachable by default? |
|---|---|---|
| Public address space | Globally unique space allocated or assigned through Internet registries and providers | Potentially, when authorized and routed; not guaranteed |
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 | Private use under RFC 1918 | No |
127.0.0.0/8 | Loopback on the local host | No |
169.254.0.0/16 | IPv4 link-local communication | No |
100.64.0.0/10 | Shared address space commonly used between a provider and subscribers | No |
192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24 | Documentation examples | No |
Private addresses can be reused inside different networks because they are not globally unique. A network commonly uses NAT or PAT to let private endpoints initiate traffic through one or more public addresses. NAT changes the address and often the port visible across the boundary; it is not encryption or a firewall.
See the public versus private IP guide for routing, NAT, and reachability details.
What are the advantages of IPv4?
IPv4 remains useful because it is widely deployed and understood, not because it is automatically faster or more secure than IPv6.
- Broad compatibility: Networks, operating systems, applications, monitoring tools, and support teams have decades of IPv4 deployment experience.
- Mature operations: Address management, routing, DNS, firewall, observability, and troubleshooting workflows are available across most infrastructure platforms.
- Compact base header: An IPv4 header can be 20 bytes without options. This is smaller than the fixed 40-byte IPv6 base header, although real performance depends on the full path, extensions, transport, workload, and implementation.
- Private address reuse: RFC 1918 addressing and NAT let many internal endpoints share a smaller public IPv4 pool. This conserves public addresses but introduces translation state and operational tradeoffs.
- Incremental coexistence: Dual-stack and translation designs let organizations keep IPv4 connectivity while adding IPv6 according to application and partner readiness.
These are deployment advantages, not guarantees. IPv4 does not inherently provide stronger security, easier configuration, better quality of service, or flawless delivery.
What are the limitations of IPv4?
- Finite address space: A 32-bit address field contains 232, or 4,294,967,296, possible values before reserved and special-purpose space is considered. Public scarcity affects acquisition, allocation, and network design.
- Address sharing adds state: NAT and CGNAT can conserve public addresses, but port capacity, logs, inbound reachability, application behavior, failover, and attribution become more complex.
- Security is separate: An IPv4 address does not authenticate a user, authorize a route, encrypt traffic, or apply firewall policy.
- Renumbering can be costly: Hard-coded addresses, allowlists, DNS records, certificates, logs, and partner systems can turn an address change into a coordinated migration.
- Fragmentation and path behavior need care: MTU differences, filtering, and middleboxes can cause failures that are easy to misdiagnose.
IPv4 vs IPv6
| Characteristic | IPv4 | IPv6 |
|---|---|---|
| Address length | 32 bits | 128 bits |
| Common notation | Dotted decimal, such as 192.0.2.25 | Colon-separated hexadecimal, such as 2001:db8::25 |
| Base header | 20 bytes minimum; options can make it longer | 40 bytes fixed; optional information uses extension headers |
| Address conservation | Private addressing and NAT are common responses to scarcity | Much larger address space reduces the need for conservation through address sharing |
| Broadcast | Supports broadcast in defined scopes | Uses multicast instead of broadcast |
IPv6 does not make IPv4 disappear immediately, and neither protocol makes a network secure by default. Many organizations run both. The right migration plan depends on application support, upstream connectivity, DNS, security controls, observability, partners, and rollback needs.
What should you verify before using an IPv4 address or block?
- Prefix: Record the exact address and prefix length. Do not infer a classful boundary from the first octet.
- Scope: Check whether the address is public, private, shared, loopback, link-local, documentation, multicast, or another special purpose.
- Authority: For public resources, verify current registry records, contractual rights, and the party authorized to announce or delegate the prefix.
- Routing: Confirm the origin ASN, route acceptance, IRR and RPKI responsibilities, upstream filters, failover, and minimum accepted prefix.
- Services: Plan forward and reverse DNS, firewall policy, NAT, monitoring, geolocation, reputation, and abuse contacts separately.
- Lifecycle: Define activation, evidence dates, renewal, transfer or return, renumbering, and rollback before production use.
The Regional Internet Registry guide explains the registration system. If you need routable capacity, compare the operating responsibilities in the IPv4 leasing guide before treating an address listing as deployment-ready.
IPv4 address FAQ
Is an IPv4 address always public?
No. IPv4 includes public space, the three RFC 1918 private blocks, loopback, link-local, shared, documentation, multicast, and other special-purpose ranges. An address must be interpreted with its prefix, scope, assignment, and routing context.
How many numbers are in an IPv4 address?
The common notation has four decimal octets separated by periods. Each octet is a number from 0 to 255 and represents 8 bits, for a total of 32 bits.
Does an IPv4 address identify a person or device?
No. An address identifies a network-layer location for a period of time. It may represent an interface, router, NAT gateway, proxy, VPN exit, shared service, or many subscribers. Attribution needs authorized logs, timestamps, ports, protocol, assignment records, and corroborating evidence.
Is 192.168.1.1 a public IPv4 address?
No. It falls within 192.168.0.0/16, one of the private-use blocks reserved by RFC 1918. Different private networks can reuse it, so it is not globally unique or routed on the public Internet.
Is IPv4 obsolete?
No. IPv4 remains widely deployed, but its address scarcity and address-sharing costs are important constraints. IPv6 provides a much larger address space. Many networks use dual stack or translation while applications and partners move at different speeds.
