Skip to content
AdminKit

RESP (Redis Serialization Protocol)

What is RESP (Redis Serialization Protocol)?

RESP (REdis Serialization Protocol) is the simple, text-based wire protocol Redis clients and servers exchange commands and replies over, typically port 6379, with no authentication built into the protocol itself. AdminKit's guide to checking an exposed Redis port explains why an internet-reachable RESP connection with no password is immediately exploitable.

By AdminKit team, Netbase JSC · Updated

RESP (REdis Serialization Protocol) is the wire protocol Redis clients and servers use to exchange commands and replies, typically over port 6379, the port IANA registers for the redis service. It’s a simple, text-based format — each message type (simple string, error, integer, bulk string, array) starts with a distinct prefix character — which makes RESP easy for client libraries to parse, and it’s defined by Redis’s own protocol specification rather than an IETF RFC the way DNS or SMTP is. RESP isn’t confined to Redis itself: Valkey, an open-source fork of Redis, documents the same protocol and notes that many other client-server projects use it. RESP itself carries no authentication: Redis’s own security documentation describes Redis as designed to be accessed by trusted clients inside trusted environments, so anyone who can open a RESP connection can issue any command the server accepts. This is why an internet-reachable Redis port with no password set is an immediately exploitable misconfiguration, not a minor gap — a 2018 Imperva study found roughly 75% of the open Redis instances it scanned already infected with malware. Redis’s own protected mode exists specifically to stop a default, unauthenticated instance from accepting non-loopback connections in the first place.

RESP (Redis Serialization Protocol) is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

Does RESP have built-in authentication?

No -- Redis's own security documentation describes Redis as designed to be accessed by trusted clients inside trusted environments, so anyone who can open a RESP connection can issue any command the server accepts.

What port does RESP typically use?

Port 6379.

Who defines the RESP specification?

Redis's own protocol specification, rather than an IETF RFC the way DNS or SMTP is.

How is a RESP message structured?

Each message type -- simple string, error, integer, bulk string, array -- starts with a distinct prefix character, making it easy for client libraries to parse.