IP Subnet Calculator

2. What Is an IP Address?

An Internet Protocol address identifies an interface or endpoint within an IP networking system. The two address families handled by this calculator are:

• IPv4: 32 bits
• IPv6: 128 bits

IPv4 Address Structure

An IPv4 address contains four 8-bit octets written in dotted-decimal notation. For example: 192.168.1.25. Each octet can range from 0 through 255. The complete IPv4 address therefore contains:

A subnet prefix determines how many of those bits represent the network.

IPv6 Address Structure

IPv6 uses 128-bit addresses written as eight hexadecimal groups. Example: 2001:db8::1. An IPv6 address can have a subnet prefix followed by an interface identifier. RFC 4291 defines IPv6 addresses as 128-bit identifiers and describes unicast, anycast and multicast address types.

The calculator therefore treats IPv4 and IPv6 as fundamentally different address families rather than applying IPv4 rules to both.

3. What Is a Subnet and Why Do We Subnet?

A subnet is a logical subdivision of an IP network. Subnetting allows a larger address block to be divided into smaller networks that can be routed and administered separately. Instead of using one large network for an entire organization, separate subnets can be created for:

• Employee workstations and departmental computers
• Production and internal application servers
• Printers and shared office peripherals
• Physical security cameras and access controls
• Guest wireless clients
• Out-of-band management interfaces

Subnetting provides four major administrative and routing benefits:

• Smaller broadcast domains: In traditional IPv4 Ethernet networks, broadcast traffic (such as ARP queries) is confined to the local subnet. Splitting an oversized network reduces the number of devices participating in the same broadcast domain, avoiding performance degradation.
• Better segmentation: Separate subnets make it easier to apply routing policies, Access Control Lists (ACLs), and firewall inspection boundaries between departments.
• More efficient address allocation: CIDR allows organizations to allocate address blocks closer to actual requirements instead of depending on fixed classful sizes.
• Easier route organization: Related networks can be aggregated into a summarized route, reducing the number of individual prefixes represented in global routing tables.

4. Understanding CIDR Notation

CIDR notation combines an address with a prefix length. For example: 192.168.1.0/24.

The /24 designates:

• 24 network bits
• 8 host bits (since 32 − 24 = 8)

The total number of addresses is calculated as 2⁸ = 256. For the traditional IPv4 host-count model, two addresses are reserved:

• The network address (all host bits 0)
• The directed broadcast address (all host bits 1)

Therefore, the traditional usable-host count is:

The important distinction is that total addresses and usable hosts are not the same quantity. For 192.168.1.0/24:

• Network: 192.168.1.0
• First usable: 192.168.1.1
• Last usable: 192.168.1.254
• Broadcast: 192.168.1.255

5. How to Calculate a Network Address

The network address is found by applying a bitwise AND operation between the IP address and the subnet mask.

Consider IP: 192.168.1.25 with prefix /24. The subnet mask is 255.255.255.0.

Therefore, 192.168.1.25/24 belongs to the network block 192.168.1.0/24. The calculator exposes this logic in its calculation-engine steps and binary breakdown so the result can be independently checked.

6. How to Calculate a Broadcast Address and Wildcard Mask

For traditional IPv4 subnetting, the broadcast address is the address obtained when all host bits are set to 1. Another way to derive it is using the wildcard mask.

The wildcard mask is the bitwise inverse (NOT) of the subnet mask. For subnet mask 255.255.255.0, the wildcard mask is 0.0.0.255.

The broadcast address can then be expressed as:

For Network 192.168.1.0 and Wildcard 0.0.0.255, performing bitwise OR results in 192.168.1.255.

7. Worked IPv4 Example: 192.168.1.25/24

Suppose the input address is 192.168.1.25/24. The subnet calculations proceed across six distinct stages:

