ARTICLE · 8 MIN READ

Public Versus Private IP Addresses Explained

Public Versus Private IP Addresses Explained

Your laptop may report an address such as 192.168.1.25, while websites see a completely different address when you connect. That difference is the practical point of public versus private IP addresses. One identifies your connection on the internet. The other helps devices find each other inside your home, office, or other local network.

Knowing which address you are dealing with prevents common troubleshooting mistakes. It tells you why port forwarding may fail, why a game server cannot be reached, why a work device is visible on Wi-Fi but not from outside the building, and why restarting a router can sometimes change the address websites see.

Public Versus Private IP Addresses: The Core Difference

A public IP address is an address that can be routed across the public internet. Your internet service provider, or ISP, assigns it to your connection, either directly to your router or to a device connected to the modem. Websites, email servers, game servers, and remote-access services use public addresses to send traffic back to the correct internet connection.

A private IP address is used only inside a local network. Your router usually assigns private addresses to phones, computers, smart TVs, printers, consoles, and other connected devices. These addresses are not globally unique, and they are not routed across the public internet.

A familiar physical-address comparison works well here. A public IP address is similar to the street address of an apartment building: it tells the outside world where the building is. Private IP addresses are like apartment numbers inside that building: they identify a specific destination after traffic has already arrived at the right location.

This distinction applies most commonly to IPv4, the address format written as four numbers separated by periods. IPv4 has a limited number of available addresses, which is why private addressing and router-based address translation are so widely used.

Which IPv4 Ranges Are Private?

Private IPv4 addresses come from three ranges reserved for internal networks. They are:

  • 10.0.0.0 through 10.255.255.255
  • 172.16.0.0 through 172.31.255.255
  • 192.168.0.0 through 192.168.255.255

Most home routers use the 192.168.x.x range by default. For example, a router may use 192.168.1.1, while devices receive addresses such as 192.168.1.10 or 192.168.1.25. Larger organizations often use the 10.x.x.x range because it provides far more internal addresses and can be divided into separate network segments.

If you see one of these ranges on your computer or phone, it is a private address. It does not reveal your public internet address, and someone on the internet cannot normally connect directly to it.

Not every non-private address is a usable public address. Some IPv4 ranges are reserved for special purposes, including loopback testing, link-local addressing, documentation, and multicast traffic. For everyday troubleshooting, the key question is whether the address belongs to a private range or is an externally routable address assigned by an ISP.

How Your Router Uses Both Addresses

A typical home network has one public IPv4 address and many private IPv4 addresses. The router sits between the local network and the ISP. On its internet-facing side, it uses the public address. On its local side, it manages private addresses for your devices.

When your laptop visits a website, the laptop sends traffic from its private address to the router. The router changes the source address to its public IP address before sending the traffic to the internet. When the website replies, the router tracks the connection and forwards the response back to the correct device.

This process is called Network Address Translation, or NAT. More specifically, home routers commonly use port address translation, which allows many devices to share a single public IPv4 address at the same time. Your phone, console, work computer, and streaming device can all access the internet through one external address because the router keeps separate records for each connection.

NAT is useful, but it also explains a common limitation: unsolicited traffic from the internet does not know which private device should receive it. By default, the router blocks or ignores incoming connection attempts that it did not expect.

Why Public IP Addresses Matter for Remote Access and Hosting

A public IP address matters whenever someone or something outside your local network needs to initiate a connection to equipment inside it. Examples include hosting a game server, viewing a security camera remotely, accessing a home lab, operating a small business server, or connecting to a remote desktop service.

To make that work over IPv4, you may need to create a port-forwarding rule in the router. The rule tells the router that traffic arriving on a specific public port should be sent to a specific private IP address and port. For example, a rule could direct incoming traffic to a gaming PC at 192.168.1.25.

Port forwarding is not automatic permission to expose a service. The target device must be running the intended service, its local firewall must allow the connection, and the software must be securely configured. Opening unused ports creates unnecessary exposure. Use strong passwords, keep the device updated, and forward only the ports you actually need.

A changing public IP can also affect remote access. Many residential ISPs assign dynamic public addresses, meaning the address can change after a modem restart, a lease renewal, or ISP maintenance. A static IP address stays the same and is often available as an add-on service, particularly for business connections. Dynamic DNS can help services remain reachable when the public address changes, but it does not solve every connectivity issue.

The CGNAT Issue: When You Do Not Control a Public IPv4 Address

Sometimes your router displays a wide-area-network address that is not the same address shown by an external IP check. This often means your ISP uses Carrier-Grade NAT, commonly called CGNAT.

With CGNAT, the ISP places another layer of NAT between your router and the public internet. Multiple customers can share a public IPv4 address, conserving the limited IPv4 supply. Normal web browsing, streaming, and most online services work without trouble. The complication appears when you need inbound connections for hosting, certain games, remote access, or some peer-to-peer applications.

If your router’s WAN address falls in the 100.64.0.0 through 100.127.255.255 range, CGNAT is a likely explanation. A mismatch between the router’s WAN address and the public address seen by websites is another useful clue. In that situation, forwarding ports on your own router may not be enough because the ISP-controlled NAT layer still blocks incoming traffic.

Your options depend on the ISP. Some providers can assign a public IPv4 address, offer a static IP plan, remove CGNAT on request, or provide IPv6 connectivity. A VPN or managed relay service can also work for specific remote-access needs, although it adds another service and may not suit every application.

How to Find the Address You Need

Start with the question you are trying to answer. If you need to know what address a website, game service, or remote user sees, check your public IP address from an external web-based tool. That result is the address associated with your internet connection at that moment.

If you need to configure a printer, reserve an address for a console, or create a port-forwarding rule, find the device’s private IP address in its network settings or in your router’s connected-device list. For port forwarding, it is usually best to create a DHCP reservation so the device keeps the same private address over time.

If a service is unreachable, work from the outside inward. Confirm the public address, check whether CGNAT is involved, verify the port-forwarding rule, confirm the device’s private address, and review the device firewall. A ping test, traceroute, speed test, and WHOIS lookup can each answer different parts of the problem, but none replaces checking the actual path traffic must take.

Public Addresses Are Not Precise Location or Identity Data

A public IP address can often be associated with an ISP and an approximate geographic area. It does not reliably identify a person, household, or exact street location. IP geolocation databases may show the location of an ISP gateway, a regional service area, or the billing address associated with an allocation rather than the current user.

WHOIS data has a different purpose. It can show the organization responsible for an address block, such as an ISP, cloud provider, university, or company. It generally identifies the network owner, not the individual using an address at a particular time.

A public IP is also not a password or a complete security risk by itself. It is normal for websites to see it when you connect. The real concern is exposing poorly secured services through that address. Keep router administration restricted, disable remote management unless you need it, and avoid treating an IP address as proof of identity.

IPv6 Changes the Address Supply, Not the Need for Care

IPv6 was designed in part to address IPv4 exhaustion. It uses a much larger address space and does not require NAT in the same way IPv4 does. An IPv6-enabled device may receive a globally routable address in addition to its private IPv4 address.

That can make direct connectivity easier, but it raises the importance of firewall rules. With IPv6, a device may be publicly addressable without an IPv4-style port-forwarding rule. A properly configured router firewall should still block unwanted inbound connections by default.

When a connection fails, identify whether you are troubleshooting the device’s private address, your router’s public address, or an ISP-managed address behind CGNAT. Once you know which layer owns the problem, the next fix becomes much easier to choose.