Public IP vs Private IP — What's the Difference?

doc

Understand the difference between public IP and private IP addresses. Learn how each type works, why both matter for your network setup, and how they affect your privacy and security online.

Public and private IP addresses serve different jobs on the same machine. The public address is the one your home network uses to reach the internet; the private address identifies a device inside your local network. Mixing the two up leads to the common belief that a private address means security, or that a public address means identity. This article separates the ranges, how they travel through NAT and IPv6, and what each one actually exposes.

The two addresses and their roles

A device on a home network typically holds two relevant addresses. The private address is assigned by the local router and used only for traffic within the home or office LAN. The public address is assigned by the upstream provider and faces the internet: it is the number websites, remote services and relay endpoints record when your traffic arrives.

Your phone, laptop and printer can each have their own private address while sharing one public address. The router keeps track of which local device asked for which external connection, and translates between the two sides as traffic crosses.

Address ranges at a glance

CategoryExample rangeWho can see itHow often it changes
Private IPv410.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16Only devices on the same local networkStable within the LAN; reassigned when the router renews leases
Loopback127.0.0.0/8Only the device itselfFixed; always local
Link-local169.254.0.0/16Same local segment onlyAppears when no other address is assigned
Public IPv4Any address outside the private, loopback and reserved blocksEvery remote service the device contactsChanges on reconnect, lease renewal, or provider reassignment
Public IPv6Globally routable prefix plus device identifierEvery remote service; the prefix often persists longer than IPv4 leasesPrefix may change with the provider; the interface identifier may be stable or random per configuration

NAT and shared public addresses

IPv4 addresses are scarce, so most home routers use network address translation. The router keeps one public address and maps outgoing connections from many private devices onto it. To an outside service, all of those devices appear as the same public number.

Carrier-grade NAT goes one step further: the provider places many homes behind a shared public address at its own edge, so even your router's public number may be one of several households. This matters for understanding what a recorded address can attribute: it identifies the shared network, not a single machine, and often not a single household.

IPv6 and why NAT did not disappear entirely

IPv6 supplies a large address pool, so devices can hold globally routable addresses without translation. The local-global distinction still exists: a link-local IPv6 address stays on the segment, while a global address travels externally.

Tracking does not disappear with IPv6. The address is built from a provider-assigned prefix plus a device identifier. The prefix groups all devices on one line, and if the device identifier stays static, it can follow a machine across networks of the same provider. Many systems rotate the identifier for privacy, but the prefix itself still reveals the network and region class.

How to read your own two addresses

  1. Find the local address. In the device's network details, look for the address tied to the active adapter. Private ranges, loopback and link-local entries are internal, not what the internet sees.
  2. Find the public address. Open an IP detection page from the same device. The number it reports is the public exit; compare it against your adapter's local address and they will differ on a routed home network.
  3. Check both IP versions. Note whether the detection page shows an IPv4 address, an IPv6 address, or both. A local private IPv4 alongside a global IPv6 means the site may track through the IPv6 path even when the IPv4 exits through a tunnel.
  4. Notice sharing. If the reported public address matches the one your router WAN shows, you are behind ordinary home NAT. If multiple devices in the household show the same public number, that is normal, not a leak.

Common misreads

  • "A private IP address is safer because outsiders cannot reach it." The private address is not exposed to the internet by design, but security still depends on the router, services open on it, and the public exit. The private number itself grants no protection.
  • "My public IP is my identity." It identifies the network line and often a shared pool. Name, household and device still need another identifier to attach to it.
  • "Two devices with the same public IP are the same person." They are on the same shared network. NAT and CGNAT routinely place many machines behind one number.
  • "IPv6 means everyone sees my real address forever." Privacy extensions rotate the device identifier on many systems, and tunnels can hide the global address. The prefix still reveals network class, but the full address is not a fixed serial number.

Frequently asked questions

Why does my router show a different address than the IP checker?

The router's WAN address may itself sit behind carrier-grade NAT. The checker sees the outer public number from the provider edge; the router's own WAN field can be a private address inside that shared pool.

Can a website see my private IP?

Not from ordinary web traffic. Private addresses never leave the local router. Exceptions come from leaks such as WebRTC, which can expose local addresses to the browser context.

Should I be worried about a public IP shown on a checker?

The address already travels to every site you visit, so reading it changes nothing by itself. Treat it as the network handle it is: it reveals rough location and network type, and it can be changed through a tunnel if that matters to you.