IPv6, explained

IPv6 (RFC 8200) was designed in the 1990s when it became clear that IPv4’s 4.3 billion addresses would run out. An IPv6 address has 128 bits: 2¹²⁸, or about 3.4 × 10³⁸ addresses. The point isn’t the size of the number; it’s that every network can get as much space as it needs, and every device can have a globally reachable address again — no NAT required.

IPv6 is not an upgrade of IPv4; the two protocols run side by side (dual stack). Today a large and growing share of traffic to major services uses IPv6, especially on mobile networks.

An IPv6 address is written as eight groups of four hexadecimal digits, separated by colons:

2001:0db8:0000:0000:0000:ff00:0042:8329

Each group is 16 bits. Hexadecimal digits run from 0–9 and a–f; letters are case-insensitive but written in lowercase by convention.

Long runs of zeros are common, so two shortening rules exist (RFC 4291), and RFC 5952 defines the one correct way to apply them:

1. Drop leading zeros in each group: 0db8 → db8, 0042 → 42, 0000 → 0.
2. Replace one run of consecutive zero groups with :: — the longest run, the first one if there’s a tie, and only if it covers at least two groups. It can appear only once, otherwise the address would be ambiguous.

So 2001:0db8:0000:0000:0000:ff00:0042:8329 becomes 2001:db8::ff00:42:8329. The loopback address 0:0:0:0:0:0:0:1 is ::1, and the unspecified address is just ::.

Try any address in the explorer below — it shows the expanded and canonical forms side by side.

IPv6 uses CIDR notation like IPv4. A typical global unicast address splits into:

• Routing prefix (usually /48 or /56) — assigned to a site by its provider.
• Subnet ID — the bits up to /64, numbering the site’s networks. A /48 holds 65,536 subnets.
• Interface identifier (the last 64 bits) — identifies the device on its network.

A single LAN is almost always a /64. Stateless address autoconfiguration (SLAAC) relies on it: devices pick their own interface identifiers, nowadays randomised for privacy (RFC 8981), and change them regularly.

• Global unicast 2000::/3 — public, routable addresses.
• Link-local fe80::/10 — every IPv6 interface has one; valid only on the local link, used for neighbour discovery and routing protocols.
• Unique local fc00::/7 (in practice fd00::/8) — the IPv6 equivalent of private addresses (RFC 4193).
• Multicast ff00::/8 — IPv6 has no broadcast; multicast groups replace it.
• Loopback ::1 and unspecified ::.
• IPv4-mapped ::ffff:0:0/96 — how IPv6 software represents IPv4 peers, e.g. ::ffff:192.0.2.1.
• Documentation 2001:db8::/32 and 3fff::/20 — for examples like the ones on this page.

The full list of reserved IPv6 blocks, generated from the IANA registry used by this site’s classifier:

A browser connects over one address family at a time. When both work, it usually prefers IPv6 (Happy Eyeballs, RFC 8305). To show you both addresses, ipaddress.tr asks two extra hostnames from your browser: one that only has an IPv4 (A) record and one that only has an IPv6 (AAAA) record. Whatever each one sees is your address for that family. If the IPv6 request fails, your connection has no working IPv6.