Basics

Public vs Private IP — The Difference Explained

meine-ip.info Editorial · · 4 min read · Updated May 2026
IP-address public private NAT RFC1918 home-network
NordVPN
Recommended
Ad
  • 5,000+ Servers
  • No Logging
  • Up to 10 Devices
Protect your IP with NordVPN →

The shortest answer

A public IP address is your address on the internet — websites and services outside your network see it. A private IP address is your address inside your home network — only devices behind your router see it.

Type Where valid? Who sees it? Example
Public IP Worldwide on the internet Every site you visit, your ISP, every online service 93.184.216.34
Private IP Only on your LAN/Wi-Fi Only devices on the same home network 192.168.1.42

Your own public IP is always shown on the meine-ip.info homepage. Your private IP is shown by your operating system — see the steps below.

Why are there two at all?

IPv4 was designed in the 1980s with 4.3 billion addresses. At that time that was plenty — servers, no smartphones. Today every household has 10–20 connected devices: PCs, laptops, phones, smart TVs, printers, smart speakers, vacuum robots, smart bulbs.

The fix is called NAT (Network Address Translation): every device behind the router shares one public IP. Internally each device gets its own private IP — the router translates between the two worlds.

Internet  ←─────── Public IP: 93.184.216.34 ───────→ [Router]
                                                        │
                                                        ├── 192.168.1.10 (PC)
                                                        ├── 192.168.1.20 (Laptop)
                                                        ├── 192.168.1.30 (Phone)
                                                        └── 192.168.1.40 (Smart TV)

Private address ranges (RFC 1918)

Three blocks are globally reserved for internal use — they never appear on the public internet:

Range Size Typical use
10.0.0.010.255.255.255 (10.0.0.0/8) 16.7M addresses Large enterprise networks, VPN pools
172.16.0.0172.31.255.255 (172.16.0.0/12) 1.05M addresses Mid-size enterprises, Docker default
192.168.0.0192.168.255.255 (192.168.0.0/16) 65,536 addresses Home networks, small offices

Special ranges that aren't assignable globally either:

  • 127.0.0.0/8 — loopback (127.0.0.1 = the device itself)
  • 169.254.0.0/16 — link-local / APIPA (auto-IP when DHCP fails)
  • 100.64.0.0/10 — Carrier-Grade NAT (ISP-internal subnet, RFC 6598)

Find your own private IP

Windows: Win + Rcmdipconfig → read "IPv4 Address" macOS: System Settings → Network → active adapter → IP address Android: Settings → Wi-Fi → active network → IP address iOS: Settings → Wi-Fi → blue "i" → IP address Linux: terminal → ip addr or hostname -I

The router IP (default gateway) is shown at the same spot. For step-by-step per platform: How to find your router's IP.

When does which IP matter?

Use case Relevant IP
Website tracking, geo-location Public
Geo blocks / streaming region Public
Banking / login security check Public
Reach a printer at home Private
Talk to a NAS on the LAN Private
Set up port forwarding Both — public (incoming) + private (target on LAN)
Test Wi-Fi coverage Private
Host a game server for friends Public (with port-forwarding to private)
VPN into the home network Public (target of the tunnel)

What about the router's IP?

The router has two IPs at the same time:

  • WAN side (public): assigned by the ISP, visible from the internet
  • LAN side (private): usually 192.168.x.1 — the default gateway for every device on the home network

When people say "router IP" they almost always mean the private LAN side — the address you type to reach the admin interface.

Security implications

Private = unreachable from outside

With no port forwarding configured, nobody on the internet can reach a private device directly. NAT works like a one-way street: outbound from inside works; inbound from outside does not.

Public = scanned constantly

Your public IP is constantly scanned by bots. That's normal and harmless as long as no unnecessary ports are open. Verify with the Port Scanner.

Private address shown on a website?

If a website suddenly displays 192.168.1.1, that's your local router IP — the site can only see it because JavaScript on your device read it via WebRTC. A well-known privacy bug, largely patched in modern browsers.

IPv6 — a world without NAT

In IPv6 the address space is so large that NAT becomes obsolete. Every device gets a global address directly visible on the internet. Security is then enforced at the router (firewall) and endpoint — not "by accident" via NAT.

More: IPv4 vs IPv6 — side-by-side comparison.

Three myths

"My private IP is secret." No — inside your home network it's visible to every other device. Outside it isn't. But "secret" it isn't, and it's not privacy-sensitive.

"Typing 192.168.1.1 reaches my router login." Yes — if that's your router IP. Common defaults: 192.168.0.1, 192.168.1.1, 192.168.178.1 (FRITZ!Box), 192.168.50.1 (ASUS).

"If I turn off Wi-Fi, my public IP changes." No — the public IP is tied to the router/ISP, not to Wi-Fi. Wi-Fi only affects the private LAN link.

Related

NordVPN
Recommended
Ad
  • 5,000+ Servers
  • No Logging
  • Up to 10 Devices
Protect your IP with NordVPN →