CIDR notation, how subnet maths works, and what to check when you split a network
In 192.168.1.10/24, the /24 says that the first 24 of the address's 32 bits identify the network and the remaining 8 identify a host inside it. Writing an address with its prefix length like this is CIDR notation, defined in RFC 4632. This guide walks through how the network and broadcast addresses fall out of simple bit operations, gives a size table for common prefixes, splits a /24 into smaller subnets and covers the planning mistakes that come up again and again.
Network address is AND, broadcast is OR
All of the calculation is bitwise arithmetic on the address and the mask. Taking 192.168.1.100/26 as the example, with every value computed by this tool's own functions:
- A /26 prefix is a mask of 26 ones followed by zeros: 11111111.11111111.11111111.11000000, which is 255.255.255.192.
- Write the address in binary: 192.168.1.100 is 11000000.10101000.00000001.01100100.
- Address AND mask gives the network address. In the last octet, 01100100 AND 11000000 = 01000000, so the network is 192.168.1.64.
- Invert the mask to get the wildcard (0.0.0.63) and OR it with the network address to get the broadcast address: 192.168.1.127.
- Everything in between is the host range: 192.168.1.65 to 192.168.1.126. That's 2^(32−26) = 64 addresses, minus two, leaving 62 usable hosts.
Prefix sizes at a glance
Each step up in prefix length halves the block. Usable hosts exclude the network and broadcast addresses, except for /31 and /32, which RFC 3021 and common practice treat differently.
| Prefix | Subnet mask | Total addresses | Usable hosts |
|---|---|---|---|
| /16 | 255.255.0.0 | 65,536 | 65,534 |
| /20 | 255.255.240.0 | 4,096 | 4,094 |
| /22 | 255.255.252.0 | 1,024 | 1,022 |
| /23 | 255.255.254.0 | 512 | 510 |
| /24 | 255.255.255.0 | 256 | 254 |
| /25 | 255.255.255.128 | 128 | 126 |
| /26 | 255.255.255.192 | 64 | 62 |
| /27 | 255.255.255.224 | 32 | 30 |
| /28 | 255.255.255.240 | 16 | 14 |
| /29 | 255.255.255.248 | 8 | 6 |
| /30 | 255.255.255.252 | 4 | 2 |
| /31 | 255.255.255.254 | 2 | 2 (point-to-point link) |
| /32 | 255.255.255.255 | 1 | 1 (single host) |
Splitting a /24 into /27s
Dividing 192.168.1.0/24 into /27 blocks gives 2^(27−24) = 8 subnets of 32 addresses each, 30 of them usable. This is what the tool's split feature returns:
| # | Network | Host range | Broadcast |
|---|---|---|---|
| 1 | 192.168.1.0/27 | 192.168.1.1 – .30 | 192.168.1.31 |
| 2 | 192.168.1.32/27 | 192.168.1.33 – .62 | 192.168.1.63 |
| 3 | 192.168.1.64/27 | 192.168.1.65 – .94 | 192.168.1.95 |
| 4 | 192.168.1.96/27 | 192.168.1.97 – .126 | 192.168.1.127 |
| 5 | 192.168.1.128/27 | 192.168.1.129 – .158 | 192.168.1.159 |
| 6 | 192.168.1.160/27 | 192.168.1.161 – .190 | 192.168.1.191 |
| 7 | 192.168.1.192/27 | 192.168.1.193 – .222 | 192.168.1.223 |
| 8 | 192.168.1.224/27 | 192.168.1.225 – .254 | 192.168.1.255 |
Planning mistakes to avoid
- Assuming the network address ends in .0. As shown above, the network for 192.168.1.100/26 is .64. Below /24, block boundaries fall on multiples of 128, 64, 32 and so on.
- Sizing for exactly today's hosts. Fifty devices fit in a /26 (62 usable), but once you allow for the gateway, DHCP headroom and growth, the next size up, a /25, is often the better choice. Some clouds reserve addresses in every subnet, AWS VPC reserves five, so the usable count is lower still.
- A start address that isn't on a boundary. Enter 192.168.1.32/26 and the tool reports the network as 192.168.1.0, because a /26 has to start on a multiple of 64. If you really meant a block starting at .32, you wanted a /27.
- Overlapping ranges. If your office uses 192.168.0.0/16 and a partner's VPN uses 192.168.1.0/24, one contains the other and routing breaks. Check every network you'll connect to before you pick a private range.
- Non-contiguous masks. Something like 255.0.255.0 can't be written as a CIDR prefix and isn't a valid subnet mask, so the tool rejects it.
Check the address type too
The address type shown with each result is based on the special-purpose ranges listed in RFC 6890 and related RFCs. Internal networks should use the RFC 1918 private ranges: 10.0.0.0/8 (about 16.7 million addresses), 172.16.0.0/12 (about 1 million) and 192.168.0.0/16 (65,536). The middle one runs from 172.16 to 172.31, so 172.32.x.x is public address space, a detail that catches people out.
100.64.0.0/10 is shared address space for carrier-grade NAT (RFC 6598); if your router's outside address falls in it, your ISP hasn't given you a public IP. 169.254.x.x is a link-local address that a device assigns itself when DHCP fails. And for documentation and examples, use the reserved ranges in RFC 5737, such as 203.0.113.0/24, so you never collide with a real network.
Sources: RFC 4632 — Classless Inter-domain Routing (CIDR) · RFC 1918 — Address Allocation for Private Internets · RFC 3021 — Using 31-Bit Prefixes on IPv4 Point-to-Point Links · RFC 6890 — Special-Purpose IP Address Registries · AWS — Subnet CIDR blocks (reserved addresses)
Last reviewed: 2026-11-22