Home/SEO, Domain & Network Inspector Tools/IPv6 to IPv4 & Hexadecimal Address Expander

IPv6 to IPv4 & Hexadecimal Address Expander

Enterprise-grade IPv6 address expander, RFC 5952 compressor, IPv4-mapped address extractor, 128-bit binary visualizer, and ip6.arpa reverse DNS PTR generator.

RFC Addressing Scenarios & Presets
Quick Load:
128-Bit IPv6

Address Forms & Expansions

Valid RFC 4291
Canonical Compressed (RFC 5952)
2001:db8:85a3::8a2e:370:7334
Fully Expanded (Full 32 Hex Digits)
2001:0db8:85a3:0000:0000:8a2e:0370:7334
Raw Hexadecimal (Unseparated 128-Bit)
0x20010db885a3000000008a2e03707334
Scope Classification & Type
Documentation Prefix

RFC 3849 Reserved globally for technical documentation and books

Reverse DNS Lookup Zone (ip6.arpa PTR)
4.3.3.7.0.7.3.0.e.2.a.8.0.0.0.0.0.0.0.0.3.a.5.8.8.b.d.0.1.0.0.2.ip6.arpa
Client-Side Native RFC ParsingRFC 4291 / RFC 5952

IPv4 Extraction & 128-Bit Binary

Dual-Stack Decoder
Dual-Stack IPv4 ExtractionPure IPv6 Unicast

This address does not contain an embedded IPv4 tail (::ffff:x.x.x.x) or 6to4 prefix (2002::/16). It is formatted purely as a native 128-bit IPv6 address.

16-Bit Hextet Decomposition (128 Bits Total)
H120018193
H20db83512
H385a334211
H400000
H500000
H68a2e35374
H70370880
H8733429492
Full 128-Bit Binary Bitstream
0010 0000 0000 0001 : 0000 1101 1011 1000 : 1000 0101 1010 0011 : 0000 0000 0000 0000 : 0000 0000 0000 0000 : 1000 1010 0010 1110 : 0000 0011 0111 0000 : 0111 0011 0011 0100
Client-Side Sandbox ComputationZero Server Telemetry

IPv6 Addressing Architecture & Compression Engineering

Internet Protocol version 6 (IPv6) was engineered by the Internet Engineering Task Force (IETF) in RFC 8200 and RFC 4291 to supersede IPv4 and solve global address space exhaustion. By expanding address boundaries from 32 bits to 128 bits, IPv6 yields approximately 3.4 x 10^38 distinct addresses—enough to assign billions of unique routable interfaces to every square meter of the earth.

RFC 5952 Formatting

Mandates consistent text representation: lowercase hexadecimal characters, suppression of unnecessary leading zeros in hextets, and single substitution of the longest contiguous null block using double colons (::).

Dual-Stack Transition

Dual-stack systems utilize IPv4-mapped addresses (::ffff:a.b.c.d) to represent legacy 32-bit IPv4 network sockets directly inside 128-bit IPv6 modern software network APIs.

DNS ip6.arpa Pointers

Reverse DNS lookups for IPv6 construct PTR record domains by exploding all 32 hexadecimal nibbles, reversing their natural sequence, and appending the authoritative ip6.arpa tree.

IPv6 Address Scope, Prefix Allocation & RFC Specifications

IPv6 structures addressing into definitive scopes that eliminate the broadcast storms typical of legacy IPv4 networks while strictly segmenting local from global routable topologies:

Scope / TypeBinary PrefixStandard NotationRFC StandardDescription & Operational Role
Loopback000...001 (128 bits)::1/128RFC 4291Localhost virtual interface; equivalent to 127.0.0.1 in IPv4.
Unspecified000...000 (128 bits)::/128RFC 4291Designates absence of address; used in socket bind all interfaces (0.0.0.0).
Link-Local Unicast1111 1110 10fe80::/10RFC 4291Autoconfigured per network link; non-routable beyond the local physical switch or VLAN.
Unique Local (ULA)1111 110fc00::/7 (fd00::/8)RFC 4193Private enterprise routable addressing; direct replacement for RFC 1918 private IPv4.
Global Unicast0012000::/3RFC 4291Publicly routable on the global Internet backbone across tier-1 ISPs.
IPv4-Mapped0...0 1111 1111::ffff:0:0/96RFC 4038Dual-stack socket encapsulation for handling legacy IPv4 connections inside IPv6 applications.
Multicast1111 1111ff00::/8RFC 4291Targeted group communication; replaces all broadcast addressing used in IPv4.

