IPv4 Range Expander

Network

Expand CIDR notation to a full list of individual IP addresses with clean bulk export, ready for firewall rules, network scans and access control lists.

11 IPs · 3 CIDRs
CIDR COVERAGE
192.168.1.0/29192.168.1.8/31192.168.1.10/32
All Addresses (11)
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.10

About IPv4 Range Expander

Operations and security work often needs a range of IPs (like 192.168.1.10-192.168.1.50 or 10.0.0.0/24) expanded into a full list of individual addresses. This tool parses a start-end interval or CIDR block and enumerates every IPv4 address within it, locally in your browser — useful for bulk-importing allowlists, building scan targets, or verifying coverage. For example, expanding 192.168.1.10-192.168.1.20 yields an 11-address list for ACLs or batch script arguments. Expanding an address block into a concrete list of addresses is a frequent step when writing firewall rules, reconciling allowlists, or checking whether a given address falls inside a range. Doing prefix-to-range arithmetic mentally is hard, especially when the prefix length is not a multiple of eight, and the boundary addresses are where mistakes cluster. The arithmetic has two steps: derive the network and broadcast addresses from the prefix length, which fixes the usable range, then optionally enumerate every address in it. The key insight is the link between prefix length and address count: dropping one prefix bit doubles the number of addresses. Going from a /24 to a /23 is not "a little wider" but a jump from 256 addresses to 512, with entirely different security implications. Practical notes: Write the narrowest block possible in an allowlist, using a thirty-two bit prefix for a single address and widening only when a range is genuinely required, and always check the first and last address after widening, because including one extra address in effect admits an entire block. When the expanded result is long, export it to a file rather than copying from the page, where rows get missed or trailing whitespace creeps in. The reverse operation, reducing many addresses to the fewest possible blocks, is address aggregation and needs a dedicated tool rather than manual effort. Limits: Private ranges are reused across organisations, so the same private address means different things in each, and exchanging allowlists across organisations requires confirming the address spaces do not overlap or rules that look correct silently fail to admit traffic. Reserved and multicast ranges should not be used for business addressing, and finding them in a rule usually signals a configuration mistake. On volume, a very short prefix expands into an enormous list with no practical value that also slows the tool and the downstream device, so the plan should avoid it from the start. Data and privacy: address planning reveals network structure and counts as internal material. This tool performs the arithmetic and expansion in the browser without uploading, and it can be used offline for internal planning, keeping internal topology out of a third-party service's query log. The most common misuse is writing a wider block than needed in an allowlist: going from a twenty-four to a twenty-three bit prefix is not a small increment but two hundred and fifty-six addresses becoming five hundred and twelve, with entirely different security meaning. Another is importing a long expanded list straight into a firewall, which may exceed the per-rule entry limit, and most devices reject the network and broadcast addresses so their presence fails the whole import.

How It Works Internally

Expansion has two steps: derive the network and broadcast addresses from the prefix to fix the usable range, then enumerate. The key is separating a range from a list — firewalls usually accept range fields, while enumerating is verbose and easily exceeds a device limit per rule; when a list is needed, note that most devices reject the network and broadcast addresses and their presence can fail the whole import.

Input192.168.1.0/30
OutputUsable 192.168.1.1–192.168.1.2, two hosts (.0 and .3 are network and broadcast)

Measured on This Page

Aggregation accuracyAll 9 ranges satisfy exact coverage, zero overlap and minimal block count
Typical result192.168.1.0–10 → 3 blocks (/29 + /31 + /32); 172.16.0.0–172.16.15.255 → a single /20
Defect fixed hereAddresses ≥128.0.0.0 could not be aggregated at all before (192.168.1.0–10 produced eleven /32 blocks) — 32-bit signed overflow
Size limitUp to 4,096 addresses per run; beyond that the total is reported instead of truncating
Google, last 90 days3 clicks / 29 impressions / average position 16.4

Writing 192.168.1.0–10 as eleven firewall rules and as three CIDR blocks means the same thing, but the latter costs 8 fewer rows and 8 fewer comparisons per match. If you implement this yourself in JS, avoid 32-bit signed arithmetic: 1 << 31 goes negative and cur & mask returns a signed value, so every address at or above 128.0.0.0 — including the ubiquitous 192.168.x — computes wrongly.

How this was measured: Measured nine address ranges and verified each with an independent checker that expands every /N block into a set of addresses, then asserts three things: the union equals the original range exactly, blocks do not overlap, and the block count equals the greedy minimum. Two invalid inputs (out-of-range IP, reversed ends) were also tested. · Measured 2026-10-28

How to Use

  1. Open "IPv4 Range Expander"
  2. Enter the start and end addresses of the range
  3. The header shows the total count and CIDR block count
  4. Review the CIDR cover, then the expanded address list
  5. Copy either the CIDR blocks or the full address list

Use Cases

  • Allowlist import — Expand a CIDR into individual IPs for firewalls or gateways that only accept single addresses.
  • Scan target list — Generate a complete list of target IPs for port scanning or asset discovery.
  • Range verification — Confirm a CIDR's actual first/last address and total count match expectations.
  • Bulk configuration — Prepare per-address lists for DHCP reservations, monitoring probes, and the like.
  • Notation cross-check — Reconcile the same range between start-end and CIDR notations.
  • Security audit — Expand a CIDR into a full IP list to verify coverage against a known asset inventory.
  • DHCP pool — Generate the full address range of a subnet to compare with the configured DHCP scope.
  • NAT rule mapping — List every IP in a translated range to confirm one-to-one NAT assignments don't overlap.

FAQ

Does CIDR expansion include network and broadcast addresses?

By default it lists every address in the block, including network and broadcast. If you need only assignable hosts, drop the first and last addresses from the result.

Can it expand very large ranges?

Yes, but be careful. A /16 holds over 65,000 addresses and a /8 over 16 million; enumerating each in a browser uses lots of memory, so keep it within /16.

Must start and end be in the same subnet?

No. Any valid start/end IPv4 works; the tool enumerates by 32-bit integer in ascending order and lists across subnets correctly.

How is this different from subnet calculation?

Subnet calculation gives summary info like network, broadcast, and host count; this tool actually lists every address. For summaries, use the IPv4 Subnet Calculator.

What is the output order?

Ascending by the address's 32-bit integer value, matching the natural dotted-decimal order, which makes comparison and deduplication easy.

The expansion produced far more addresses than expected. Is it wrong?

Usually a misreading of the prefix length. Every bit removed from the prefix doubles the count, so widening twenty-four to twenty-three is not a small change but two hundred and fifty-six becoming five hundred and twelve; and a mask set beyond the host portion also includes the network and broadcast addresses, which are not usable for hosts. Confirm the prefix matches the expected count, then check the first and last address.

Can the expanded list go straight into a firewall?

Yes, after two checks. First, decide whether the list should include the network and broadcast addresses, since most devices reject or ignore them and their presence can fail the import. Second, confirm the entry count is within the device limit for a single rule, using a range field instead of a long enumeration when it is not. Validate on a test device before pushing to production.

What happens if the start IP is larger than the end IP?

The tool reports the inverted range instead of silently swapping, because a silent swap can hide input mistakes. Remember the expanded count equals the numeric difference plus one — huge ranges show a count rather than a full list.