Canonical IPv6 Subnet
{{ result.canonicalCidr }}
{{ result.secondaryLine }}
{{ result.scopeLabel }} {{ result.hostBits }} host bits {{ result.nibbleAligned ? 'Nibble-aligned rDNS' : 'Non-nibble rDNS' }} {{ result.statusText }}
Example: 2001:db8::1234/64.
Accepted: 0-128; ignored when a typed CIDR suffix is honored.
/
On honors /64 in the address; Off uses Prefix length.
{{ use_input_prefix ? 'On' : 'Off' }}
Choose Custom to keep manual values.
Select Match current prefix or a /48-/127 planning boundary.
Decimal slot, for example 0, 3, or 12.
Decimal offset from 0; leave blank for default samples.
Accepted: 00:11:22:33:44:55 or 0011.2233.4455.
On shows a warning for non-canonical but valid IPv6 text.
{{ enforce_rfc5952 ? 'On' : 'Off' }}
Metric Value Copy
{{ row.label }} {{ row.value }}
Field Value Copy
{{ row.label }} {{ row.value }}
Target Subnets from current Addresses per subnet Typical use Copy
/{{ row.target }} {{ row.subnetCount }} {{ row.addressesPerSubnet }} {{ row.useCase }}
Field Value Copy
{{ row.label }} {{ row.value }}
Field Value Copy
{{ row.label }} {{ row.value }}
Target Relationship Anchor CIDR / span Scale or slot Operational note Copy
/{{ row.target }} {{ row.relationship }} {{ row.anchor }} {{ row.scale }} {{ row.note }}
Address role Canonical Expanded Copy
{{ row.label }} {{ row.canonical }} {{ row.expanded }}
Field Value Copy
{{ row.label }} {{ row.value }}
Field Value Copy
{{ row.label }} {{ row.value }} 

      

    


  



                

                

                    

                        

                            Tags: IP Addressing, Networking, Sysadmin
                        

                        

                            Export to PDF
                            Fullscreen
                        

                    

                

            

        

    


        
    

        

        

            


                

                    

                    
                


                

                

                
            

            

                
                
            

        

    


    

        

                                                                                                                                                                                                                                                                        
        

            

                
                
                
                
            

            

                
                
            

            

                

                    

                        

                            
                            
                        

                    

                    

                        

                            
                            
                        

                    

                    

                        

                            
                            
                        

                    

                    

                        

                            
                            
                        

                    

                    

                        
                        
                    

                    

                        
                        

                            
                            
                        

                    

                    

                        
                        

                            
                            
                        

                    

                    

                        
                        

                            
                            :
                            
                        

                    

                    

                        
                        

                            
                            
                        

                    

                    

                        
                        
                    

                    

                        
                        
                    

                    

                        

                            
                            
                        

                    

                    

                        
                        
                    

                    

                        
                        
                    

                

            


            
        

    



    

        

  

    

IPv6 subnet planning starts with a 128-bit address and a prefix length. The prefix marks the network portion, while the remaining bits describe the addresses inside that block. A small change in prefix length can move the boundary from a broad delegation to a single host route, so the written CIDR must match the operational intent.

    
Several IPv6 conventions matter before any allocation is copied into DNS, routing, or firewall notes. A /64 is the common LAN boundary for stateless address autoconfiguration, /127 is often used for point-to-point links, and /128 names one address. Reverse DNS also works on hexadecimal nibbles, so prefixes that are not multiples of four need extra care when planning ip6.arpa delegation.

    
Address identity matters as much as size. Documentation, loopback, link-local, unique-local, multicast, transition, and IANA special-purpose ranges should not be treated as ordinary global unicast space. A subnet count can still be mathematically correct while the address family is wrong for deployment.

  






  

    
Technical Details

    
The calculation masks the host bits below the selected prefix, producing a normalized network address and a last address in the same block. RFC 5952-style text compression is useful for display, but the underlying value is always the full 128-bit integer.

    
Reverse DNS is built from the hexadecimal form of the address. Each fixed nibble becomes one label under ip6.arpa, ordered from least significant fixed nibble to most significant fixed nibble. Prefixes such as /48, /56, /60, /64, /96, and /112 land cleanly on nibble boundaries; a /57 or /65 does not.

    

      

        
        
          
Network valueaddress AND prefix mask

          
Last valuenetwork OR host mask

          
Host bits128 minus prefix length

          
Child subnet count2 raised to the target-prefix minus current-prefix bit gap

          
Reverse zonefixed hexadecimal nibbles reversed under ip6.arpa

        
      

    

    
The implementation also classifies the entered address against well-known IPv6 ranges. It uses IANA special-purpose entries and RFC-based fallbacks for multicast, link-local, unique-local, and global-unicast style space. That classification drives warning text such as documentation-only, lab-only, transition range, translation range, or typical host subnet size.

  






  

    
Everyday Use & Decision Guide

    
Start with the exact address or CIDR you received from your provider, lab plan, or router. If the input already contains a suffix, leave CIDR suffix handling enabled so the visible prefix comes from the pasted value. Use the separate prefix field when you are testing how the same address behaves at a different boundary.

    
    
      
  • Use Prefix Metrics to confirm the canonical CIDR, host-bit count, and size of the range.
    • 
      
  • Use Range Identity before deployment. A match to documentation or translation space changes the meaning of every other row.
    • 
      
  • Use Allocation Planner and Target Prefix Plan when carving a provider block into /64 LANs, /127 links, or narrower service routes.
    • 
      
  • Use Reverse DNS before delegating PTR zones. Non-nibble results need a plan outside simple zone cuts.
    • 
      
  • Use Address Samples and Interface ID Plan to inspect one host offset or an optional modified EUI-64 address from a MAC address.
    • 
    

    
