Prefix sizes
IPv6 prefixes are usually planned on nibble boundaries (multiples of 4) so that each step is one hex digit and reverse DNS delegation stays clean. The /64 column is the number of LAN-sized subnets the prefix holds.
| Prefix | Addresses | /64 subnets | Typical use |
|---|---|---|---|
| /3 | 2^125 | 2^61 | Global unicast space (2000::/3) |
| /8 | 2^120 | 2^56 | |
| /12 | 2^116 | 4,503,599,627,370,496 | Typical regional registry allocation |
| /16 | 2^112 | 281,474,976,710,656 | |
| /19 | 2^109 | 35,184,372,088,832 | |
| /20 | 2^108 | 17,592,186,044,416 | |
| /24 | 2^104 | 1,099,511,627,776 | |
| /29 | 2^99 | 34,359,738,368 | Common minimum ISP allocation |
| /32 | 2^96 | 4,294,967,296 | Typical ISP allocation (LIR) |
| /36 | 2^92 | 268,435,456 | |
| /40 | 2^88 | 16,777,216 | |
| /44 | 2^84 | 1,048,576 | |
| /48 | 2^80 | 65,536 | One site or organisation |
| /52 | 2^76 | 4,096 | |
| /56 | 2^72 | 256 | Typical home or small business delegation |
| /60 | 2^68 | 16 | Some ISPs delegate this to homes |
| /64 | 2^64 | 1 | One LAN or VLAN (SLAAC needs /64) |
| /80 | 281,474,976,710,656 | part of one | |
| /96 | 4,294,967,296 | part of one | NAT64 prefix (64:ff9b::/96) |
| /112 | 65,536 | part of one | |
| /120 | 256 | part of one | |
| /126 | 4 | part of one | |
| /127 | 2 | part of one | Point-to-point link (RFC 6164) |
| /128 | 1 | part of one | One address (loopback, host route) |
Address types
The first bits of an IPv6 address tell you what kind it is. These are the ranges you will meet on real networks.
| Prefix | Type | Defined in |
|---|---|---|
| 2000::/3 | Global unicast, routable on the internet | RFC 4291 |
| fc00::/7 (in practice fd00::/8) | Unique local, the private range | RFC 4193 |
| fe80::/10 | Link-local, every interface has one | RFC 4291 |
| ff00::/8 | Multicast | RFC 4291 |
| ::1/128 | Loopback | RFC 4291 |
| ::/128 | Unspecified | RFC 4291 |
| ::ffff:0:0/96 | IPv4-mapped | RFC 4291 |
| 64:ff9b::/96 | NAT64 well-known prefix | RFC 6052 |
| 2001:db8::/32 | Documentation and examples | RFC 3849 |
| 2002::/16 | 6to4 (deprecated) | RFC 3056 |
Writing addresses
RFC 5952 defines one canonical text form so that the same address is always written the same way:
- Use lowercase hex digits.
- Drop leading zeros in each 16-bit group:
0db8becomesdb8. - Replace the longest run of all-zero groups with
::, once. If two runs are equally long, shorten the first. - Do not use
::for a single zero group: write2001:db8:0:1:1:1:1:1. - Put the prefix length after a slash:
2001:db8::/32. In URLs wrap the address in brackets:[2001:db8::1]:443.
| Written as | Canonical form |
|---|---|
| 2001:0DB8:0000:0000:0000:0000:0000:0001 | 2001:db8::1 |
| 2001:db8:0:0:1:0:0:1 | 2001:db8::1:0:0:1 |
| fe80:0:0:0:0:0:0:1 | fe80::1 |
Planning on nibble boundaries
Each hex digit is four bits, so a nibble-aligned plan lets people read the hierarchy straight from the address. A common enterprise layout:
- /48 per site: 2001:db8:acad::/48
- /52 per building or zone: 16 per site
- /56 per function or floor: 256 per site
- /64 per VLAN: 65,536 per site
- /127 per router-to-router link, taken from a reserved /64
Read our IPv6 subnetting guide for a worked plan, or open the IPv6 calculator to split a prefix.