1. Determine the subnet mask: Prefix /24 corresponds to dotted-decimal 255.255.255.0.
2. Determine host bits: 32 − 24 = 8 host bits.
3. Determine total addresses: 2⁸ = 256 total IP addresses.
4. Determine network address: Bitwise AND between 192.168.1.25 and 255.255.255.0 yields 192.168.1.0.
5. Determine broadcast address: Setting the 8 host bits to 1 yields 192.168.1.255.
6. Determine traditional usable hosts: Range is 192.168.1.1 through 192.168.1.254 (254 usable host addresses).

This reference IPv4 example verifies binary operations and numerical integrity against standard networking specifications.

8. IPv4 Prefixes and Host Capacity

For an ordinary IPv4 subnet, the number of host bits is H = 32 − prefix, and the total number of addresses is 2ᴴ. Under traditional subnetting rules:

The /31 case requires special handling because the traditional network/broadcast subtraction rule does not apply. RFC 3021 defines the use of 31-bit prefixes on point-to-point IPv4 links where both addresses are treated as interface endpoints.

A /32 identifies a single IPv4 address (0 host bits) and is commonly used for loopback or host routes. The calculator explicitly handles /31 and /32 rather than applying the 2ᴴ − 2 rule indiscriminately.

9. Private IPv4 Address Ranges

Three IPv4 address blocks are reserved for private internets under RFC 1918:

• 10.0.0.0/8: 10.0.0.0 to 10.255.255.255 (16,777,216 addresses)
• 172.16.0.0/12: 172.16.0.0 to 172.31.255.255 (1,048,576 addresses)
• 192.168.0.0/16: 192.168.0.0 to 192.168.255.255 (65,536 addresses)

These addresses are intended for private network use and are not globally routable on the public internet without Network Address Translation (NAT). Examples include 10.1.2.3, 172.16.5.10, and 192.168.1.25.

An important detail is that not every address beginning with 172 is private. For instance, 172.16.0.1 is private, whereas 172.15.255.255 and 172.32.0.0 are public unicast addresses. The calculator validates exact RFC 1918 boundaries.

10. Classful Networking Versus CIDR

Older IPv4 networking terminology divided address space into rigid classes: Class A (/8), Class B (/16), and Class C (/24). The familiar historical examples include 10.0.0.0, 172.16.0.0, and 192.168.1.0.

The calculator includes legacy class shortcuts because they remain useful for training and recognizing common private-network examples. However, modern network engineering is based on CIDR prefix lengths, not rigid classful allocation. RFC 4632 describes CIDR as the classless architecture for IPv4 address assignment and route aggregation. Therefore, 192.168.1.0/26 is properly understood as a 26-bit prefix allocating a 64-address block, rather than merely "a subnetted Class C."

11. Subnet Splitter: Dividing One Network Into Smaller Networks

The Subnet Splitter starts with a parent network and divides it into smaller child networks.

Suppose the parent network is 192.168.1.0/24 and the target prefix is /26.

The four child networks are:

• Subnet 1: 192.168.1.0/26 (Hosts: 192.168.1.1 – 192.168.1.62, Bcast: 192.168.1.63)
• Subnet 2: 192.168.1.64/26 (Hosts: 192.168.1.65 – 192.168.1.126, Bcast: 192.168.1.127)
• Subnet 3: 192.168.1.128/26 (Hosts: 192.168.1.129 – 192.168.1.190, Bcast: 192.168.1.191)
• Subnet 4: 192.168.1.192/26 (Hosts: 192.168.1.193 – 192.168.1.254, Bcast: 192.168.1.255)

Their ranges are perfectly contiguous and do not overlap. The calculator verifies that each subsequent subnet begins immediately after the preceding subnet's broadcast address.

12. Subnet Planner: Designing a Network From a Host Requirement

The Subnet Planner solves a reverse sizing problem: instead of analyzing an existing prefix, it determines the smallest CIDR block that satisfies a required host count.

For example, suppose a department requires capacity for 50 hosts. Comparing nearby subnet sizes:

