IP Range Expander
Expand IP ranges, wildcards, or CIDR blocks into listing, offering statistics and paginated views.
IP Input Configuration
Formats accepted: 192.168.1.0/24, 10.0.0.5-25, or 172.16.*.*
Host Statistics (CIDR Subnet)
| Network IP / Start | 192.168.1.0 |
| Broadcast IP / End | 192.168.1.255 |
| Subnet Mask | 255.255.255.0 |
| Enclosing Subnet Prefix | /24 |
| Total IP Hosts | 256 |
| Usable Range | 192.168.1.1 – 192.168.1.254 (254 hosts) |
Expanded IP Addresses
Expanding Subnets, Wildcards, and Ranges
This IP Range Expander is a robust network planning tool. It accepts standard CIDR suffix notations (like /24 or /28), wildcard expressions using stars (such as 192.168.1.*), or raw IP address ranges separated by hyphens (e.g. 10.0.0.100 - 150).
By displaying full network statistics, you can quickly locate the Subnet Mask, the Network Identifier, the Broadcast IP Address, and the range of Usable Hosts. Paginated client-side listings prevent application lag even when computing up to 262,144 individual nodes.
Built and maintained by Meet Shah · Last updated
What this tool is used for
- Expanding a CIDR block into individual addresses for an allowlist.
- Producing a list for a tool that will not accept CIDR notation.
- Checking exactly how many addresses a block contains.
- Exporting a range as CSV or JSON for a spreadsheet.
- Confirming the first and last address of a block.
Frequently Asked Questions
- Which range notations does it accept?
- CIDR blocks, explicit `start-end` ranges, the shorthand `192.168.1.10-20` where the last octet alone is given, wildcard forms such as `192.168.1.*`, and a single address. Each is normalised to a first and last address internally.
- What is the enclosing CIDR it reports?
- The smallest single prefix that contains your whole range, found by XOR-ing the endpoints and counting leading zero bits. For an arbitrary range it will usually be larger than the range itself, so do not paste it into a firewall rule expecting an exact match.
- Why is there a limit on how many addresses it lists?
- Rendering is capped at 262,144 addresses, roughly a /14. Beyond that the browser would spend more memory on DOM nodes than the list is worth, and the summary — first, last, mask, count — answers the question anyway.
- Does the expanded list include network and broadcast?
- Yes — it enumerates every address in the range, which is what you want for scanning or allow-listing. If you need only assignable hosts, drop the first and last entries for any prefix shorter than /31.
- Is a reversed range accepted?
- No. A range whose start is above its end is rejected rather than silently swapped, because the usual cause is a typo in one octet and quietly reordering it would hide the mistake behind a plausible-looking result.
- Can I get the output as CSV or JSON?
- Yes, alongside the one-per-line list. JSON suits feeding a script; the plain list pastes directly into most firewall and scanner configuration files, which expect one address per line.
Common errors and gotchas
- Expanding a large block, where a /16 is 65,536 addresses and a /8 is millions.
- Including the network and broadcast addresses in a host list where they do not belong.
- Expanding an IPv6 block, which is almost never finite enough to enumerate.
- Pasting a very long list into a config that has a size limit.
- Assuming every address in the block is in use, which a scan would establish.