Public vs Private IP: The Difference and How to Check

Check your computer's IP address and you'll see something like 192.168.0.10. Visit a "what is my IP" site and you'll get a completely different number. Both are correct — one is your private IP, the other your public IP. A private IP only means something inside your home or office network. A public IP is globally unique on the internet, and it's the only one websites, game servers, and mail servers ever see.

This guide walks through why two kinds of addresses exist in the first place (IPv4 ran out), exactly which ranges are reserved for private use, what NAT and port forwarding do in between, and how to check each of your addresses. If you just want the answer right now, the What Is My IP tool shows your public address instantly.

Why two kinds of IP exist: IPv4 scarcity

An IPv4 address is 32 bits, which caps the entire supply at roughly 4.3 billion addresses (2^32). That seemed plenty in the early internet, but give every laptop, phone, TV, and smart bulb its own globally unique address and the pool empties fast. So in 1996, RFC 1918 reserved blocks of addresses that are never routed on the public internet and can be reused freely inside any local network. Those are private IPs.

• Millions of homes and companies use the exact same private addresses at the same time. Your 192.168.0.10 and your neighbor's 192.168.0.10 never collide, because they live in separate networks.
• Public IPs are handed out through regional registries (RIRs) to ISPs, and each one is unique worldwide at any given moment.
• The payoff: an entire household needs only one public IP, no matter how many devices sit behind the router. This single trick extended IPv4's life by decades.

The private ranges — if you see these, it's not a public address

Beyond the three RFC 1918 blocks, a few other special-purpose ranges show up constantly in practice. Here is the full cheat sheet.

You don't need to memorize the boundaries. Paste any address into the Private IP Checker and it classifies the range for you — handy for edge cases like 172.16.x.x being private while 172.32.x.x is public.

NAT: how many devices share one public IP

If your devices only have private addresses, how do they reach the internet at all? Your router performs NAT (Network Address Translation): it rewrites the source of every outgoing packet from the device's private IP to the router's own public IP, keeps a note of which port maps to which device, and reverses the swap when replies come back.

Worked example — tracing one request through a home network. Say your router's public IP from the ISP is 203.0.113.45, and behind it sit a PC (192.168.0.10) and a phone (192.168.0.20). Your PC opens a website:

1. The PC sends a packet: source 192.168.0.10:51000 → destination webserver:443.
2. The router rewrites the source to 203.0.113.45:62001, records "port 62001 = the PC's 51000" in its NAT table, and forwards it out.
3. The web server only ever sees 203.0.113.45. The address 192.168.0.10 never leaves your house.
4. The reply arrives at 203.0.113.45:62001; the router looks up its table and hands it back to the PC at 192.168.0.10:51000.
5. If the phone browses at the same time, the router simply assigns it a different port (say 62002). To every website, the phone and the PC appear as the same IP address.

That's the whole mystery of "my PC says 192.168 but websites see something else." To see the address the outside world sees, open What Is My IP; to find out which country and ISP that public address belongs to, use IP Geolocation Lookup.

Port forwarding: why inbound connections need help

NAT handles outbound connections automatically, but it cannot handle a connection that starts from the outside. When a stranger's packet arrives at 203.0.113.45:8080, there is no NAT table entry for it — the router has no idea which internal device should receive it, so it drops the packet.

• Port forwarding is you writing that missing rule by hand: "anything arriving on public port 8080 goes to 192.168.0.10 port 8080."
• This is why hosting a game server, NAS, security camera, or personal web server from home requires router configuration.
• One catch: if your router's WAN address is in the CGNAT range (100.64.0.0/10), your ISP runs another NAT layer above yours, and port forwarding on your own router won't help. You'd need to request a real public IP from the ISP or use a tunneling service.

Dynamic vs static public IPs, and common misconceptions

Most residential public IPs are dynamic: the ISP leases them via DHCP, and the address can change after a router reboot, a long outage, or simply at the ISP's discretion. A static IP is contractually pinned to you — useful for hosting servers or remote access, usually at extra cost. If you want to host on a dynamic IP, DDNS (dynamic DNS) is the standard workaround: a domain name that automatically follows your changing address.

Finally, three misconceptions worth clearing up:

• "A private IP means I'm hidden and secure." No. NAT's side effect of blocking unsolicited inbound connections helps, but it is not a security feature. Malware that a device downloads itself, or ports auto-opened via UPnP, bypass it completely. Private addressing is an address-conservation technique, not a firewall.
• "192.168.0.10 identifies me." The same 192.168.0.10 exists in millions of homes right now. A private address alone identifies nobody on the internet.
• "If someone has my public IP, they know where I live." Not precisely. Run any address through IP Geolocation Lookup and you'll typically get a city and an ISP name — not a street address. And VPNs or proxies change the visible IP, though the VPN provider and your ISP still keep their own records.