IPv4 Address Byte Order Swap
Reverse the four explicit IPv4 byte lanes while retaining the original exact integer value; not reverse DNS or host/network byte conversion in memory.
Description
Reverse the four explicit IPv4 byte lanes while retaining the original exact integer value; not reverse DNS or host/network byte conversion in memory.
Reversing IPv4 octets is a textual byte-order operation. The original integer value remains separately useful for checking the source address.
When to use this tool
Reverse the four explicit IPv4 byte lanes while retaining the original exact integer value; not reverse DNS or host/network byte conversion in memory.
- 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.address, result.integer. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate address, reverse its four written dot-separated octets and return that address string. integer is the decimal integer value of the original, unreversed address.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.address | The address value under the stated formula or text convention. |
| result.integer | Exact decimal integer text under the operation described above. |
{
"input": {
"address": "1.2.3.4"
},
"output": {
"result": {
"address": "4.3.2.1",
"integer": "16909060"
}
}
}Limitations and assumptions
- The returned integer is deliberately not the swapped address's integer. No packet byte order, host endianness or DNS record is inferred.
- 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
- IPv4 Address Pair Common Prefix
Find the exact common leading-bit prefix of two IPv4 addresses; identical addresses yield a /32 ancestor.
- IPv4 Address Prefix Offset
Return an address’s exact zero-based prefix offset only when it belongs to an explicitly normalized IPv4 network; outside offsets remain null.