Internet Checksum Complement Tool
Take the bounded ones-complement of one explicit 16-bit Internet-checksum word; this is not a packet checksum calculation.
Description
Take the bounded ones-complement of one explicit 16-bit Internet-checksum word; this is not a packet checksum calculation.
A 16-bit one's-complement operation flips every bit of an already supplied word.
When to use this tool
Take the bounded ones-complement of one explicit 16-bit Internet-checksum word; this is not a packet checksum calculation.
- Prepare the supplied word 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 word. 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.complement. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require word from 0 to 65,535 and return 65,535 minus word.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| word | word. | Integer from 0 to 65535 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.complement | The complement value under the stated formula or text convention. |
{
"input": {
"word": 1
},
"output": {
"result": {
"complement": 65534
}
}
} Limitations and assumptions
- No word list is summed and no packet integrity check is performed. This is a complement operation, not a complete Internet checksum.
- 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 the complete specified checksum algorithm and independent test vectors when verifying a payload. Field packing, parameter shape and arithmetic agreement are separate checks; none supplies cryptographic authenticity.
References
Similar or alternative tools
- Internet Checksum Carry Fold Trace
Trace exact Internet-checksum end-around carry folding of an unsigned integer sum without complementing it or reading packet fields.
- Internet Checksum Residue Check
Verify an explicit Internet-checksum word list including its checksum against all-one folded residue; no packet-field or protocol coverage assumptions.