IPv4 to IPv6 Converter
Convert IPv4 addresses to IPv6 notation: IPv4-mapped, 6to4, and Teredo formats.
About this tool
IPv4 to IPv6 Converter translates an IPv4 address into several standard IPv6 representations. Paste any IPv4 address and instantly see its IPv4-mapped, 6to4, Teredo, and full hex IPv6 equivalents.
Example: 192.168.1.1 becomes ::ffff:192.168.1.1 (IPv4-mapped), 2002:c0a8:0101::/48 (6to4 prefix), a Teredo address with obfuscated client data, and ::ffff:c0a8:0101 in canonical hex notation.
Useful for configuring dual-stack servers, setting up 6to4 tunnels, debugging Teredo traffic, or writing IPv6-aware application code that needs to handle IPv4-compatible address formats.
FAQ
What is the difference between IPv4-mapped and IPv4-compatible IPv6? ›
IPv4-mapped addresses (::ffff:0:0/96) are used by dual-stack sockets to represent IPv4 connections inside an IPv6 API — they look like ::ffff:192.0.2.1. IPv4-compatible addresses (::/96) had the IPv4 address in the low 32 bits with all zeros in the upper 96 bits (e.g. ::192.0.2.1) but were deprecated by RFC 4291 and are no longer used.
What is a 6to4 address? ›
6to4 (RFC 3056) is an automatic IPv6-over-IPv4 tunneling mechanism. Each public IPv4 address gets a /48 IPv6 prefix: 2002:XXXX:XXXX::/48 where XXXX:XXXX is the hex encoding of the IPv4. For example, 192.168.1.1 (0xC0A80101) becomes 2002:c0a8:0101::/48. The host can then assign any /64 subnet under that prefix.
How does Teredo encode the IPv4 address? ›
Teredo (RFC 4380) is designed for hosts behind NAT. The Teredo server IPv4 and the client IPv4 are both XORed with 0xFFFFFFFF (bitwise-NOT) and embedded in the last 64 bits of the address. This obfuscation prevents naive middleboxes from rewriting the embedded addresses. The client port is also XORed with 0xFFFF.
Why does the full IPv6 hex notation show ::ffff: before the hex IPv4? ›
In a dual-stack environment, IPv4 addresses are represented in IPv6 as ::ffff:aabb:ccdd (the IPv4-mapped format). The full hex notation shows the canonical 8-group IPv6 address with the last two groups encoding the IPv4 octets as hex — e.g. 192.168.0.1 → ::ffff:c0a8:0001.