127.0.0.1 and Localhost Explained

127.0.0.1 means "this machine."

When you connect to it, packets do not go to your router, your ISP, or the internet. The operating system routes them straight back to the same computer.

That is why developers use addresses like:

http://127.0.0.1:3000
http://localhost:3000

They mean "connect to the service running on my own machine, on port 3000."

What 127.0.0.1 Is

127.0.0.1 is part of the IPv4 loopback range:

127.0.0.0/8

The common address is:

127.0.0.1

If an application opens a connection to 127.0.0.1, the network stack loops the connection back locally.

browser -> 127.0.0.1:3000 -> local app on the same machine

No external DNS provider is involved.

What Localhost Is

localhost is the human-readable name for loopback.

Most systems map it locally:

127.0.0.1    localhost
::1          localhost

You can usually find that mapping in:

The hosts file is checked before normal DNS on most systems. That is why localhost works even when you are offline.

IPv4 vs IPv6 Localhost

There are two common loopback addresses:

Some tools prefer IPv6 first. If an app listens only on IPv4, this can matter:

curl http://localhost:3000
curl http://127.0.0.1:3000
curl http://[::1]:3000

If 127.0.0.1 works but localhost fails, check whether the app is listening on IPv4, IPv6, or both.

Localhost Is Not Public DNS

This is the key point:

your localhost != someone else's localhost

If you send a colleague a URL like:

http://localhost:3000

their browser tries to connect to port 3000 on their own machine.

To share a local app, use a proper hostname, a tunnel, a VPN, or deploy it somewhere reachable.

Why Local Dev Servers Use It

Localhost is useful because it is safe by default:

• it does not expose the service to the network
• it avoids public DNS changes
• it works offline
• it lets many apps use different ports on one machine

Examples:

npm run dev
# Vite starts on http://localhost:5173
 
go run ./cmd/api
# API starts on http://127.0.0.1:8080

The port number chooses the local service. The hostname chooses the local interface.

127.0.0.1 vs 0.0.0.0

These are often confused:

If a dev server is bound to 127.0.0.1, another device on your Wi-Fi cannot reach it.

If it is bound to 0.0.0.0, another device may be able to reach it through your LAN IP:

http://192.168.1.25:3000

Only do this intentionally. Firewalls and development servers are not a substitute for production access control.

Localhost in Containers

Containers add one more layer.

Inside a Docker container:

localhost = that container

Not your laptop. Not another container.

Common fixes:

• publish the container port with -p 8080:8080
• bind the app inside the container to 0.0.0.0
• use the Docker service name to reach another container on the same network

If an app works inside the container but not from your browser, check port publishing first.

Debugging Checklist

If localhost is not working:

1. Check the service is running.
2. Check the port is correct.
3. Try 127.0.0.1 instead of localhost.
4. Try ::1 if IPv6 may be involved.
5. Check the app bind address.
6. Check firewall or security software.
7. Check /etc/hosts or the Windows hosts file.
8. If using Docker, check port publishing.

Useful commands:

curl -v http://127.0.0.1:3000
lsof -iTCP:3000 -sTCP:LISTEN
dig localhost

Related Reading

• What is DNS?
• FQDN explained
• DNS troubleshooting
• IPv4 vs IPv6