• /27 yields 2⁵ − 2 = 30 traditional usable hosts (insufficient)
• /26 yields 2⁶ − 2 = 62 traditional usable hosts (sufficient)

Since /27 is too small and /26 provides 62 slots, the smallest suitable subnet is /26. For a base allocation beginning at 192.168.1.0, the planned block is 192.168.1.0/26 with 62 usable host slots. The calculator selects the minimal prefix and aligns the allocation to a valid network boundary.

13. IPv6 Subnetting

IPv6 changes several fundamental assumptions from IPv4. IPv6 addresses contain 128 bits rather than 32. RFC 4291 defines the IPv6 addressing architecture and the 128-bit address model.

For a prefix length P, the number of addresses represented by the prefix is:

For a standard local subnet of 2001:db8::/64, there are:

That quantity far exceeds JavaScript's 53-bit integer limit (Number.MAX_SAFE_INTEGER), so the calculator utilizes arbitrary-precision 128-bit BigInt logic for exact address calculations.

14. IPv6 Compression and Canonical Representation

IPv6 addresses are commonly written in compressed form. For example, the fully expanded loopback address:

is canonically compressed to ::1.

RFC 5952 establishes the standard canonical representation for IPv6 addresses: leading zeros within each 16-bit hexadecimal field must be suppressed, and the longest run of consecutive 16-bit zero fields must be replaced with :: (used only once). The calculator supports bidirectional expansion and canonical compression.

15. IPv6 Does Not Use IPv4 Broadcast Semantics

One of the most critical differences between IPv4 and IPv6 is the treatment of broadcast. In IPv4, directed broadcast addresses (such as 192.168.1.255) send packets to all hosts on the subnet.

IPv6 does not use broadcast addresses. Instead, IPv6 relies on multicast groups (such as all-nodes multicast ff02::1) and solicited-node multicast for Neighbor Discovery (NDP), replacing ARP. Therefore, an IPv6 subnet result should never report a broadcast address, and host capacity does not subtract 2 addresses.

16. Route Summarization and CIDR Aggregation

Route summarization (CIDR aggregation or supernetting) consolidates multiple routing entries into a single broader prefix when the address blocks fit a continuous common power-of-two boundary.

Consider four contiguous /24 networks:

These can be summarized into a single route: 10.0.0.0/22, which spans from 10.0.0.0 through 10.0.3.255 (1,024 addresses). This reduces routing table overhead on enterprise WAN edge routers.

However, aggregation must be applied with care. For non-contiguous routes such as 10.0.0.0/24 and 10.0.2.0/24, a single /23 cannot represent them without also inadvertently covering 10.0.1.0/24. The calculator verifies contiguity and flags broad supernets.

For traffic-capacity planning alongside subnet design, the Bandwidth Calculator can help estimate required network throughput across aggregated links.

17. Network Bits Versus Host Bits

CIDR divides an IPv4 address into two conceptual parts:

• Network bits: Identify the subnetwork pathway used by routers to forward packets.
• Host bits: Identify individual device network interface cards (NICs) connected to that subnetwork segment.

For 192.168.1.0/26, there are 26 network bits and 6 host bits, yielding 2⁶ = 64 total addresses and 62 usable hosts. A longer prefix means more network bits and fewer host bits; a shorter prefix means fewer network bits and more host bits.

18. Common Subnetting Mistakes

Subnet calculations frequently fail when engineering assumptions from one addressing model are improperly applied to another:

