Skip to main content
Tool Factory

Network & Web

NetBIOS Name Encoder

Encode 1–16 NetBIOS name bytes as 32 A–P letters. Inspect both nibbles, encoded letters, and space padding for every byte.

Tool workspace

Your input stays in this browser.

Add the required input to continue.

Needs input

Run the tool when your input is ready.

Input

Enter 1–16 name bytes. Short names receive space padding. Hex accepts an explicit service suffix byte.

Options

RFC 1001 adds ASCII A (65) to each nibble. Keep Offset at 65.

Your result appears here

Encode 1–16 NetBIOS name bytes as 32 A–P letters. Inspect both nibbles, encoded letters, and space padding for every byte.

This tool runs open-source code from CyberChef by GCHQ (Apache License 2.0). See open-source credits.

NetBIOS first-level encoding adds ASCII A to each nibble, producing two letters per input byte.

The result contains the encoded label and a table of byte, nibble, and padding calculations.

  • Compare a known name with the 32-letter first-level label in a NetBIOS packet capture.

Sources: RFC 1001 section 14.1: first-level encoding

Set the name bytes and service suffix

  1. Choose Latin1 text or Hex bytes under Name format.
  2. Enter the name. Supply its final service byte explicitly when required.
  3. Run the encoder and inspect the label.

Encode FRED as a first-level label

Input: FRED

Settings: Name format Latin1 text; Offset 65; twelve space bytes fill the 16-byte name.

Result: EGFCEFEECACACACACACACACACACACACA

F becomes EG, R becomes FC, E becomes EF, and D becomes EE. Each trailing space becomes CA.

Byte encoding and packet boundaries

  • The encoder preserves case and does not select an OEM code page.
  • The result omits DNS label lengths, scope, and packet headers.
  • Encoding does not check host existence or name ownership.