IPv6 Mapped IPv4 Payload Extractor
Extract an IPv4 payload only from the exact IPv4-mapped IPv6 ::ffff:0:0/96 format; other embeddings are not guessed.
Description
Extract an IPv4 payload only from the exact IPv4-mapped IPv6 ::ffff:0:0/96 format; other embeddings are not guessed.
An IPv6 address may contain an IPv4-looking tail without being in the IPv4-mapped range. This extractor checks the exact mapped prefix first.
When to use this tool
Extract an IPv4 payload only from the exact IPv4-mapped IPv6 ::ffff:0:0/96 format; other embeddings are not guessed.
- Prepare the supplied address fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter address. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.mapped, result.ipv4. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse address as 128 bits. mapped is true only when shifting right 32 bits gives 65535. If true, format the low 32 bits as dotted IPv4; otherwise return ipv4 as null.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| address | Address text for the family named by this tool. Prefix lengths are separate fields where shown. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.mapped | Flag for mapped under the exact condition described above. |
| result.ipv4 | The ipv4 value under the stated formula or text convention. |
{
"input": {
"address": "::ffff:192.0.2.1"
},
"output": {
"result": {
"mapped": true,
"ipv4": "192.0.2.1"
}
}
}Limitations and assumptions
- No other embedding prefix is guessed. A mapped address says nothing about interface configuration, reachability or translation policy.
- IPv4 input uses strict dotted-decimal octets without leading zeros or surrounding whitespace. IPv6 accepts its supported compressed or full spellings and trims surrounding whitespace, but rejects zone identifiers; embedded dotted IPv4 uses the strict IPv4 spelling. IPv6 address outputs are fully expanded unless stated otherwise.
- All declared input fields are required and unexpected top-level fields are rejected. Numbers must be finite; lists are limited to 128 entries and ordinary text fields to 8,192 UTF-16 code units, with tighter limits where stated.
- JSON text inputs must parse within bounded nesting and size limits. Numeric outputs outside the safe finite range are rejected; large exact integer results use decimal strings. Indexes and half-open spans are zero-based unless a rank is explicitly described as one-based.
Alternative or Complementary methods
Use address-set arithmetic for prefix planning and a routing or interface inspection for deployed configuration. Membership and overlap do not establish reachability, ownership or route preference.
References
Similar or alternative tools
- IPv6 Mapped IPv4 Payload Builder
Build the exact IPv4-mapped IPv6 address for a validated IPv4 payload, formatted fully expanded; not NAT64 or an interface assignment.
- IPv6 Hextet Field Extractor
Extract one zero-based IPv6 hextet in network order after existing address parsing; returns its exact 16-bit numeric value.