If you've ever tried to set up a home security camera, configure remote desktop access, or host a game server, you've probably encountered the confusing reality that your device actually has two different IP addresses — and they serve very different purposes. Your public IP address is the one the rest of the internet sees, assigned by your ISP. Your private IP address is the one used within your local network, assigned by your router. Understanding the difference between these two types of addresses, and how your router translates between them, is fundamental to understanding how your home or office network actually works.

In my 20+ years of IT and network administration, this is one of the topics I explain most frequently. It's also one of the most important concepts to understand before you start opening ports, setting up servers, or troubleshooting connectivity issues. Let's break it down.

What Is a Public IP Address?

Your public IP address is the address that identifies your network on the global internet. It's assigned to your router by your Internet Service Provider (ISP) and is visible to every website, service, and server you connect to. When you visit IP Lobster, the address displayed at the top of the page is your public IP address — the one the outside world uses to send data back to you.

Public IP addresses are globally unique. No two devices on the internet can have the same public IP address at the same time. This uniqueness is managed by the Internet Assigned Numbers Authority (IANA), which allocates blocks of addresses to Regional Internet Registries (RIRs), which in turn allocate them to ISPs, which assign them to individual customers.

Most residential internet connections use dynamic public IP addresses, meaning your ISP may change your address periodically — often when your router restarts or when the ISP's DHCP lease expires. Businesses typically pay for static public IP addresses that never change, which is necessary for hosting servers, running VPN endpoints, or any service that other systems need to reach at a consistent address.

The key characteristic of a public IP address is that it's routable on the internet. Any device anywhere in the world can send packets to your public IP address, and those packets will be delivered to your router (assuming no firewalls block them along the way). This is what makes public IP addresses both powerful and potentially risky from a security perspective.

What Is a Private IP Address?

Private IP addresses are used within local networks — your home Wi-Fi, your office LAN, or any internal network that isn't directly exposed to the internet. They're assigned by your router's DHCP server and are only meaningful within your local network. A device with the private address 192.168.1.50 on your home network can't be directly reached from the internet using that address.

The Internet Engineering Task Force (IETF) defined three ranges of IP addresses reserved exclusively for private use in RFC 1918. These ranges are 10.0.0.0 to 10.255.255.255 (a single Class A block with over 16 million addresses), 172.16.0.0 to 172.31.255.255 (16 Class B blocks with about 1 million addresses), and 192.168.0.0 to 192.168.255.255 (256 Class C blocks with about 65,000 addresses).

The 192.168.x.x range is by far the most common in home networks. If you check your device's network settings, you'll almost certainly see an address like 192.168.0.x or 192.168.1.x. Business networks often use the 10.x.x.x range because it provides far more addresses — useful when you have hundreds or thousands of devices on the network. The 172.16.x.x through 172.31.x.x range is less commonly seen but provides a middle ground between the two.

The critical thing about private IP addresses is that they can be reused across different networks without conflict. Your home router might assign 192.168.1.100 to your laptop, and your neighbor's router might assign the exact same address to their laptop. There's no conflict because these addresses only have meaning within their respective local networks. This reusability is what saved the internet from running out of IPv4 addresses decades ago.

How NAT Bridges the Gap

If private IP addresses can't be reached from the internet, how does your laptop with address 192.168.1.100 actually browse the web? The answer is NAT — Network Address Translation — and it's one of the most important technologies in modern networking.

Your router sits at the boundary between your private network and the public internet. It has two IP addresses: a private one facing your local network (usually something like 192.168.1.1) and a public one facing the internet (assigned by your ISP). When your laptop sends a request to load a website, the router intercepts that packet, replaces the source address (your private 192.168.1.100) with its own public IP address, and keeps a record of which internal device made the request in its NAT table. When the website's server responds, the packets arrive at your router's public IP. The router checks its NAT table, finds that this response belongs to your laptop, replaces the destination address with 192.168.1.100, and forwards the packet to your device.

This process happens for every single packet, for every device on your network, simultaneously. Your router is constantly translating between private and public addresses, maintaining a table that tracks thousands of active connections. From the outside, all traffic from your entire household appears to come from a single public IP address. The websites you visit have no way to know how many devices are behind that address.