Demystifying the Reverse DNS (ip6.arpa) Nibble Structure

Unlike IPv4 reverse DNS which splits 32-bit addresses by full 8-bit octets (e.g., 1.1.168.192.in-addr.arpa), IPv6 reverse DNS delegates PTR records along 4-bit boundaries known as nibbles. Every individual hexadecimal digit represents a delegation node in the DNS hierarchy under the ip6.arpa domain tree.

Example Reverse DNS Transformation
Compressed IPv6: 2001:db8::1
Expanded 32 Nibbles: 2001:0db8:0000:0000:0000:0000:0000:0001
Reversed Dot-Separated String: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa

Automated IPv6 Address Expansion (Python 3 & Node.js)

Integrate programmatic address expansion, canonical compression, and PTR generation into infrastructure validation pipelines:

Python 3 (ipaddress Module)

import ipaddress

addr = ipaddress.IPv6Address('2001:db8::1')

print("Expanded:", addr.exploded)
print("Compressed:", addr.compressed)
print("Reverse DNS PTR:", addr.reverse_pointer)
print("Is IPv4-Mapped:", addr.ipv4_mapped)
print("Is Link-Local:", addr.is_link_local)
print("Raw 128-Bit Integer:", int(addr))
print("Hexadecimal:", hex(int(addr)))

Node.js (ipaddr.js Library)

import ipaddr from 'ipaddr.js';

const addr = ipaddr.parse('::ffff:192.168.1.1');

if (addr.kind() === 'ipv6') {
  console.log("Canonical:", addr.toNormalizedString());
  console.log("RFC 5952:", addr.toString());
  
  if (addr.isIPv4MappedAddress()) {
    const ipv4 = addr.toIPv4Address();
    console.log("Extracted IPv4:", ipv4.toString());
    console.log("Hex Value:", ipv4.toByteArray());
  }
}

Frequently Asked Questions (FAQ)

What is the difference between expanded and compressed IPv6 addresses?

An expanded IPv6 address explicitly writes out all 8 16-bit hextets using four hexadecimal characters each (32 total hex digits separated by 7 colons). A compressed IPv6 address follows RFC 5952 recommendations: leading zeros within each hextet are stripped, and the longest contiguous sequence of two or more zero-value hextets is replaced once by a double colon (::).

How does IPv4 address embedding work within IPv6?

Under RFC 4291 and RFC 4038, standard 32-bit IPv4 addresses can be embedded inside 128-bit IPv6 headers. In IPv4-mapped addresses (::ffff:x.x.x.x), the first 80 bits are zero, bits 81-96 are set to one (ffff), and the final 32 bits contain the dotted quad IPv4 address, allowing dual-stack networking software to handle both protocols seamlessly.

What is an ip6.arpa reverse DNS PTR record?

An ip6.arpa PTR record enables reverse DNS lookups for IPv6 addresses. To construct it, the 128-bit address is completely expanded into 32 single hexadecimal nibbles, reversed in sequence, separated by dots, and appended with the domain ".ip6.arpa".

What are RFC 4193 Unique Local Addresses (ULA)?

Unique Local Addresses (ULA) are the IPv6 counterpart to RFC 1918 private IPv4 spaces. Defined under prefix fc00::/7 (most commonly fd00::/8), ULAs are routable throughout private networks and enterprise VPNs but are strictly non-routable on the public global Internet.

Are my IP addresses logged or transmitted to your servers?

No. All IPv6 parsing, bitwise conversions, nibble reversals, and hexadecimal calculations execute strictly in your client-side browser memory. No telemetry, address data, or server requests are transmitted.

Found this tool helpful? Share it with others!

Share on Facebook
Share on X
Share on LinkedIn
Copy URL

Related & Complementary Utilities

Explore more privacy-first client-side web tools.