• Confusing total addresses with usable hosts: A /26 contains 64 total addresses, but only 62 usable hosts under traditional IPv4 subtraction rules.
• Applying IPv4 broadcast assumptions to IPv6: IPv6 uses multicast groups rather than directed broadcast.
• Treating all 172.x.x.x addresses as private: Only 172.16.0.0/12 (172.16.0.0 to 172.31.255.255) is private under RFC 1918.
• Creating unaligned subnet boundaries: Subnet blocks must align with power-of-two boundaries (e.g. /26 must begin at .0, .64, .128, or .192).
• Treating /31 like an ordinary subnet: Point-to-point /31 behavior is a special IPv4 case defined by RFC 3021 allowing both endpoints to be utilized.
• Treating /32 as a multi-host subnet: A /32 specifies an individual single host route.
• Assuming every route set can be summarized: Non-contiguous routes produce lossy or broad supernets that cover unallocated space.
• Confusing IPv6 scale: IPv6 address spaces are vast (2⁶⁴ addresses per standard /64 subnet) and do not use traditional IPv4 host subtraction.

19. How to Use the IP Subnet Calculator Efficiently

A reliable subnet engineering workflow follows these steps:

• For IPv4 calculation: Enter the IP address and CIDR prefix (or select from the bidirectional dotted mask list). Review the network ID, broadcast address, wildcard mask, usable host range, host counts, and binary breakdown.
• For IPv6 calculation: Enter the IPv6 address and prefix length. Review canonical compression, expanded representation, network block, and exact BigInt address counts.
• For subnet splitting: Enter base network, base CIDR, and target CIDR. Review generated subnet counts, aligned network boundaries, and host ranges.
• For host planning: Enter base network and required host count. The planner computes the smallest compatible CIDR prefix.
• For route summarization: Enter individual network prefixes to determine the common enclosing supernet.

20. When to Use an IP Subnet Calculator

Subnet calculators are essential tools across network administration, security engineering, and cloud architecture:

• Designing VLAN addressing architectures and IP allocation plans
• Sizing VPC and virtual network subnets in AWS, Azure, and Google Cloud
• Splitting private RFC 1918 allocations for multi-branch organizations
• Determining network and broadcast boundaries for firewall ACL configurations
• Configuring point-to-point /31 router interconnects
• Validating IPv6 local /64 assignments and global unicast blocks
• Preparing for networking certifications (CCNA, CCNP, Network+)

For binary, hexadecimal, and other base-conversion tasks involved in network addressing, the Conversion Calculator can be used alongside subnet calculations. For electrical or infrastructure calculations outside IP addressing, see the Voltage Drop Calculator.

21. IPv4 and IPv6 Should Never Be Treated as the Same Calculation

Although IPv4 and IPv6 both use prefix lengths, their underlying architectures differ fundamentally:

• IPv4: 32 bits, dotted-decimal notation, directed broadcast, traditional host subtraction.
• IPv6: 128 bits, hexadecimal groups, multicast neighbor discovery, no broadcast address, vast address spaces.

IPv4 address counts fit within standard 32-bit integer arithmetic. In contrast, IPv6 address spaces (such as 2⁶⁴) exceed 53-bit precision and require arbitrary-precision 128-bit BigInt calculations to guarantee exact numerical outputs.

22. Engineering Perspective: Calculation Versus Deployment

A subnet calculator verifies mathematical and addressing logic. It does not replace operational verification against hardware capabilities, routing protocol convergence, and cloud security group constraints.

Production deployments depend on router operating systems, DHCP scopes, hypervisor virtual switches, and cloud-provider reserved addresses (for instance, AWS reserves the first four and last IP address in every subnet). Always cross-reference logical calculations against your target deployment environment.

Technical References

• RFC 1918: Address Allocation for Private Internets — Defines the 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 private address ranges.
• RFC 3021: Using 31-Bit Prefixes on IPv4 Point-to-Point Links — Defines the allocation of 2-address subnets for point-to-point router links.
• RFC 4291: IP Version 6 Addressing Architecture — Defines IPv6 128-bit address formats, unicast, anycast, and multicast spaces.
• RFC 4632: Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan — Replaced classful networking.
• RFC 5952: A Recommendation for IPv6 Address Text Representation — Canonical formatting, zero suppression, and compression rules.