Do not read a huge address count as permission to allocate casually. The better check is whether the prefix length, address family, reverse zone, and target plan all say the same thing.

  






  

    
Step-by-Step Guide

    
    
      
  1. Enter an IPv6 literal such as 2001:db8:12:3400::1234/56.
    2. 
      
  2. Choose whether a pasted CIDR suffix should override the prefix field.
    3. 
      
  3. Open Advanced when you need a target prefix, target subnet index, sample host offset, or EUI-64 MAC example.
    4. 
      
  4. Review the status badges for scope, host bits, reverse-DNS alignment, and special-range warnings.
    5. 
      
  5. Copy individual rows, export CSV or DOCX from the relevant tab, or keep the JSON payload for a runbook.
    6. 
    

  






  

    
Interpreting Results

    
Canonical IPv6 Subnet is the normalized network and prefix, not necessarily the literal address you typed. If the entered address has host bits set, the canonical subnet moves down to the true network boundary.

    
Nibble-aligned rDNS means the prefix can map directly to a clean ip6.arpa zone. Non-nibble rDNS means the next hex label covers more addresses than the selected prefix, so delegation or record generation needs special handling.

    
Target Prefix Plan changes meaning depending on the target. If the target prefix is longer than the current prefix, the tool selects a child subnet by index. If it is shorter, the result is the containing parent and the slot position of the current block inside it.

  






  

    
Worked Examples

    
Provider /56 to LAN /64s. Enter 2001:db8:abcd:1200::/56 and target /64. The planner shows 256 child /64 blocks, the first child, the last child, and the selected child if you set a target subnet index.

    
Point-to-point link. Enter a routed address and set the prefix to /127. The status shifts to a point-to-point profile, and the host-bit count drops to one. That is useful for infrastructure links, not for a normal SLAAC LAN.

    
Reverse-DNS problem. A /61 can be valid routing policy, but Reverse DNS reports a partial nibble window. Use that warning before promising a simple delegated zone.

  






  

    
FAQ

    
Why does the canonical subnet differ from the address I typed?
The address can contain host bits. The calculator clears those bits to show the actual network boundary for the chosen prefix.

    
Does a /64 always mean the network is public?
No. Prefix length describes size. The range identity tab tells you whether the address is global unicast, unique-local, link-local, documentation, or another special family.

    
Why is reverse DNS tied to nibbles?
IPv6 PTR zones are written from hexadecimal nibbles under ip6.arpa. Four prefix bits equal one hex digit, so multiples of four are clean delegation points.

    
Can I use EUI-64 output as the final host address?
Treat it as a planning sample. Modern networks may use privacy or stable opaque interface identifiers instead of MAC-derived addresses.

  






  

    
Glossary

    

      
CIDR
Address plus prefix length, such as 2001:db8::/32.

      
Prefix length
The number of fixed network bits from the left side of the 128-bit address.

      
ip6.arpa
The reverse-DNS tree used for IPv6 PTR records.

      
Interface ID
The host-side portion of an IPv6 address, commonly 64 bits on LAN subnets.

    

  






  

    
References