🌐 IPv6 Subnet Calculator

Expand an IPv6 address, parse a CIDR block, and see the first and last address, network range, host count, and reverse DNS.

Last updated: November 8, 2026 · By the BoltQuickTools team

Reading an IPv6 prefix without counting hex digits

Compressed notation like 2001:db8:: hides where a prefix ends, which makes it easy to get firewall rules and delegated ranges wrong. This calculator expands an address, applies the prefix with exact 128-bit arithmetic and shows the range it covers.

How the page works

There is one input box. Type an address, with or without a prefix, and the results update on every keystroke. Sample 1, Sample 2 and Sample 3 load a documentation /64, a link-local /64 and a /128. Clicking any result value selects the whole value, ready to copy. Errors appear in red beneath the box.

With no prefix, the input is treated as a single address, /128.

Example: 2001:db8:abcd:12::1/62

RowValue
Compressed2001:db8:abcd:12::1
Expanded2001:0db8:abcd:0012:0000:0000:0000:0001
Prefix length/62
Network2001:db8:abcd:10::
First address2001:db8:abcd:10::
Last address2001:db8:abcd:13:ffff:ffff:ffff:ffff
Total addresses73,786,976,294,838,206,464
Address maskffff:ffff:ffff:fffc:0000:0000:0000:0000
Reverse DNS1.0.0.d.c.b.a.8.b.d.0.1.0.0.2.ip6.arpa

So that /62 spans the four /64s ending in 10, 11, 12 and 13. Note the Reverse DNS row, which the next section explains.

Parser behaviour and limits

Notation and range questions

Which short form does Compressed use?

Lowercase, leading zeros removed, and :: replacing the longest run of two or more zero groups. On a tie the first run wins, so 2001:DB8:0:0:1:0:0:1 becomes 2001:db8::1:0:0:1. That matches the RFC 5952 recommendation.

Can I enter a prefix shorter than /4?

Yes. Anything from /0 to /128 works. ::/0 shows Total addresses as 340,282,366,920,938,463,463,374,607,431,768,211,456, and the Reverse DNS row is just ip6.arpa.

Why are the totals exact when the numbers are so large?

The page uses JavaScript BigInt rather than ordinary numbers, so every digit shown is correct.

For the IPv4 version of the same job, use the IPv4 Subnet Calculator. To check what a name actually resolves to, try DNS Lookup, and the DNS records reference explains the PTR records that the Reverse DNS row is for.