Back
Asciify Logo
Asciify
NULSTX

Start Of Heading

SOH (Start of Heading) is ASCII code point 1 (0x01), Unicode U+0001. It is a C0 control character that preceded a message header on teleprinter links — everything between SOH and the following STX (0x02) was routing or addressing metadata, not payload. In IBM BSC, the SOH-to-STX region carried station addresses and sequence numbers that the receiver processed before the actual data block began. Ctrl+A emits 0x01, which tmux and GNU Screen repurposed as their default command prefix. UTF-8 encodes it as the single byte 0x01; Unicode classifies it as Cc (Control) with the alias START OF HEADING.

Control Character

Technical Details

Code Example

</>
unsigned char frame[] = {0x01,'A','1',0x02,'O','K'};
// SOH marks header start; STX marks payload start
int is_soh = (frame[0] == 0x01);

Frequently Asked Questions

  • SOH (ASCII 1) marks the beginning of a message header in communication protocols. It separates routing/control information from the actual message content. Think of it as the start of the 'envelope' before the 'letter' inside.

  • It's used in protocols like BISYNC and some industrial/serial standards to indicate where the header section begins. In HL7 healthcare messaging, SOH-like markers delineate message segments. Some serial device protocols still frame messages with SOH.

  • Conceptually yes — both separate metadata from content. But HTTP uses text-based boundaries (the blank line \r\n\r\n between headers and body) instead of a control byte. SOH was the binary-protocol approach to the same structural problem.

  • Ctrl+A sends SOH (ASCII 1). In modern terminals, Ctrl+A is intercepted for 'move to start of line' (readline/emacs) or as the tmux/screen prefix key, so the raw SOH byte almost never reaches programs.

@workani&@alexluthor
Privacy & legal

Privacy

No accounts, no ads, no tracking cookies, and no cross-site tracking. The only analytics we keep are faceless — anonymous, aggregated counts of pages and searches, never tied to you. We store no IP addresses, set no tracking cookies, and build no profiles. Cloudflare hosts the site and handles requests for delivery and security.

Full privacy policy·Extension privacy·legal@asciify.dev

Attributions & licenses

Twemoji
© Twitter, Inc and other contributors · CC-BY 4.0
Noto Color Emoji
© Google · Apache 2.0
Fluent UI Emoji
© Microsoft · MIT
OpenMoji
© HfG Schwäbisch Gmünd · CC-BY-SA 4.0
Toss Face
© Viva Republica (Toss) · SIL OFL 1.1
JoyPixels
© JoyPixels Inc. · Free Limited Use License
SerenityOS Emoji
© The SerenityOS Developers · BSD-2-Clause
EmojiTwo
© EmojiTwo contributors · CC-BY 4.0
Apple Color Emoji
© Apple, Inc.
Facebook Emoji
© Meta Platforms, Inc.

Apple and Facebook emoji styles are proprietary and shown here solely for reference and comparison — a common-sense application of nominative-use / fair-use principles. asciify is not affiliated with, endorsed by, or sponsored by Apple, Inc., Meta Platforms, Inc., or any other rights holder listed above. If a rights holder requests removal of their emoji style from this site, it will be removed.

All other vendor emoji are reproduced for reference and comparison under their respective open licenses listed above.

Character names and code points from the Unicode® Standard. Unicode® and the Unicode Logo are registered trademarks of Unicode, Inc.

Privacy
© asciify.dev 2025-2026