IPv4 to Mapped IPv6 & Hex Converter
IPv4 / IPv6 transition formats. Enter dotted IPv4 (optional /0–/32, validated only) or an IPv4-mapped IPv6 address such as ::ffff:192.0.2.1 or ::ffff:c000:201. IPv6 input must have no suffix. General IPv6, 6to4 input and zone identifiers are rejected.
About this ipv4 to mapped ipv6 & hex converter
IPv4 / IPv6 transition formats. Enter dotted IPv4 (optional /0–/32, validated only) or an IPv4-mapped IPv6 address such as ::ffff:192.0.2.1 or ::ffff:c000:201. IPv6 input must have no suffix. General IPv6, 6to4 input and zone identifiers are rejected Performs protocol inspection, IP calculation, and network analysis client-side without sending probes or exposing network topology.
Protocol mechanics & network logic
The execution engine processes input tokens and applies transformations in the browser sandbox. Specifically, Enter dotted IPv4 (optional /0–/32, validated only) or an IPv4-mapped IPv6 address such as ::ffff:192.0.2.1 or ::ffff:c000:201. Mapped IPv6 uses 80 zero bits + 16 one bits + the 32 IPv4 bits: ::ffff:0:0/96 (RFC 4291). Reverse conversion accepts only this prefix. 6to4 places the 32 IPv4 bits after 2002::/16, yielding a /48 prefix (RFC 3056). The remaining 80 bits are for subnet and interface identifiers.
Worked network diagnostic scenario
Scenario: Convert IPv4 and mapped IPv6, and derive the 6to4 prefix locally.
Sample input:
Processing: Validate IPv4; the /24 suffix does not change output. For mapped IPv6 use 80 zero bits, 16 one bits, then 32 IPv4 bits. For 6to4 place the IPv4 bits after 2002::/16 to form /48.
Illustrative output:
Addressing limits & protocol boundaries
This is local format arithmetic, not a reachability or allocation check. Private, documentation and other special IPv4 values can be illustrated but do not imply a usable public 6to4 site. RFC 7526 deprecates 6to4 anycast relay service.
Addressing calculations and subnet models in IPv4 to Mapped IPv6 & Hex Converter follow IETF RFC definitions. Ensure subnet masks and CIDR prefixes match your network topology.
Offline network inspection boundary
Address parsing and CIDR calculations in IPv4 to Mapped IPv6 & Hex Converter run entirely client-side without probing external IP networks or transmitting routing data.
IETF RFC specifications & IANA registries
IETF Request for Comments (RFC) standards and IANA registry references:
- RFC 791 (Internet Protocol: IPv4)
- RFC 4632 (Classless Inter-domain Routing: CIDR)
- RFC 4291 (IP Version 6 Addressing Architecture)
IPv4 to Mapped IPv6 & Hex Converter verification · Audit standards
How to use it
- Enter 192.0.2.1/24, ::ffff:192.0.2.1 or ::ffff:c000:201 in the text area.
- Click Run locally. IPv4 octets and optional /0–/32 are validated; mapped IPv6 must have the ::ffff:0:0/96 prefix and no suffix.
- Read the JSON fields ipv4, ipv4MappedIpv6 and hex: ::ffff:c000:0201 and 0xc0000201 are derived from 192.0.2.1. 6to4 prefix · /48: 2002:c000:201::/48; Mapped IPv6 · dotted decimal: ::ffff:192.0.2.1.
Frequently asked questions
What does this IPv4 converter return?+
Operational requirements for "What does this IPv4 converter return?" are verified in local memory during execution of IPv4 to Mapped IPv6 & Hex Converter.
Can I try an example?+
Enter `192.0.2.1/24` and choose Run locally. It returns `::ffff:c000:0201` and `0xc0000201`.
Does the optional prefix change the conversion?+
No. An optional `/0` through `/32` suffix is validated, but conversion uses only the IPv4 value and does not return a subnet.
Does it create 6to4 prefixes?+
IPv6: 2002:c000:201::/48.