Skip to content

Main content

Network: TCP Flags Single Byte Label Tool

Decode the conventional eight TCP flags bits FIN through CWR from a supplied octet; excludes extended flags in adjacent header bits and state-machine validity.

Loading tool…

Description

Inspect bits zero through seven of flagsByte and return set labels in FIN, SYN, RST, PSH, ACK, URG, ECE, CWR order.

Packet headers encode several meanings in fixed-width fields. Bit positions, network byte order, and reserved values must be distinguished from validation of an entire message.

Inspect bits zero through seven of flagsByte and return set labels in FIN, SYN, RST, PSH, ACK, URG, ECE, CWR order.

When to use this tool

Use Network: TCP Flags Single Byte Label when you need to decode or encode one explicit packet field.

How to use the tool and how it works

  1. Enter flagsByte. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Inspect bits zero through seven of flagsByte and return set labels in FIN, SYN, RST, PSH, ACK, URG, ECE, CWR order.1

Input fieldMeaning and unitsAccepted input
flagsByteFlags ByteRequired. Safe integer.
Output fieldInterpretationReturned shape
resultResultRequired. Object.
result.flagsFlagsCalculated result member: array.
json
{
  "input": {
    "flagsByte": 18
  },
  "output": {
    "result": {
      "flags": [
        "SYN",
        "ACK"
      ]
    }
  }
}

Limitations and assumptions

  • Only this byte is decoded; other header bits and the legality of flag combinations are not checked.
  • Outputs are nested inside result. Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Inspect the complete captured header and apply the relevant protocol's structural and state rules.

References

  1. Calculation and input contract: network/tcp-flags-single-byte-label — tool.io

Similar or alternative tools