Dual-Stack Debugging
Modern operating systems and containers report IPv4 connections as ::ffff: addresses in logs and socket APIs. Convert between formats to correlate IPv4 firewall rules with IPv6 socket output.
500+ fast, free tools. Most run in your browser only; Image & PDF tools upload files to the backend when you run them.
Mapped IPv6 textual forms such as ::ffff dotted quartet.
IPv4 to IPv6 Converter on UtilityKit transforms any dotted-decimal IPv4 address into its standardised IPv6 representations instantly in your browser. Paste an address like 192.168.1.1 and receive the IPv4-mapped IPv6 address (::ffff:192.168.1.1), its fully expanded 128-bit hexadecimal form, the compressed RFC 5952 notation, and the 6to4 tunnel prefix used by the 2002::/16 range. The tool also performs the reverse: paste an IPv4-mapped IPv6 address and extract the original IPv4. Understanding how IPv4 and IPv6 coexist is essential for developers testing dual-stack configurations, writing socket code that handles both address families, configuring reverse DNS (PTR) records, or debugging mixed-mode networking in Docker, Kubernetes, and cloud environments where the kernel reports connections using ::ffff: prefixed addresses.
Modern operating systems and containers report IPv4 connections as ::ffff: addresses in logs and socket APIs. Convert between formats to correlate IPv4 firewall rules with IPv6 socket output.
All output formats follow RFC 4291 (IPv6 addressing), RFC 5952 (compressed text representation), and RFC 3056 (6to4) — safe to use directly in configuration files and DNS records.
Reverse DNS PTR records for IPv4-mapped addresses follow a specific nibble-reversed format. The tool shows the ARPA PTR suffix needed for ip6.arpa zone entries.
When writing cross-family socket code in Python, Go, or C, you need the exact ::ffff: form to bind or connect to IPv4 addresses via an IPv6 socket. Verify the format instantly.
6to4 tunnelling embeds IPv4 addresses inside 2002::/16 prefixes. Inspect any 6to4 address to extract the embedded IPv4 and diagnose tunnel routing issues.
All bit manipulation and format conversion runs entirely in your browser — no internal IP addresses are transmitted to external services.
Input: 203.0.113.45
Output: IPv4-mapped: ::ffff:203.0.113.45 | Expanded: 0000:0000:0000:0000:0000:ffff:cb00:712d | 6to4 prefix: 2002:cb00:712d::/48
Input: 192.168.1.1
Output: IPv4-mapped: ::ffff:192.168.1.1 | Expanded: 0000:0000:0000:0000:0000:ffff:c0a8:0101 | Compressed: ::ffff:c0a8:101 | 6to4: non-routable (private IPv4)
Input: 127.0.0.1
Output: IPv4-mapped: ::ffff:127.0.0.1 | Expanded: 0000:0000:0000:0000:0000:ffff:7f00:0001 — appears in dual-stack server logs as ::ffff:127.0.0.1 for local connections