The /7 subnet
A /7 subnet uses the mask 254.0.0.0 and holds 33,554,432 addresses, 33,554,430 of them usable.
Reference data last reviewed:
The /7 mask is 7 network bits followed by 25 host bits, for a total of 32 bits.
A /7 is a very large IPv4 block. Its mask is 254.0.0.0 and it holds 33,554,432 addresses, which puts it at the scale of a regional allocation or an entire private supernet rather than a single LAN.
Networks this size are almost always carved into smaller subnets before use. You will see a /7 as an aggregate route or a private-address supernet such as 10.0.0.0/8, not as a single broadcast domain.
Below you can see the exact network, broadcast, and host range for any /7 you enter, calculated instantly in your browser.
Calculate a /7 network
Accepts CIDR (192.0.2.0/24), IP + mask (192.0.2.0 255.255.255.0), or a bare IP (defaults to /24).
00001010.00000000.00000000.0000000011111110.00000000.00000000.00000000Example: 10.0.0.0/7
Taking 10.0.0.0/7 as a worked example, the block breaks down like this:
| Network address | 10.0.0.0 |
|---|---|
| Usable range | 10.0.0.1 - 11.255.255.254 |
| Broadcast address | 11.255.255.255 |
| Total addresses | 33,554,432 |
| Usable hosts | 33,554,430 |
| Size | 2 class A blocks |
A note on the example: 10.0.0.0 is in 10.0.0.0/8, private-use space under RFC 1918. The largest private range, 16,777,216 addresses. The usual choice for a big internal network. Every example on this site uses reserved space on purpose, so nothing here points at somebody's real network.
Splitting a /7 into smaller subnets
Borrowing bits from the host part doubles the number of subnets and halves the size of each one. This is what a /7 looks like at the next 4 prefix lengths.
| Split into | Subnets | Mask | Usable hosts each |
|---|---|---|---|
| /8 | 2 | 255.0.0.0 | 16,777,214 |
| /9 | 4 | 255.128.0.0 | 8,388,606 |
| /10 | 8 | 255.192.0.0 | 4,194,302 |
| /11 | 16 | 255.224.0.0 | 2,097,150 |
Each subnet has to start on a multiple of its own size, which is what keeps the blocks from overlapping. Working the other way, from a host count back to a prefix, is what subnet by host count is for.
Do this from the terminal
The same numbers are available as keyless JSON, and there are good local tools that need no network at all. Naming them costs nothing and is more useful than pretending this page is the only option.
curl -s https://subnetkit.dev/api/cidr/7.json | jq # or locally, with no network at all: ipcalc 10.0.0.0/7 sipcalc 10.0.0.0/7
ipcalc ships in most Linux distributions and sipcalc handles IPv4 and IPv6. The SubnetKit API is the one to reach for in a build step or a script that wants the same values this page shows.
Frequently asked questions
What is the subnet mask for a /7?
A /7 uses the subnet mask 254.0.0.0. Its wildcard mask, used in access lists, is 1.255.255.255.
How many hosts are in a /7 subnet?
A /7 has 33,554,432 total addresses and 33,554,430 usable hosts (the total minus the network and broadcast addresses, except for /31 and /32).
What is a /7 used for?
Very large network. It is equivalent to 2 class A blocks.
How do I calculate a /7 network?
Set the host bits to zero for the network address and to one for the broadcast address. The calculator on this page does it for any /7 block you enter.
How many /8 subnets fit in a /7?
2, each with 16,777,214 usable hosts and the mask 255.0.0.0. Every extra bit you borrow doubles the number of subnets and halves the size of each one.
Opening a port on a /7
A firewall rule needs two halves: the range and the port. The wildcard mask 1.255.255.255 matches this whole block in an access list. For the other half, the port number reference lists what each TCP and UDP port carries and whether it is encrypted by default, so you can tell what you are about to expose to 33,554,430 addresses.
Sources
The arithmetic on this page follows the documents below. Every number is computed from the prefix length rather than stored, and the calculation is covered by tests over all 33 prefixes.
- RFC 4632: Classless Inter-domain Routing (CIDR), the address assignment and aggregation plan
- RFC 1878: Variable Length Subnet Table for IPv4
- RFC 3021: Using 31-bit prefixes on IPv4 point-to-point links
- RFC 1918: Address allocation for private internets
- RFC 6598: IANA-reserved IPv4 prefix for shared address space (carrier-grade NAT)
- RFC 5737: IPv4 address blocks reserved for documentation
- IANA IPv4 Special-Purpose Address Registry
Spotted something wrong? Tell us and it gets corrected. How the data is maintained is described on the about page.