IPv6 Subnet Calculator |
IPv6 Subnet Calculator — What the Results Tell You
IPv6 subnet calculation operates on 128-bit addresses using prefix length notation — /0 through /128 — in place of IPv4's dotted-decimal subnet mask. A /64 prefix reserves 64 bits for the network and leaves 64 bits for host addresses, yielding 264 addresses per subnet. IPv6 has no broadcast address — all addresses in a prefix are usable in principle. The tool outputs two representations of the address per RFC 5952, the network prefix, and the number of available /64 subnets for any shorter-than-/64 allocation.
| Prefix | Typical Assignment | Total Addresses | Standard |
|---|---|---|---|
| /32 | ISP allocation from RIR | 296 | RFC 6177 |
| /48 | Organization / customer site | 280 | RFC 6177 |
| /56 | Residential customer site | 272 | RFC 6177 |
| /64 | Single LAN subnet — SLAAC required | 264 (~18.4 quintillion) | RFC 4291, RFC 4862 |
| /127 | Point-to-point router link | 2 | RFC 6164 |
| /128 | Single host — loopback, anycast | 1 | RFC 4291 |
IPv6 Address Types — Reference Table
IPv6 defines several address categories by prefix range. Knowing which range an address falls into determines how it can be routed and used.
| Prefix | Type | IPv4 Equivalent | RFC |
|---|---|---|---|
| 2000::/3 | Global Unicast (GUA) — publicly routable | Public IPv4 | RFC 4291 |
| fc00::/7 | Unique Local Address (ULA) — private use | RFC 1918 (10.x, 172.16.x, 192.168.x) | RFC 4193 |
| fe80::/10 | Link-Local — single link only, not routed | APIPA (169.254.x.x) | RFC 4291 |
| ::1/128 | Loopback | 127.0.0.1 | RFC 4291 |
| ff00::/8 | Multicast — replaces IPv4 broadcast | 224.0.0.0/4 | RFC 4291 |
| 2001:db8::/32 | Documentation / examples — not routable | 192.0.2.0/24 (TEST-NET) | RFC 3849 |
How to Use the IPv6 Subnet Calculator
Type or paste an address such as 2001:db8::1, or a prefix such as 2001:db8::/48. Compressed, expanded and embedded IPv4 forms (::ffff:192.0.2.1) are accepted; results update as you type.
Read the Range and Size
Plan Subnets
Check an Address
How IPv6 Subnetting Differs from IPv4
IPv6 addresses are 128 bits long (RFC 4291) — four times the width of IPv4's 32-bit address. The address space is 2128, or approximately 3.4 × 1038 addresses. This eliminates the scarcity that drove IPv4's complex subnet planning; a single /48 prefix contains 280 addresses — more than the entire IPv4 internet.
IPv6 has no broadcast address. Broadcast functionality is replaced by multicast (ff00::/8, RFC 4291). This eliminates the network/broadcast address reservations that reduce IPv4 usable hosts — all addresses in an IPv6 prefix are assignable.
IPv6 uses no dotted-decimal subnet mask. The equivalent is the prefix length, written in CIDR notation (e.g. /64). There is no "255.255.255.0" notation in IPv6 — only /0 through /128.
SLAAC (Stateless Address Autoconfiguration, RFC 4862) enables IPv6 hosts to self-configure an address without DHCP. SLAAC requires exactly 64 host bits — meaning the network prefix must be /64. Using longer prefixes (/65 through /127) on a LAN breaks SLAAC and is incompatible with most dual-stack deployments.
Address compression (RFC 5952) removes leading zeros from each 16-bit group and collapses the longest consecutive run of zero groups into :: — which may appear only once. This rule produces a unique canonical form for every address, eliminating notation ambiguity in routing tables, firewall rules, and logs.
Common Uses for an IPv6 Subnet Calculator
ISP address delegation planning. An ISP receives a /32 prefix from their RIR (per RFC 6177) and needs to allocate /48 blocks to enterprise customers and /56 blocks to residential customers. The calculator shows how many /48 subnets fit inside the /32 — 65,536 — and confirms the prefix boundaries before configuring the routing infrastructure.
Firewall ACL documentation. A security engineer writing an IPv6 access control list needs to confirm the canonical compressed form of a prefix before committing it to change control documentation. A typo in hexadecimal — or inconsistent use of compressed versus expanded notation — creates ambiguity in tickets and audit trails. The calculator provides the RFC 5952 canonical form and the fully expanded form for deterministic comparison.
Point-to-point router link addressing. A network engineer configuring an inter-router link assigns a /127 prefix (RFC 6164) instead of a /126, conserving address space. The calculator confirms that a /127 contains exactly 2 addresses with no broadcast — both fully usable — and displays the network prefix for the router configuration.