Skip to content
ZeroServer.tools

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 / Start192.168.1.0
Broadcast IP / End192.168.1.255
Subnet Mask255.255.255.0
Enclosing Subnet Prefix/24
Total IP Hosts256
Usable Range192.168.1.1 – 192.168.1.254 (254 hosts)

Expanded IP Addresses

Showing 256 matching IPs
192.168.1.0192.168.1.1192.168.1.2192.168.1.3192.168.1.4192.168.1.5192.168.1.6192.168.1.7192.168.1.8192.168.1.9192.168.1.10192.168.1.11192.168.1.12192.168.1.13192.168.1.14192.168.1.15192.168.1.16192.168.1.17192.168.1.18192.168.1.19192.168.1.20192.168.1.21192.168.1.22192.168.1.23192.168.1.24192.168.1.25192.168.1.26192.168.1.27192.168.1.28192.168.1.29192.168.1.30192.168.1.31192.168.1.32192.168.1.33192.168.1.34192.168.1.35192.168.1.36192.168.1.37192.168.1.38192.168.1.39192.168.1.40192.168.1.41192.168.1.42192.168.1.43192.168.1.44192.168.1.45192.168.1.46192.168.1.47192.168.1.48192.168.1.49192.168.1.50192.168.1.51192.168.1.52192.168.1.53192.168.1.54192.168.1.55192.168.1.56192.168.1.57192.168.1.58192.168.1.59192.168.1.60192.168.1.61192.168.1.62192.168.1.63192.168.1.64192.168.1.65192.168.1.66192.168.1.67192.168.1.68192.168.1.69192.168.1.70192.168.1.71192.168.1.72192.168.1.73192.168.1.74192.168.1.75192.168.1.76192.168.1.77192.168.1.78192.168.1.79192.168.1.80192.168.1.81192.168.1.82192.168.1.83192.168.1.84192.168.1.85192.168.1.86192.168.1.87192.168.1.88192.168.1.89192.168.1.90192.168.1.91192.168.1.92192.168.1.93192.168.1.94192.168.1.95192.168.1.96192.168.1.97192.168.1.98192.168.1.99
Page 1 of 3

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.

Related Developer Utilities tools

Private & free — this tool runs entirely in your browser.

IndieKitShip your Next.js startup in days.affiliate