How to use the CIDR aggregator
- Paste your networks, for example from a firewall address group, an allowlist or a cloud provider's published ranges.
- Select Aggregate. Invalid entries are listed with their line numbers and skipped.
- Copy or download the result. IPv4 networks are listed first, then IPv6.
What gets merged
- Duplicates: the same network listed twice.
- Overlaps:
10.0.0.0/24already contains10.0.0.128/25, so the /25 disappears. - Adjacent blocks:
10.0.0.0/24and10.0.1.0/24become10.0.0.0/23.
The result always covers exactly the same addresses as the input; nothing is added. That is why 10.0.1.0/24 and 10.0.2.0/24 stay as two entries: a single /23 would have to start at 10.0.0.0 or 10.0.2.0 and would include addresses you did not list.
Entries with host bits set
An entry such as 192.168.1.10/24 has bits set after the prefix. The tool treats it as the network it belongs to, 192.168.1.0/24, and lists it as a warning so you can check the source data.
IPv6 output
IPv6 networks are written in the RFC 5952 recommended form: lowercase, no leading zeros, and the longest run of zero groups shortened to ::. That makes output from different sources directly comparable.
Where this helps
- Tidying firewall address objects and groups before a firewall rule review.
- Shortening allowlists for SaaS or cloud services, where some products limit the number of entries.
- Checking route summaries before configuring them.
Frequently asked questions
Does aggregation change which addresses are allowed?
No. The output covers exactly the same addresses as the input; it is just a shorter list.
Why are two adjacent /24 networks not merged?
Two blocks can only become one larger block if together they form an aligned power-of-two range. 10.0.1.0/24 and 10.0.2.0/24 are adjacent but not aligned, so merging them would add addresses.
Can I mix IPv4 and IPv6?
Yes. Each family is aggregated separately and IPv4 is listed first.