IPv4 Subnet Calculator: Check Your Network Range at a Glance

Plan your next network change

An IPv4 subnet calculator helps a small team check address boundaries before configuring DHCP, routes, a firewall, or a cloud network. Enter an address and CIDR prefix to review the network address, subnet mask, broadcast address, and host range.

Try the free IPv4 subnet calculator with a synthetic address before planning a change. A calculator checks arithmetic; it cannot inspect your routing table, identify overlapping networks, confirm address ownership, or approve a production change.

Understand CIDR and subnet masks

CIDR notation places a prefix length after the address, as in 192.0.2.34/27. The address is a host candidate; /27 means the first 27 bits identify the network. Its dotted-decimal subnet mask is 255.255.255.224. Five host bits create a block of 32 addresses. Under the traditional IPv4 convention, the first is the network address and the last is the broadcast address, leaving 30 usable host addresses.

Platform conventions can differ, especially for point-to-point links and cloud networks. Confirm the rules for your environment before treating a calculator's usable count as a DHCP pool size.

Example: divide a documentation block

Suppose a lab is assigned the synthetic documentation block 192.0.2.0/24 and needs four equal subnets. Borrowing two host bits changes the prefix to /26, creating four blocks of 64 addresses:

• 192.0.2.0/26
• 192.0.2.64/26
• 192.0.2.128/26
• 192.0.2.192/26

For the second block, .64 is the network address, .127 is the broadcast address, and .65 through .126 are the conventional usable host range. These are documentation-only values, not a recommendation for a real network. Confirm the parent block is assigned to the lab and does not overlap an existing route.

A six-step subnet planning workflow

1. Confirm the parent range. Check its owner, environment, and prefix in your IP address management record.
2. Estimate demand. Count endpoints and growth, plus gateways and platform reservations.
3. Select a prefix. Provide enough addresses without consuming a larger block than needed.
4. Check the boundaries. Use a calculator to compare the network address, mask, broadcast address, host range, and count.
5. Check for overlap. Compare office, VPN, cloud, container, and reserved ranges, including larger connected prefixes.
6. Record and review. Update IPAM and obtain the normal change approval before configuring DHCP, routing, or firewall policy.

The calculator assists with step four. It does not inventory existing routes or perform the approval steps.

Common mistakes to catch

A mathematically valid subnet can still be operationally wrong. A team may forget a gateway, static device, cloud-reserved address, or DHCP exclusion. A mask typo can shift a boundary, so compare both the starting and ending addresses. Check copied values carefully and use standard dotted-decimal notation.

For /31 and /32, traditional network and broadcast assumptions may not describe the way a platform uses a point-to-point link or a single-host route. Read the tool's assumptions and the platform documentation. If the result looks surprising, verify it through an independent reviewed method, such as an IPAM system or tested script.

Verify before implementation

Have a second operator compare the prefix, proposed range, and neighboring routes. Check the change record, IPAM entry, DHCP scope, firewall objects, and cloud network configuration against the same plan. After an approved change, test reachability and name resolution through your normal procedures, then record the observed result and rollback point.

If the ranges overlap or the parent allocation is uncertain, stop and ask the network owner rather than choosing a different prefix on the fly. A calculator can reduce arithmetic mistakes; it cannot prove reachability, establish authorization, or guarantee an outage-free change. Use synthetic examples for practice and follow your organization's handling rules for internal address plans.