0.0.0.0 vs 127.0.0.1: What’s the Difference?

0.0.0.0 and 127.0.0.1 are not interchangeable: 127.0.0.1 is for connecting, 0.0.0.0 is for listening. 127.0.0.1 is the loopback address reachable only from your own machine. 0.0.0.0 is a special "all interfaces" address used when a server binds a socket — it tells the server to accept connections on every network interface. You connect to a service at 127.0.0.1; you bind a service to 0.0.0.0 (or 127.0.0.1) to choose who can reach it.

0.0.0.0 vs 127.0.0.1 at a glance

When to use 127.0.0.1

Bind to 127.0.0.1 when a service should be local only — a dev database, a local API you do not want exposed, or anything sensitive. Other devices on the network cannot reach it, which is the safe default. To connect, use 127.0.0.1 or localhost (note the IPv6 nuance in 127.0.0.1 vs localhost).

When to use 0.0.0.0

Bind to 0.0.0.0 when the server must be reachable from outside the machine: testing a site on your phone over the LAN, or a Docker container whose port must reach the host. Many frameworks default to 127.0.0.1; switch to 0.0.0.0 (e.g. --host 0.0.0.0) to expose it.

The Docker gotcha

A container that binds its app to 127.0.0.1 listens only inside the container, so docker run -p 8080:8080 appears broken. Bind the app to 0.0.0.0 inside the container so the published port reaches the host. See managing the hosts file with Docker.

Security reminder

Binding to 0.0.0.0 exposes the service to your whole network. On untrusted Wi-Fi, this can leak a dev server. Prefer 127.0.0.1 unless you specifically need external access, and use friendly local domains for clarity — see the hosts file syntax guide. Locahl makes those local domain mappings easy to manage and toggle.

_Last reviewed: June 2026._