Skip to content
AdminKit

Loopback address

What is Loopback address?

A loopback address is the reserved address a device uses to talk to itself -- 127.0.0.1 for IPv4, ::1 for IPv6 -- handled entirely inside its own network stack and never sent over a physical interface. AdminKit's guide to checking for an exposed Redis instance explains why services default to listening there instead of a public interface.

By AdminKit team, Netbase JSC · Updated

A loopback address is a reserved address a device uses to address itself: 127.0.0.0/8 for IPv4 (commonly 127.0.0.1), defined in RFC 1122 and listed in IANA’s IPv4 Special-Purpose Address Registry, and ::1/128 for IPv6, defined in RFC 4291. Traffic sent to it is handled entirely inside the host’s own network stack and never reaches a physical network interface, which is why it keeps working even with no network connection at all. Many services are deliberately configured to listen only on the loopback interface by default, accepting connections from processes on the same machine but refusing anything arriving from outside — Redis’s own security documentation explains that its “protected mode” falls back to loopback-only access whenever no password is configured, and PostgreSQL’s connection settings documentation gives listen_addresses a default of localhost, which allows only local loopback TCP/IP connections. Confirming whether a service is bound to loopback or to a public interface is the first question in diagnosing an unexpected database exposure. The same naming also describes NAT loopback (NAT hairpinning), where a whole local network reaches its own public-facing address the same way a device reaches itself here.

Confirming a service’s bind address matters alongside its well-known port number — together they determine who, if anyone outside the host, can reach it.

AdminKit groups loopback address under its IP & network cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What is the loopback address, exactly?

The reserved address a device uses to talk to itself -- 127.0.0.0/8 for IPv4 (commonly 127.0.0.1), defined in RFC 1122, and ::1/128 for IPv6, defined in RFC 4291.

Does loopback traffic ever leave the device?

No -- it's handled entirely inside the host's own network stack and never reaches a physical network interface, which is why it keeps working even with no network connection at all.

Why do services like Redis default to listening only on loopback?

Redis's own 'protected mode' falls back to loopback-only access whenever no password is configured, accepting connections only from processes on the same machine and refusing anything arriving from outside.

What's the first thing to check when diagnosing an unexpected database exposure?

Whether the service is actually bound to loopback or to a public interface -- that single setting is usually what separates a database reachable only locally from one exposed to the internet.