We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
A two-way IPv4 and IPv6 address converter for network configuration, debugging, and format validation.
Enter IP address to start conversion
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
This converter maps a dotted IPv4 address into two text forms: an IPv4-mapped IPv6 address and a 6to4 address. In the reverse direction, it extracts IPv4 from those forms. This is not a general IPv4-to-IPv6 network translation: there is no single ordinary IPv6 address that every IPv4 address inherently becomes, and the page does not create a NAT64 mapping or convert a subnet.
The familiar form is ::ffff:a.b.c.d. The final 32 bits retain the IPv4 value, preceded by the mapped-address prefix. Example: 192.168.1.1 becomes ::ffff:192.168.1.1.
A 6to4 address starts with 2002::/16 and embeds the four IPv4 octets as two hexadecimal groups. For 192.168.1.1, the octets become c0, a8, 01, and 01, producing 2002:c0a8:0101::.
IPv4-mapped notation represents an IPv4 node in an IPv6 address structure. 6to4 was designed as a transition mechanism for carrying IPv6 across IPv4 networks. These outputs describe address forms; they do not establish that a host is reachable, that a network supports IPv6, or that a mapped address can be used in a particular application.
RFC 7526 deprecated the 6to4 anycast relay mechanism and says the basic unicast 6to4 mechanism should be disabled by default in new deployments. Treat the 6to4 result as a legacy representation or reference, not as a recommendation to deploy it.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use dotted decimal for IPv4, such as 192.168.1.1. For reverse extraction, use an IPv4-mapped address such as ::ffff:192.168.1.1 or an address beginning with the 6to4 prefix.
An IPv4 input displays both mapped and 6to4 text. A supported IPv6 input displays the extracted dotted IPv4 value. Copy the specific representation you need.
Confirm the full address and intended network context with the system or documentation that will use it. The converter does not test connectivity or validate an address for every protocol use.
For instance, entering 192.168.1.1 shows ::ffff:192.168.1.1 and 2002:c0a8:0101::.
Use cases
See how the tool fits into real work and everyday tasks.
A network operator reviewing a known IPv4-mapped value can recover its dotted decimal part for comparison with an IPv4 record.
A student or engineer can see how the IPv4 octets are written into the 6to4 prefix when reading older protocol material.
Use the paired output to understand how the same four IPv4 octets appear in these two distinct IPv6 forms.
Q&A
Find concise answers to common questions and confusing cases.
No. This page shows two specific embedded representations. General translation, including NAT64, depends on additional network configuration and is not performed here.
Do not treat it as a deployment recommendation. RFC 7526 describes operational problems with 6to4 and says the basic mechanism should be disabled by default in new deployments.
The reverse operation only extracts from recognized mapped or 6to4 patterns. Other IPv6 addresses do not necessarily contain an IPv4 value in those positions.
Notes
Review scope, result limitations, and important precautions before use.
Use these strings as representations for inspection. They do not configure routing, provide IPv4/IPv6 connectivity, prove reachability, or perform standards-complete address validation.
Related
Discover related tools, collections, and available API capabilities.