A valid host range is the assignable portion of a traditional IPv4 subnet
For a conventional IPv4 subnet, the first address identifies the network and the last address is the broadcast. Ordinary host assignments sit between those two boundaries. That means the useful question is not simply “what range does the calculator show?” but “how were the boundaries derived, and what do they imply for gateways, DHCP, and troubleshooting?”
Calculate the traditional host range and inspect every boundary
Enter an IPv4 address and CIDR prefix. The calculator shows the subnet mask, network address, broadcast address, first and last traditional usable host, total address count, and traditional usable-host count. It is designed to reinforce the manual method rather than hide it.
Find a host range in five repeatable steps
- Convert the prefix to a mask or block size.
- Find the subnet boundary that contains the given address.
- Find the next subnet boundary and subtract 1 for the broadcast.
- Add 1 to the network address for the first traditional usable host.
- Subtract 1 from the broadcast for the final traditional usable host.
Then verify that the original IP lies inside the calculated network-to-broadcast block and that the range size matches the prefix.
192.168.25.150/26
A /26 uses mask 255.255.255.192 and a block size of 64 in the fourth octet. The legal subnet starts are .0, .64, .128, and .192. Address .150 lies in the .128–.191 block.
10.10.10.77/28
A /28 uses a block size of 16. The fourth-octet subnet boundaries include 48, 64, 80, 96, and so on. Since .77 lies between .64 and .79, the subnet is 10.10.10.64/28.
172.16.45.10/20 uses third-octet boundaries
A /20 is 255.255.240.0, giving a third-octet block size of 16. The third-octet boundaries are 0, 16, 32, 48, 64, and so on. The value 45 lies in the 32–47 block.
This matters because not every subnetting problem lives entirely in the fourth octet.
The gateway is normally one valid host inside the same local subnet
A default gateway interface cannot normally use the network or broadcast address. It also needs to be locally reachable by the client. Many networks choose the first usable or last usable address as a convention, but that is a design choice rather than a mathematical requirement.
Valid convention
Network .64/27
Gateway .65
Also valid
Network .64/27
Gateway .94
Invalid
Gateway .64 or .95
network/broadcast
Host-range math is the foundation of a safe DHCP scope
A DHCP scope should lease only valid host addresses and should exclude infrastructure addresses such as the gateway, servers, printers, access points, or other statically assigned devices.
A mathematically valid host can still be operationally unavailable if it has been reserved for infrastructure.
A calculator can give the range but cannot tell you whether the design is sensible
Suppose a calculator reports that 192.168.40.129–190 are valid hosts in a /26. It does not know whether .129 is already the gateway, whether .150 is reserved for a printer, or whether DHCP is incorrectly leasing static infrastructure addresses. Range math is necessary, but network design adds another layer.
Determine whether a proposed endpoint address is assignable
For 10.10.10.64/28, the network is .64 and the broadcast is .79. Ordinary hosts are .65 through .78. A proposed endpoint address of .64 is therefore invalid in traditional subnetting because it identifies the network. Address .79 is also invalid because it is the broadcast.
The address count and the usable count are not the same
A /27 contains 32 total addresses but traditionally 30 usable host addresses. A /29 contains 8 total and traditionally 6 usable. This is why host-capacity questions should ask whether they mean total addresses or ordinary assignable host addresses.
| Prefix | Total addresses | Traditional usable hosts |
|---|---|---|
| /24 | 256 | 254 |
| /25 | 128 | 126 |
| /26 | 64 | 62 |
| /27 | 32 | 30 |
| /28 | 16 | 14 |
| /29 | 8 | 6 |
| /30 | 4 | 2 |
Swipe horizontally to see the capacity table.
Do not blindly apply the traditional first/last exclusion to every prefix
Most classroom subnet exercises use conventional multiaccess subnets. However, /31 is a special point-to-point case where both addresses can be usable, and /32 identifies a single IPv4 host route. If a problem specifically introduces those prefixes, use the rules appropriate to that context instead of forcing the ordinary network-plus-one/broadcast-minus-one method.
Use three checks to catch a wrong host-range answer
A correct result should satisfy three independent checks: the supplied IP must lie inside the calculated block, the block must contain the expected number of addresses, and broadcast + 1 should equal the next legal subnet boundary.
Use a working client to detect wrong range, scope, or prefix problems
If one client fails, compare its IP, prefix, gateway, and DHCP lease with a known-good peer in the same intended VLAN. A client can have a syntactically valid IP address and still be on the wrong subnet or DHCP scope.
This is why host-range validation should always include the intended network, not just arithmetic.
The client is assigned the network address
Observed: endpoint configured as 192.168.12.64/26.
Calculation: .64 is the network address of the .64–.127 block.
Inference: the address is not an ordinary host assignment in traditional subnetting. Correct the IP before troubleshooting DNS or the Internet.
The DHCP pool accidentally includes the gateway
Observed: router uses 10.10.10.1/24 and DHCP pool starts at 10.10.10.1.
Risk: a client can be offered the router's address, creating a duplicate-IP conflict and first-hop failure.
Correction: exclude the gateway and any other reserved infrastructure addresses.
A proposed gateway is a valid host—but in the wrong subnet
Observed: client is 192.168.50.70/27 and gateway is 192.168.50.1.
Calculation: .70 belongs to network 192.168.50.64/27 with host range .65–.94.
Inference: .1 is a valid IPv4 host address somewhere, but it is not a local host in this client's subnet.
The address is valid but reserved for infrastructure
Observed: DHCP leases 192.168.10.50 to a laptop, but .50 is statically configured on a printer.
Inference: host-range math says .50 is legal, but operational design says it is reserved. Expect duplicate-address symptoms until the pool or reservation is corrected.
Choose the smallest subnet that satisfies a host requirement
If a segment needs 25 ordinary host addresses, /28 is too small because it offers only 14 traditional usable hosts. /27 provides 30 and is a better fit. /26 provides 62, which also works but consumes a larger address block.
This turns host-range calculation into an address-planning skill rather than a standalone math exercise.
Host-range questions often hide inside gateway, DHCP, and wrong-mask scenarios
The exam-style value of range practice is not calculator speed. It is being able to recognize instantly that a gateway is outside the subnet, that a DHCP pool contains a reserved boundary address, or that an endpoint has landed in the wrong scope.
Eight host-range mistakes to eliminate
- Using the network address as an ordinary host.
- Using the broadcast address as an ordinary host.
- Assuming the gateway must always be the first usable address.
- Forgetting to exclude gateway and static infrastructure from DHCP.
- Confusing total address count with usable-host count.
- Assuming every broadcast ends in .255.
- Ignoring earlier-octet subnet boundaries.
- Trusting a calculator result without checking whether it matches the intended network design.
A host-range calculation also predicts whether traffic should stay local
Knowing the valid host range is not only about deciding whether an address can be assigned. It also tells you which destinations belong to the same local subnet. If a client is 192.168.25.150/26, then every address from network .128 through broadcast .191 is inside that /26 block. Ordinary hosts .129 through .190 are therefore local peers. A destination such as .200 is outside the block and should be reached through the default gateway.
This is why range calculation transfers directly into packet-path analysis: the same boundaries used to validate host addresses also determine local-versus-remote behavior.
A large subnet can still have a small usable DHCP pool
Subnet capacity and DHCP capacity are not the same thing. A /24 has 254 traditional usable host addresses, but an administrator may reserve large portions for servers, printers, network devices, or static assignments. If the DHCP pool contains only .100 through .150, that is just 51 possible leases even though the subnet itself supports far more hosts.
This distinction helps separate a true subnet-size limitation from an artificially small or exhausted scope.
Valid does not mean available
A mathematically valid host address can still be unavailable because it is reserved for infrastructure, statically assigned, excluded from DHCP, or already in use. Good address plans typically reserve predictable regions for gateways, servers, network devices, printers, wireless infrastructure, and dynamic clients.
This is the operational layer that a simple subnet calculator cannot infer on its own.
Host-range math helps explain duplicate-IP failures
Suppose a printer is statically assigned 10.20.30.50/24 and the DHCP pool also includes .50. The address is valid for the subnet, but two devices can now claim the same IPv4 address. Symptoms may include intermittent connectivity, ARP-table changes, and traffic reaching the wrong device.
The fix is not to change the subnet mask. The fix is to reserve or exclude the infrastructure address from dynamic assignment.
Host-range math helps choose an efficient prefix
Imagine one segment needs 12 ordinary host addresses and another needs 50. A /28 provides 14 traditional usable hosts, so it can fit the 12-host segment closely. A /26 provides 62 usable hosts, making it a better fit for the 50-host segment. Assigning /26 to both would work mathematically but consume more address space than necessary for the smaller network.
| Need | Candidate | Traditional usable | Fit |
|---|---|---|---|
| 12 hosts | /28 | 14 | Good fit |
| 12 hosts | /27 | 30 | Works, more space |
| 50 hosts | /27 | 30 | Too small |
| 50 hosts | /26 | 62 | Good fit |
Swipe horizontally to compare subnet sizes.
Use one subnet to validate a host, gateway, DHCP pool, and remote destination
This single example demonstrates why host-range math has much higher value than a standalone calculator answer. It lets you validate infrastructure placement, dynamic addressing, individual host assignments, and the forwarding decision for remote traffic.
24 Valid Host Range digital flashcards
Practice network and broadcast boundaries, first/last usable hosts, block sizes, gateway placement, DHCP pools, validation checks, special prefixes, and troubleshooting.