CALCULATE / IP60BPS / MODULE
IPV6 PREFIX NORMALIZER
Canonicalize, deduplicate and exactly aggregate IPv6 CIDR lists with 128-bit browser-local arithmetic.
ADVERTISEMENT
EXAMPLES
Normalization keeps the exact union of the entered IPv6 prefixes. It never broadens the address set merely to produce fewer rows. Zone IDs and dotted IPv4-mapped notation remain intentionally unsupported.
ADVERTISEMENT
RESULT / EXPLAINED
Exact address math, with operational claims kept separate.
The network-planning tools perform deterministic IPv4/IPv6 arithmetic locally. They describe address-space relationships, not whether a network is deployed correctly.
What is exact
Network boundaries, containment, ranges, prefix lengths, masks and exact aggregation/splitting results come from deterministic address arithmetic.
Canonical output
Normalized network values remove host bits where appropriate. Containment means one calculated address range fully includes another; overlap means ranges intersect.
No live network validation
The browser does not confirm routing tables, VLANs, DHCP, firewall rules, ownership, reachability or whether the calculated prefix is appropriate for your deployment.
Before deployment
Use the arithmetic result as a planning input, then verify it against the real network design, routing/firewall policy and authoritative address allocation.
0BPS SHOWS MEASURED OR CALCULATED FACTS SEPARATELY FROM INTERPRETATION. WHERE A RESULT IS ADVISORY, ESTIMATED OR DESTINATION-SPECIFIC, THE LIMIT IS STATED IN THE TOOL.
REFERENCE / FAQ
COMMON QUESTIONS
What does IPv6 prefix normalization do?
It canonicalizes every input prefix, removes duplicates and contained space, then summarizes the exact same address union with the smallest aligned IPv6 CIDR set it can produce.
Can normalization add IPv6 addresses that were not in my input?
No. The normalizer merges only overlapping or adjacent address space that can be represented exactly. It never broadens the union just to reduce the number of rows.
Why is BigInt required?
IPv6 uses 128-bit addresses. Exact normalization needs integer-safe range boundaries, so the browser uses BigInt instead of floating-point numbers.
Normalization removes duplicate or contained prefixes and re-summarizes only the same IPv6 address union.
BigInt keeps prefix boundaries exact across the full IPv6 address space; no floating-point approximation is used.
PRACTICAL / EXAMPLES
PUT THE NUMBER IN CONTEXT.
Short examples using the same units and assumptions as this module.
2001:db8::/48 plus 2001:db8:0:1::/64 normalizes to the single /48 because the /64 adds no new addresses.
2001:db8::/49 plus 2001:db8:0:8000::/49 aggregates exactly to 2001:db8::/48.