Public vs private IP addresses use different maps
The address printed in a device’s Wi-Fi panel often works only inside your home or office. The address on this site belongs to the internet-facing side of the connection.
Learn why your router shows one address while websites see another, and how NAT connects the two scopes.
Private space is intentionally reusable
Every home can use ranges such as 10.0.0.0/8 or 192.168.0.0/16 because public routers never carry those destinations. Reuse makes local planning easy, but it also means a private address cannot identify a location on the wider internet.
Translation keeps the conversation together
For IPv4, a router often replaces the private source address and port with its public address and a mapped port. It remembers that association long enough to deliver replies to the correct device. Unsolicited inbound traffic has no mapping unless you create a port-forward rule.
Other non-public ranges
Loopback, link-local, documentation, multicast, and reserved ranges are also non-global, but they have different purposes. A good diagnostic tool distinguishes these categories instead of calling every non-public address private.
Follow the boundary from a local device to the public internet
Scope explains why a router can show one address while a website reports another. The next pages connect that boundary to range notation, address sharing, and VPN exits.
- Read CIDR and subnet boundaries to identify exactly which local or public range contains an address.
- Review what a public IP reveals to keep network metadata separate from claims about a device or person.
- Run the VPN IP address check to observe how a different public exit changes what this server receives.
A practical checklist
- Use your operating-system network panel for the local address.
- Use Check My IP for the address visible beyond your gateway.
- Remove old port forwards when a service is no longer needed.
Questions readers ask next
Why do search results show a different IP from my router?
The router interface may show its local or provider-facing address, while the website sees a translated public address.
Is 192.168.1.1 visible online?
No. It is commonly a local gateway address and is not routed on the public internet.
Sources and further reading
The key ideas and how they connect
Private addresses work inside a local network. A public address can be routed across the internet. Translation often connects the two for IPv4.
Private ranges are reusable
Many unrelated homes can safely use 192.168.1.0/24 internally.
Public ranges are globally administered
Registries and operators coordinate who announces each routable prefix.
NAT stores a mapping
A router connects an internal address and port with an outside address and port.
Why the router page and an IP website disagree
Your laptop shows 192.168.1.20, the router shows 10.20.30.40 on its provider side, and the homepage shows a third public address. This can happen with home NAT plus carrier-grade NAT. The IP exposure guide explains what the final public address can and cannot reveal.
Core semantic relationships
| Subject | Relationship | Object |
|---|---|---|
| Local device | uses | a private address |
| NAT gateway | translates | private traffic to a public source |
| Internet destination | replies to | the observed public source |