← Back to Main Calculator

IPv6 Subnet Prefix Calculator & SLAAC Planner

Split delegated prefixes into /64 subnets, convert compressed and expanded IPv6 text, and plan SLAAC vs. stateful DHCPv6 scopes.

100% Client-Side Processing — Enterprise IPv6 addressing schemes are computed completely in your web browser. No input ever leaves this page.

Source / Parent
-
Child Subnets
-
First / Last Subnet
-
Subnet-ID bits (parent → child)
-
Subnet listPage 1 / 1
#Subnet (CIDR)First addressLast address

How to Split an Enterprise IPv6 /48 Prefix into /64 Subnets

An enterprise /48 delegation contains 16 bits of subnetting headroom: 264−48 = 65,536 possible /64 subnets. Each increment of the subnet ID (bits 49–64) moves the next /64 exactly 264 addresses upstream. In hexadecimal terms this is a one-unit bump of the fourth hextet: 2001:db8:abcd:0000::/64, 2001:db8:abcd:0001::/64, and so on up to 2001:db8:abcd:ffff::/64.

When you slice a /52 instead, exactly 4,096 /64 subnets fall out; a /56 yields 256. The math is always 2childPrefix − parentPrefix. This calculator performs that arithmetic on 128-bit integers with JavaScript BigInt so no precision is lost at /128 boundaries, and it aligns every child subnet to a clean network bit boundary.

SLAAC vs. Stateful DHCPv6 vs. Stateless DHCPv6

MechanismAddress sourceRequired prefixAssignment / leaseOptions (DNS, NTP)
SLAACRA prefix + interface identifier (EUI-64 / privacy)Exactly /64None — host self-assignsVia RA option (RDNSS) or combo with stateless DHCPv6
Stateful DHCPv6Central server pool (IA_NA)/64 or narrower scopes (/112, /120)Lease with timers; auditableYes — via DHCPv6 options
Stateless DHCPv6SLAAC for address, DHCP only for optionsExactly /64NoneYes — DNS, NTP, SIP via DHCPv6

The practical consequence of the /64 rule: exactly one routed subnet fits in a /64 LAN segment, so the /48 delegation of 65,536 subnets is what most ISPs hand to enterprise fiber customers. The planner tab above shows the exact /64 inventory you get from your /48, /52 or /56, plus the finite address window DHCPv6 manages in a /112 or /120 scope.

How SLAAC Addresses Are Built: 64-Bit Prefix + Interface Identifier

SLAAC concatenates the router's 64-bit prefix and a 64-bit interface identifier. If the identifier is derived from a MAC address (EUI-64), the host inserts ff:fe into the middle of the 48-bit MAC (for example 00:1A:2B:3C:4D:5E → 021A:2BFF:FE3C:4D5E) and flips the 7th bit (the universal/local bit) to mark the address as locally generated, producing fe80::21a:2bff:fe3c:4d5e. Hosts using privacy extensions (RFC 8981) instead rotate random lower-64 bits to defeat tracking — both techniques still require the prefix to fit entirely inside the first 64 bits. The step-by-step bit-flip math is covered by the separate EUI-64 Calculator.

Frequently Asked Questions

What is the difference between a /48, /52, /56 and /64 IPv6 prefix?
A prefix length fixes how many /64 subnets it can hold: a /48 holds 65,536, a /52 holds 4,096, a /56 holds 256, and a /64 holds exactly one. LIRs assign /32 or /48 per site, RFC 6177 recommends /56 for home broadband, and enterprise engineers typically plan /48s per region and /56s per branch so every floor segment can still reach /64 depth.
Why does IPv6 not use a dotted-decimal subnet mask like IPv4?
IPv6 addresses are 128-bit hexadecimal values, so an IPv4-style dotted mask would be meaningless. Every IPv6 interface and routing table entry carries the prefix length in CIDR notation (<address>/<length>), and tools like this one normalize everything to /64 subnet boundaries.
How do I convert a compressed IPv6 address back to its full 8-hextet form?
Expand the single :: into enough zero hextets to reach eight total, then pad every hextet back to four digits. For example 2001:db8::1 becomes 2001:0db8:0000:0000:0000:0000:0000:0001. The Format Converter tab performs this in both directions for entire lists at once.
When should I use a /112 or /120 scope for stateful DHCPv6?
A /112 scope holds 65,536 addresses and a /120 scope holds 256 — both are still far larger than any LAN needs, but they keep the address pool tight, make DHCPv6 leases auditable, and free the rest of the /64 for future split routing. Point-to-point links and infrastructure addresses often use /120, while user LANs commonly get a /112 or plain /64.