NAT provides a significant side benefit for security: because your private devices aren't directly addressable from the internet, unsolicited incoming connections are blocked by default. If an attacker sends a packet to your public IP address on a random port, your router doesn't know which internal device to forward it to (unless you've set up a port forwarding rule), so the packet is dropped. This is effectively a basic firewall, and it's why home networks are reasonably secure out of the box even without additional security software.

Finding Your IP Addresses

Finding your public IP address is straightforward — visit IP Lobster and it's displayed immediately. This is the address your ISP has assigned to your router, and it's what every server on the internet sees when you connect.

Finding your private IP address depends on your operating system. On Windows, open a command prompt and type ipconfig. Look for the "IPv4 Address" under your active network adapter — that's your private address. On Mac, go to System Settings, then Network, and click on your active connection to see the IP address. On Linux, run ip addr show or hostname -I in a terminal. On smartphones, the IP address is typically found in Wi-Fi settings by tapping on the connected network.

Your router's private IP address (the gateway address) is also worth knowing, as it's the address you'll use to access your router's administration interface. It's typically 192.168.0.1 or 192.168.1.1, but you can find it listed as the "Default Gateway" in the output of ipconfig (Windows) or ip route (Linux).

When the Distinction Matters

Port forwarding is the most common scenario where understanding public vs. private IPs is essential. If you want to host a service that's accessible from the internet — a game server, a web server, a security camera feed — you need to configure your router to forward incoming connections on specific ports from your public IP to the private IP of the device running the service. Without this forwarding rule, the traffic arrives at your router but has nowhere to go.

Remote access requires your public IP address. If you want to connect to your home computer from the office using remote desktop, you need to know your home network's public IP (and have port forwarding configured for the RDP port). Since residential public IPs are usually dynamic, many people use Dynamic DNS (DDNS) services that associate a hostname with your current public IP, automatically updating when the address changes.

Security camera setup often involves port forwarding from your public IP to the camera's private IP. However, this exposes the camera's interface to the internet, so it's crucial to use strong passwords and keep the camera's firmware updated. A better approach for most home users is to use cameras that connect to a cloud service through an outbound connection, which doesn't require opening any ports.

VPN configuration depends on the type of VPN. If you're connecting to a commercial VPN service, the service provides the public IP of their server. But if you're setting up a VPN server on your own network (to access your home network remotely), you'll need to know your public IP and configure port forwarding for the VPN protocol.

Troubleshooting connectivity often starts with identifying whether the problem is on the local network or on the internet side. If your device can reach your router (ping the gateway address) but can't reach the internet (ping 8.8.8.8), the problem is likely with your ISP connection or router's WAN configuration. If your device can't even reach the router, the problem is on your local network.

IPv6 Changes the Equation

The public/private distinction exists largely because of IPv4 address scarcity. With only about 4.3 billion possible IPv4 addresses and billions of internet-connected devices, NAT and private addressing became essential to stretch the available supply. IPv6, with its vastly larger address space (roughly 340 undecillion addresses), was designed to eliminate this need.

In an IPv6 world, every device can have its own globally unique, publicly routable address. Your laptop, phone, smart TV, and thermostat could each have their own public IPv6 address without NAT. This simplifies networking in many ways — peer-to-peer connections work without port forwarding, and routing is more efficient without the overhead of address translation.

However, the elimination of NAT in IPv6 also removes that incidental security benefit of private addressing. In an IPv6 network, firewalls become even more important because every device is potentially reachable from the internet. Most IPv6-capable routers default to blocking unsolicited inbound connections, maintaining the security posture users expect, but the underlying mechanism is an explicit firewall rather than the inherent limitation of NAT.

As of 2026, we're in a transition period where both IPv4 and IPv6 coexist. Most networks run dual-stack configurations that support both protocols simultaneously. Understanding the public/private distinction remains essential for IPv4, which still carries the majority of internet traffic.

Key Takeaways

Your public IP address is your network's identity on the internet, visible to every server you connect to and viewable anytime at IP Lobster. Your private IP address is your device's identity on your local network, meaningful only within the walls of your home or office. NAT on your router translates between the two, allowing dozens of devices to share a single public address. Understanding this relationship is the foundation for everything from basic troubleshooting to hosting services and securing your network.