WebToolArcPractical guide and verification
Confirm the address family and prefix length
IPv4 and IPv6 prefixes use different address widths, and the allowed prefix range depends on the family. Treat the slash length as part of the network definition and reject values that are outside the family range instead of clipping them silently.
Know which range definition the downstream system expects
For IPv4, older subnet conventions distinguish network and broadcast addresses from usable host addresses, while point-to-point and other modern cases can follow different rules. Keep total address range separate from any usable-host convention.
Use the normalized network address for comparison
A CIDR value can be typed with host bits set. Normalizing to the network boundary makes overlapping-range checks and routing comparisons easier to audit because equivalent prefixes are represented consistently.
Treat huge IPv6 counts as exact integers
IPv6 ranges can contain values far beyond ordinary JavaScript floating-point precision. Preserve address counts and endpoints with integer-safe or bitwise address logic rather than converting the full count into an imprecise Number.
Verify endpoints with a second representation
For an important routing or firewall change, compare the calculated first and last address against a trusted network library or device configuration and confirm the intended prefix. A one-bit prefix error can expand the range dramatically even when the endpoints look superficially similar.