Back
Asciify Logo
Asciify
EOTACK

Enquiry

ENQ (Enquiry) is ASCII code point 5 (0x05), Unicode U+0005. It is a C0 control character that a teleprinter station sent to ask "are you there?" — the remote end was expected to reply with ACK (0x06) or a station identity string. In IBM BSC, ENQ initiated the bidding phase to establish which station would control the half-duplex line before any data blocks flowed. Ctrl+E emits 0x05, and some terminal emulators like xterm still respond to it by returning a configurable answerback string — a vestige of that original polling role. UTF-8 encodes it as the single byte 0x05; Unicode classifies it as Cc (Control) with the alias ENQUIRY.

Control Character

Technical Details

Code Example

</>
unsigned char enq = 0x05; // ENQ
unsigned char frame[] = { enq, 'I','D' }; // poll + payload
size_t n = sizeof(frame); // bytes to write

Frequently Asked Questions

  • ENQ (ASCII 5) is a 'who's there?' signal. In communication protocols, one device sends ENQ to ask the other end to identify itself or confirm it's ready. The expected reply is usually ACK or a station identification.

  • Mostly in legacy point-of-sale systems, industrial protocols, and serial devices. Some payment terminals still use ENQ/ACK handshaking. In mainstream software development, you're unlikely to encounter it unless interfacing with older hardware.

  • Conceptually, yes. ENQ asks 'are you there?' just like ICMP ping does at the network level. The difference is that ENQ operates at the data-link level in serial protocols, while ping operates at the network layer in IP networks.

  • The sender assumes the connection is down or the other device is offline. After a timeout (or a few retries), it typically reports a communication error. It's the serial protocol equivalent of a network timeout.

@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